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

CRA-le vastavus turvameeskondadele

Buildi ajal salvestatud tõendid, haavatavuste seire ja triaaž teie CRA protsessi tarneahela poole jaoks

Pidev turvaseire

CRACI hindab teie tarnitud tarkvara jälgitavaid SBOM-e uute haavatavuste avaldamisel pidevalt uuesti ja koondab leiud kõigist buildidest ja repositooriumidest. See on salvesti, mitte skanner: iga SBOM tuleb sellest, mida build tegelikult alla laadis, ja sellel on täielikkuse olek. Hoiatused annavad märku väljuva liikluse poliitika rikkumistest.

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

Haavatavuste triaaž

Turvameeskonnad teevad avastatud haavatavuste triaaži ja suunavad need parandamise eest vastutavatele meeskondadele ning CRACI toetab VEX-i. See näitab, millised teie buildid, repositooriumid ja tooted sisaldavad haavatavat komponenti, nii et teate, kus iga leid kehtib.

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

Intsidentidele reageerimine ja jälgimine

Kui haavatavust kasutatakse aktiivselt ära, valmistab CRACI ette ELi küberkerksuse määruse (Cyber Resilience Act, CRA) teadete sisu (eelhoiatus, teavitus ja lõpparuanne), mille te esitate. Selle inventarivaade näitab, millised tarkvaraversioonid on millistesse toodetesse juurutatud, ning API tagastab SBOM-id, võrgujäljed ja päritoluteabe teie kirjete jaoks.

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

Tarneahela turvalisus

Iga SBOM salvestatakse selle põhjal, mida build tegelikult kaasa tõi, sealhulgas CI vahemäludest taastatud paketid. Runneri väljuva liikluse poliitika piirab, kuhu build saab ühenduda, valideeritakse enne töö algust ja suletakse tõrke korral ning API tagastab SBOM-id, võrgujäljed ja päritoluteabe. Tarnijate SBOM-e jälgitakse teie enda buildide kõrval.

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

Tugevdage oma turvaseisundit

Broneerige demo, et täiustada turvatööd CRACI-ga

Broneerige demo