131% flere rapporterede CVE'er pr. dag i 2026 end sidste år.

Livscyklusstyring

Fra første build til end-of-life – spor sårbarheder, patches og versioner på tværs af hele din produktportefølje

Sårbarhedsovervågning

Løbende scanning af CVE'er og sikkerhedsadvisories på tværs af hver produktversion i din flåde. CRACI sammenholder nye sårbarheder med dit enhedsinventar, så du, når en trussel opstår, straks ved, hvilke produkter og kunder der er berørt – og kan handle, før det bliver til en hændelse.

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

Sporing af patches og opdateringer

Spor hele afhjælpningsforløbet fra opdagelsen af en sårbarhed til udrulningen af en patch. CRACI overvåger, hvilke produktversioner der er patchet, hvilke der afventer, og hvilke der stadig er eksponerede – så du får et klart billede af dit sikkerhedsniveau på tværs af hver release.

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

Versionsstyring

Styr den komplette versionshistorik for hvert produkt gennem hele dets livscyklus. CRACI sporer firmwarereleases, ændringer i afhængigheder og SBOM'ens udvikling over tid, så du kan sammenligne versioner, forstå, hvad der ændrede sig, og spore enhver komponent tilbage til det build, der introducerede den.

Provenance data from every build Every job on CRACI records the packages it fetched and its network trace. The public REST API returns the job's SBOMs, network trace and provenance. Build release job on CRACI Recorded packages fetched network trace Provenance build data, via the API Ask the API about any job Job → SBOM, trace, provenance Returned by the API Job Packages CycloneDX SBOM Network trace Recorded on every CRACI job, no extra step

Planlægning af end-of-life

Planlæg og kommunikér et produkts end-of-life med fuldt overblik over konsekvenserne. CRA kræver, at producenter leverer sikkerhedsopdateringer i produktets forventede levetid. CRACI hjælper dig med at spore supporttilsagn, identificere EOL-datoer, der nærmer sig, og sikre, at kunderne får besked og bliver migreret, før supporten ophører.

CRA notifications, prepared 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 prepares their content; a person at the manufacturer submits them through the CRA Single Reporting Platform to the CSIRT and ENISA. Actively exploited vulnerability found Aware 24 hours Early warning 72 hours Notification Fix + 14 days Final report CRACI prepares the notification content You submit it through the 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

Sikr dine produkter på lang sigt

Book en demo, og styr dine produkters sikkerhedslivscyklus fra ende til anden

Book en demo