2026. aastal teatati päevas 138% rohkem CVE-sid kui eelmisel aastal.Uus: alati töös olevad Fixboxid. Haavatavad sõltuvused, parandatud ja kontrollitud.

Elutsükli haldus

Esimesest buildist elutsükli lõpuni – jälgige haavatavusi, paiku ja versioone kogu oma tooteportfellis

Haavatavuste seire

CVE-de ja turvateadete pidev skannimine teie seadmepargi iga tooteversiooni lõikes. CRACI seob uued haavatavused teie seadmete inventariga, nii et ohu ilmnemisel teate kohe, millised tooted ja kliendid on mõjutatud – ning saate tegutseda enne, kui sellest saab intsident.

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

Paikade ja uuenduste jälgimine

Jälgige kogu parandamise elutsüklit haavatavuse avastamisest paiga paigaldamiseni. CRACI jälgib, millised tooteversioonid on paigatud, millised ootel ja millised endiselt avatud – nii saate selge pildi oma turvaseisundist iga väljalaske lõikes.

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

Versioonihaldus

Hallake iga toote kogu versiooniajalugu kogu selle elutsükli vältel. CRACI jälgib püsivara väljalaseid, sõltuvuste muudatusi ja SBOM-i muutumist ajas, nii et saate versioone võrrelda, mõista, mis muutus, ja jälitada iga komponendi tagasi buildini, mis selle kaasa tõi.

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

Elutsükli lõpu planeerimine

Planeerige ja teavitage toote elutsükli lõppu, nähes selle mõju täielikult. ELi küberkerksuse määrus (Cyber Resilience Act, CRA) nõuab, et tootjad pakuksid turvauuendusi toote eeldatava kasutusaja jooksul. CRACI aitab teil jälgida tugikohustusi, tuvastada lähenevaid EOL-kuupäevi ja tagada, et kliente teavitatakse ja nad viiakse üle enne toe lõppu.

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

Kaitske oma tooteid pikaks ajaks

Broneerige demo ja hallake oma tooteturvalisuse elutsüklit algusest lõpuni

Broneerige demo