The reporting clock starts. The drafts are ready.

When an exploited vulnerability hits a release you shipped, Cordon opens the incident and drafts the Cyber Resilience Act's 24-hour and 72-hour reports. A person submits them.

exploitedCVE-2026-41187, on CISA KEV
Shipped inabc Gateway 4.2.0 and 4.2.1
23:41Early warning duedraft ready
71:41Full notification duedrafting

Cordon never files automatically.

Evidence

Checked by an auditor, not trusted on faith.

SBOM per releaseCycloneDX 1.6 or SPDX, with each component's vulnerabilities and exploited status
VEXEach known vulnerability, with its status for the release; OpenVEX, CycloneDX and CSAF statements read in
AI-BOMAgents, MCP servers and models, as a CycloneDX ML-BOM
Sealed and signedHashed together and signed with Ed25519
Exploited-vulnerability watchEvery shipped release, matched as advisories land
Auditor accessA read-only role: exports and signatures, nothing else
Why it holds up

Evidence that survives a sceptical reader.

A scan that says what it did not checkEvery result records coverage: files unread, limits hit, rules disabled. Incomplete evidence is never presented as complete.
Results signed where they were madeCI uploads are signed with the pipeline's own identity, so a result cannot be edited between the runner and the record.
Suppressions with a reason and an ownerEvery accepted risk names who accepted it, why, and when it expires, in the audit history.
Your suppliers, held to the same barLoad a vendor's SBOM, CycloneDX or SPDX, and see their components against the same intel, exploited flags and policy as your own, beside the vulnerabilities the vendor listed.
Verifiable without trusting CordonEach sealed bundle carries its digest and signature, so an auditor checks it offline, with no account and no call home.
A full audit trailEvery scan, decision, suppression, export and sign-in recorded, append-only, and exportable to your SIEM.
CRA and exports

Sealed when it ships. Ready when it is exploited.

Each release's SBOM, VEX, AI-BOM and signed scans are sealed together. When CISA KEV or the EUVD lists a flaw in something you ship, the release, the reachability and the ENISA early-warning draft are already open, with the clock running.

Watch a release seal

From the scans of what shipped, to a seal.

The release's revisions, its scans and its evidence, sealed together and verifiable offline.

release ledger 2.14 sealing evidence
revisions 3 repositories at their release commits
scans 3 complete, signed by CI (verified)
sbom 1,284 components CycloneDX 1.6
vex 41 vulnerabilities, each with a status
ai-bom 9 agents, MCP servers and models
digest sha256:4f1c08b2...e9a2
signature Ed25519 key 7c2a91d0
sealed evidence ready for an auditor
14:30 CISA KEV CVE-2026-41187 matches ledger 2.14
incident opened early warning due in 24 h draft ready
full notification due in 72 h drafting
AI-BOM

AI in the product, listed.

Regulators are starting to ask what AI a product contains. The answer is already in the evidence.

Compliance evidence is part of Enterprise.