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

CRA-compliance til telekommunikation

Sikr netværksinfrastruktur, og sørg for CRA- og NIS2-compliance for teleudstyr og samfundsvigtige tjenester

Compliance for netværksudstyr

Omfattende CRA- og NIS2-compliance for teleudstyr og -infrastruktur. CRACI styrer compliance for routere, switches, basestationer og netværksenheder. Følg firmwareopdateringer og sikkerhedspatches, og vedligehold dokumentation for samfundsvigtige tjenester og kritisk netværksinfrastruktur.

Embedded builds on CRACI runners Yocto and BitBake builds such as core-image-sato run on CRACI runners at size 32. Like every CRACI job, the build runs under an egress policy, records what it fetched and its provenance data. Embedded build bitbake core-image-sato Yocto and BitBake; pi-gen for Raspberry Pi OS CRACI runner, size 32 32 vCPU in an isolated virtual machine Egress policy Fetches recorded Provenance Firmware image SBOM recorded during the build

Styring af infrastruktursikkerhed

Beskyt kritisk teleinfrastruktur med løbende sikkerhedsovervågning under NIS2- og CRA-kravene. Spor sårbarheder på tværs af netværksudstyr, og sørg for infrastrukturens robusthed. Opfyld lovkravene til samfundsvigtige tjenester og netværkskomponenter med høj kritikalitet.

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

Compliance i carrier-klasse

Bygget til teleudbydere og udstyrsproducenter. CRACI skalerer til at styre compliance for systemer i carrier-klasse med komplekse afhængigheder. Understøttelse af SDN, NFV og cloud-native netværksarkitekturer med omfattende SBOM-styring.

An SBOM recorded during the build Packages from npm, PyPI, Cargo, Go, OCI registries and the CI cache pass through a package-aware proxy on the CRACI runner. The job's SBOM lists what was fetched, states its completeness and exports as CycloneDX or SPDX. Package sources npm PyPI Cargo · Go OCI registries CI cache restore Package- aware proxy on the runner Job SBOM express 5.2.1 requests 2.32.3 serde 1.0.219 + transitive deps Declared license on every component Complete Completeness states per job and cache: Complete, Complete with connections, Incomplete, Unavailable, Not recorded CycloneDX · SPDX

Gennemsigtighed i forsyningskæden

Spor og validér komponenter på tværs af komplekse telekommunikationsforsyningskæder. Overvåg tredjepartsfirmware, styr leverandørers compliance, og oprethold fuld synlighed i netværksudstyrets afhængigheder. Sørg for forsyningskædesikkerhed for kritisk infrastruktur.

Vendor SBOMs tracked next to your own SBOMs from your own builds and SBOMs added from your vendors are monitored in the same place, so bought-in components are re-evaluated against new vulnerabilities alongside your own dependencies. Your builds api-service SBOM web-app SBOM firmware SBOM Your vendors Payment SDK SBOM Camera module SBOM RTOS SBOM Monitored in one place Every SBOM re-evaluated as new vulnerabilities are published Third-party code tracked like your own dependencies Findings triaged and routed to the team that owns the fix

Sikr din kritiske infrastruktur

Book en demo for at sikre CRA- og NIS2-compliance på teleområdet med CRACI

Book en demo