The Certificate You Have to Ask For
from The Sam Ellis Show Hosted by Sam Ellis
The Certificate You Have to Ask For The Cloud Security Alliance’s public STAR Registry displayed the AIUC-1 agent-safety trustmark beside nine services. A buyer could reasonably read that placement as third-party reassurance. When this show asked what certificate identity, issuer, validity dates, audited product or configuration scope, and current status CSA verifies before adding the trustmark, CSA chief technology officer Daniele Catteddu answered: “None.” The exchange began with a narrower defect. On September 15, all nine registry links labeled “Download AIUC-1” returned the same one-page blank PDF. Its metadata named the U.S. Justice Department’s Executive Office for Immigration Review and carried a 2006 creation date. CSA responded the next day that the download option was an error and should not have appeared. It removed the links. CSA says AIUC-1 appears as a third-party Partner entry outside the CSA-governed program; validation remains the third party’s responsibility. AIUC announced a $40 million Series A on September 15, bringing its disclosed funding total to $55 million. Its commercial proposition combines an agent-specific standard, accredited audit work, technical evaluation, certification, and access to insurance. AIUC says its testing uses roughly 5,000 business-specific risk and attack combinations covering failures such as jailbreaks, hallucinations, and data leaks. The process has real structure and real concentration. AIUC owns the auditor-accreditation process, is currently the sole listed technical-testing body, and issues every certificate through its certification committee. Schellman is the only fully accredited auditor listed; several other firms are provisional. AIUC’s documentation also says the company may periodically conduct audits itself. A September 15 capture of AIUC’s auditor documentation described a certification threshold requiring all applicable requirements to pass with no P0 or P1 vulnerabilities. It classified P2 findings as “Significant,” with moderate potential for harm and discretionary remediation. It also said the report’s technical-testing section uses final-round results while reporting the total test count across rounds, and marked a future model for auditor-run evaluations as “Coming soon.” That page was unavailable when checked again on September 17. AIUC’s live certification page separately states that certification cannot guarantee a system is secure, safe, or reliable. The trustmark is easier to inspect than the evidence beneath it. Cursor lists an AIUC-1 certificate behind an access-request form. Intercom’s Fin Trust Center lists a locked AIUC-1 Certification Report described as including quarterly evaluation results from March and June 2026. Full-access requests were submitted for both artifacts on September 17; both portals confirmed receipt, but neither had produced access or an artifact more than three hours later. That does not establish refusal or report absence. It establishes that the public signal travels farther than the supporting evidence. Lovable publishes a substantive 15-page AIUC-1 paper naming a completed Schellman audit. The paper tells buyers: “Ask for the test results. Ask for the audit report.” It includes neither. AIUC itself tells buyers to contact the certified party for the report and exact certification scope. Lenny Zeltser, former chief information security officer at Axonius and a Faculty Fellow at the SANS Institute, replied on the record. He said buyers should confirm the exact agent, tools, model versions, and data flows covered by the audit and AIUC testing. He also pointed buyers to exclusions, judgment-based tests, and the latest quarterly retest. On AIUC’s insurance proposition, Zeltser said he would want policy exclusions, claims history, and evidence of how much risk AIUC retains before giving the argument much weight. AIUC says certification can open access to insurance. Its ElevenLabs announcement says unnamed leading insurers can cover risks created by deployed agents, including incorrect information supplied to customers. Historical specialist reporting names Beazley as a capacity provider for an AIUC liability product; separate reporting describes certified Lovable customers as insured through the Lloyd’s market. Those reports do not establish the current carrier entity, policyholder, trigger, limits, exclusions, jurisdictions, loss allocation, claims process, or AIUC’s retained risk. This show found no public claim record demonstrating what happens after a certified agent causes a covered loss. The practical standard is not whether a badge exists. It is whether a qualified buyer can determine what exact system was examined, what material problems survived, what changed after certification, and what loss the insurance actually transfers before treating the trustmark as permission to deploy. Key points CSA corrected the blank-download defect, but says it validates none of the underlying AIUC-1 partner-entry certificate evidence. AIUC combines standard-setting, auditor accreditation, current technical testing, certificate issuance, and an insurance route. Outside auditors collect evidence and prepare reports, while AIUC currently performs the technical testing and issues certificates. September 15 AIUC documentation allowed discretionary remediation of P2 “Significant” findings and described final-round result reporting; that page was unavailable two days later. Cursor and Intercom expose named AIUC-1 artifacts behind access-request forms. Lovable publishes a paper about its audit, not the underlying audit report or test results. The public record does not disclose enough current policy or claims information to establish what AIUC-linked insurance transfers in practice. The next meaningful proof is an observable procurement, deployment, coverage, or claim consequence—not another trustmark or funding announcement. Sources and presenter notes AIUC — Series A announcement. Current-cycle first-party source for the $40 million round, $55 million disclosed total, named certified organizations, approximately 5,000 business-specific risk and attack combinations, and the standards-audits-insurance proposition. Company claims are attributed rather than treated as independent validation. TechCrunch — AIUC funding and enterprise-assurance report. Current-cycle independent business reporting on the founders, financing, customers, third-party assurance pitch, test count, and Rune Kvist’s statement that humans verify the final audit. AIUC-1 — certification overview. Current first-party documentation for certification scope, twelve-month certification, quarterly technical retesting, annual re-audit, customer custody of full reports, and the explicit limit that certification does not guarantee security, safety, or reliability. AIUC-1 — accredited auditors. Current first-party source for Schellman’s full accreditation, provisional auditors, AIUC’s accreditation authority, AIUC’s current role as the sole technical-testing body, certificate issuance, and periodic AIUC-conducted audits. AIUC-1 — live documentation index. Current index used to recheck which process pages remained live on September 17. The auditor-delivery page captured on September 15 was no longer listed or available; the episode dates claims drawn from that preserved page. Schellman — first accredited AIUC-1 auditor. Background first-party participant source describing Schellman’s evidence-collection and reporting role alongside AIUC’s technical evaluations and certificate issuance. AIUC-1 × CSA AI Controls Matrix crosswalk. Current first-party scope context. The crosswalk identifies both aligned controls and explicit gaps; it is not evidence that a certified customer lacks governance or that a certificate is invalid. Cloud Security Alliance STAR Registry. Current registry surface where nine AIUC-1 Partner entries were observed. CSA’s direct response corrected the blank-download defect and clarified that it does not validate the underlying partner-entry certificate evidence. Cursor — AIUC-1 certification. Participant source describing Schellman’s control review, AIUC testing across IDE and cloud-agent surfaces, thousands of scenarios, quarterly evaluation, annual audit, and a detailed report available through Cursor’s trust portal. Intercom / Fin Trust Center. Current access-state source listing a locked AIUC-1 Certification Report described as including March and June 2026 quarterly evaluation results. Lovable — AIUC-1 paper. Participant paper naming a completed Schellman audit and urging buyers to ask for the test results and audit report. It is not itself the certificate, audit report, or complete test-results package. Lenny Zeltser — analysis of AIUC-1. Background independent analysis of scope, auditor-selection incentives, accreditation structure, and buyer diligence. The episode’s quotations come from Zeltser’s separate on-record September 16 response to this show. AIUC / ElevenLabs — insurance announcement. Background participant claim that AIUC-1-backed insurance can cover deployed-agent actions and incorrect customer information. The announcement does not identify the carrier or disclose complete policy terms or claims history. The Insurer — historical Beazley report. Historical specialist reporting naming Beazley as capacity provider for an AIUC liability product. This is not current confirmation of the carrier entity or any named customer’s coverage. The Next Web — Lovable, AIUC-1, and Lloyd’s. Historical secondary report connecting certified Lovable customers to insurance through the Lloyd’s market. It does not disclose the policy form, exclusions, claims process, or current applicability to another customer. CSIS — AI insurance and deployment. Independent background analysis explaining why insurance can become a practical deployment gate and why weak loss data and poor visibility into models, use cases, and controls make AI risk difficult to price. Source-response status CSA replied on September 16 through its media representative with answers attributable to chief technology officer Daniele Catteddu. CSA’s correction was independently verified. Lenny Zeltser replied on the record and permitted quotation. AIUC was contacted through the company address published in its FAQ after its press-group address rejected external delivery. Schellman, Beazley, and CSIS were also contacted through documented routes. A final pre-publication Proton Mail sweep found no substantive reply from those four. Cursor and Intercom/Fin had not granted access or delivered the requested artifacts by the final sweep. None is characterized as refusing access or declining to comment. If you buy, audit, insure, or operate an AIUC-1-certified agent, tell the show what evidence you received, what exclusions were visible before purchase, and whether the certification changed a deployment decision or claim. Use the subject line AIUC-1 evidence. Anonymous notes and source-protection requests are welcome at [email protected]. Every message is read.
Embed this episode
What this episode covers
Sam Ellis reports on an AI-agent safety trustmark whose public signal travels farther than the certificate scope, audit results, governance, and insurance evidence beneath it.
No transcript yet.