103% more reported CVEs per day in 2026 than last year.

CRA Compliance for Security Teams

Build-time evidence, vulnerability monitoring and triage for the supply chain side of your CRA process

Continuous Security Monitoring

CRACI keeps re-evaluating the monitored SBOMs of what you shipped as new vulnerabilities are published, and aggregates findings across builds and repositories. It is a recorder, not a scanner: each SBOM comes from what the build actually fetched, with a completeness state. Alerts flag egress policy violations.

Vulnerability tracking after release After a release ships, its SBOM stays monitored. When a new vulnerability is published, CRACI re-evaluates the monitored SBOMs, finds the affected releases, and the security team triages the finding and routes it to the team that owns the fix. The inventory view shows which software versions are deployed to which products. Release shipped SBOM monitored Later New advisory published Re-evaluated automatically Finding: critical, in 2 releases 1. Triage 2. Route to owner 3. Team fixes Policy gates can block a build on findings · VEX supported Inventory: deployed versions Product Version Web app v4.12.0 Mobile API v2.3.1

Vulnerability Triage

Security teams triage discovered vulnerabilities and send them to the teams that own the fix, and CRACI supports VEX. It shows which of your builds, repositories and products contain a vulnerable component, so you know where each finding applies.

Triage and routing to the owning team A security team triages a discovered vulnerability and sends it to the team that owns the fix. CRACI supports VEX for recording how a vulnerability affects your product. New finding Vulnerable component in shipped builds 3 builds 2 repositories Security team Triages the finding VEX supported Owning team Receives the finding and ships the fix Each finding reaches the people who can act on it Policy gates can block a build on findings, so a known issue does not ship again

Incident Response & Tracking

When a vulnerability is actively exploited, CRACI submits the CRA notifications (early warning, notification and final report) on your behalf. Its inventory view shows which software versions are deployed to which products, and the API returns SBOMs, network traces and provenance for your records.

CRA notifications, submitted for you When a vulnerability is actively exploited, the CRA sets deadlines: an early warning within 24 hours, a notification within 72 hours and a final report 14 days after a fix is available. CRACI submits them through the CRA Single Reporting Platform to the CSIRT and ENISA on the manufacturer's behalf. Actively exploited vulnerability found Aware 24 hours Early warning 72 hours Notification Fix + 14 days Final report CRACI submits on your behalf Through the CRA Single Reporting Platform to the CSIRT and ENISA and shows which products and releases are affected What stays with you The reporting obligation itself Informing affected users Severe incidents: final report within one month

Supply Chain Security

Every SBOM is recorded from what the build actually pulled in, including packages restored from CI caches. An egress policy on the runner limits where a build can connect, is validated before the job starts and fails closed, and the API returns SBOMs, network traces and provenance. Vendor SBOMs are monitored alongside your own builds.

An egress policy on the build network A build job connects to hosts in its egress policy, such as package registries and Git, and a connection to a host outside the policy is blocked. The policy is validated before the job starts and fails closed, and a violation sends an alert. Egress policy Default deny Validated before the job starts Fails closed · 24 source presets Build job on a CRACI runner npm registry allowed PyPI allowed Git over HTTPS allowed Unapproved host blocked Alert on policy violation Connections are recorded in the job's network trace

Strengthen your security posture

Book a demo to enhance security operations with CRACI

Book a demo