The EU Cyber Resilience Act asks manufacturers of products with digital elements to know what is in their software, fix vulnerabilities without delay and report actively exploited ones within hours. We build the engineering side of that: SBOMs, signing, vulnerability handling and a reporting workflow. Your counsel assesses compliance.
Reporting of actively exploited vulnerabilities applies since 11 Sep 2026.1
SBOMs, signing, vulnerability handling and a 24h / 72h / 14-day reporting workflow.
Technical controls and an evidence pack for your counsel.
Regulation (EU) 2024/2847, Article 71(2):1
We quote the text, then say what we implement. Whether a requirement applies to your product, and how, is for your counsel and, where relevant, your notified body.
| Requirement (Regulation (EU) 2024/2847) | Technical control |
|---|---|
| Annex I, Part II (1): identify and document components, “including by drawing up a software bill of materials in a commonly used and machine-readable format covering at the very least the top-level dependencies”1 | CycloneDX SBOM generated for every release in CI, stored and versioned; monitored in Dependency-Track |
| Annex I, Part II (2): address and remediate vulnerabilities without delay, including by providing security updates1 | Vulnerability alerts on released versions, triage workflow with owners and deadlines, security fixes released separately where feasible |
| Annex I, Part II (3): apply effective and regular tests and reviews of security1 | Automated SAST, dependency, container and IaC checks in every pipeline; scheduled re-scans of released versions |
| Annex I, Part II (5)–(6): coordinated vulnerability disclosure policy and a contact address for reports1 | Disclosure policy template, security.txt, intake address routed into the triage workflow |
| Annex I, Part II (7): mechanisms to securely distribute updates1 | Signed artefacts (cosign), verified provenance, signature checks at deploy time |
| Article 13(5): due diligence when integrating third-party components, including free and open-source software1 | Component policy: allowed licences and sources, pinned versions, checks that block unknown or risky components |
| Article 14(2): early warning within 24 hours, notification within 72 hours, final report within 14 days after a fix is available, for actively exploited vulnerabilities1 | Internal workflow: detection, decision, prepared report templates and evidence collection, so your team can meet the deadlines |
Your current pipelines and processes measured against the technical requirements above.
An SBOM for every release, stored, searchable and monitored for new vulnerabilities.
Artefacts signed in CI and verified at deployment.
Triage workflow, owners, deadlines and evidence, tied to your releases.
A tested internal procedure and templates for the 24-hour, 72-hour and 14-day reports.
Documentation of each control, ready to hand to your counsel or a notified body.
The order is always the same. How long each step takes depends on your volume — the measurement in step 1 sets the price and the dates. Our free scope script gives the first numbers.
Starts from your scope report. Products, repositories, ecosystems and maintained versions mapped against the technical requirements. Plan and fixed price for the build.
SBOM, signing, scanning and vulnerability handling built into pipelines, product by product.
Disclosure policy, intake, reporting workflow; one rehearsal of an actively exploited vulnerability.
Documentation, evidence pack, training for engineering and security.
Fixed price per phase. Our free scope script counts these for you.
Starting smaller? A DevSecOps Pipeline on GitLab covers SBOM and security testing for one platform.
That is a legal question about your products and how you place them on the EU market. We don't answer it; your counsel does. We build the technical measures once scope is clear.
You will have the technical controls and evidence for the requirements listed above. Compliance as a whole is assessed by you, your counsel and, where required, a notified body.
Start with the reporting workflow and an SBOM for your current releases: without knowing what is in your products, you cannot tell whether an exploited vulnerability affects you.
Annex I sets “at the very least the top-level dependencies”. We generate the full dependency tree by default, which costs nothing extra in CI.
Run our scope script or answer five questions, and we fix the price of the assessment.