- Home
- Capabilities
- Cyber resilience (CRA)
Capability 07
Cyber Resilience & CRA Compliance
The Cyber Resilience Act makes product security a condition for the EU market. We turn it into an engineering discipline.
01Introduction
Overview
The Cyber Resilience Act (Regulation (EU) 2024/2847) applies to almost every product with software and a data connection placed on the EU market. Its reporting obligations apply since September 2026; its essential requirements apply from December 2027. For manufacturers of embedded products, it changes how products are designed, built, documented and maintained.
We approach compliance as engineering: requirements traced to design decisions, evidence generated by the build and test pipeline, and processes that work in practice, not a document written once before certification. We are an engineering consultancy, not a law firm or a notified body; legal interpretation and third-party certification remain with your legal counsel and, where required, a notified body.
02Engineering challenges
The problems we are typically asked to solve.
- 01
Unclear scope and classification
Is the product in scope, or does a sector regime apply instead? Is it a default, important (class I or II) or critical product? And which conformity assessment route follows from that?
- 02
Components nobody has inventoried
Open-source packages, vendor BSPs and third-party libraries without a software bill of materials make it impossible to know which known vulnerabilities affect a product.
- 03
Vulnerability reporting without a process
Since September 2026, manufacturers must report actively exploited vulnerabilities and severe incidents within 24 hours. That requires monitoring, triage and a disclosure process that already works.
- 04
Security updates for the whole support period
Products must receive security updates, delivered securely, for their declared support period (generally at least five years), often over constrained or intermittent links.
03Scope
What an engagement can cover.
- Applicability analysis: scope, exclusions, product category and conformity assessment route
- Gap analysis against the essential requirements of Annex I (product security properties and vulnerability handling)
- Cybersecurity risk assessment and threat modelling, documented for the technical file
- Secure-by-design implementation: secure boot, signed and fail-safe updates, hardening, secure defaults and attack-surface reduction
- SBOM generation in CI (SPDX, CycloneDX) and continuous vulnerability monitoring
- Vulnerability handling and coordinated disclosure process, including readiness for the reporting obligations
- Technical documentation and preparation for self-assessment or third-party conformity assessment
- Alignment with related frameworks: RED delegated act (EN 18031), IEC 62443-4-1/4-2, ISO/SAE 21434
04Technical expertise
Technologies and methods in practice.
- Regulation
- Cyber Resilience Act (EU) 2024/2847
- RED delegated act (EU) 2022/30
- Machinery Regulation (EU) 2023/1230
- Standards
- IEC 62443-4-1 / 4-2
- EN 18031-1/-2/-3
- ISO/SAE 21434
- ETSI EN 303 645
- Product security
- Secure boot and chain of trust
- Signed OTA updates
- Linux and Yocto hardening
- DDS Security / SROS2
- TLS and mutual authentication
- Evidence
- SBOM (SPDX / CycloneDX)
- Vulnerability management (CVE / VEX)
- Fuzzing and security testing
- Technical documentation
05Deliverables
What you receive.
- D01
CRA applicability report
Scope, product category, conformity assessment route and timeline for each product, with the reasoning behind each conclusion.
- D02
Gap analysis and roadmap
Every Annex I requirement mapped to the current product and process, with prioritised and estimated actions.
- D03
Risk assessment and threat model
A documented cybersecurity risk assessment, structured to be included in the technical file.
- D04
SBOM and vulnerability pipeline
An SBOM generated for every release and vulnerability monitoring integrated into CI.
- D05
Vulnerability handling process
Policy, roles, triage workflow and a reporting playbook for the 24-hour, 72-hour and final reports.
- D06
Technical documentation
The cybersecurity parts of the technical file, organised for self-assessment or a notified body.
06Related capabilities
Often engaged together.
Contact
Discuss cyber resilience (cra) for your system.
Describe the system and the challenge. We will tell you honestly whether and how we can help.
Start a conversation