SBOM and vulnerability management: the practical foundation of CRA compliance
Without visibility into a product's components you cannot manage vulnerabilities. Why an SBOM is at the core of CRA compliance.
The Cyber Resilience Act (Regulation EU 2024/2847) is not introduced on a single date. It rolls out in phases, and each one means a different type of obligation for manufacturers, importers and distributors. If you plan your preparation around the final deadline only, you risk being caught off guard by the earlier obligations.
The regulation entered into force and the transition period began. Legally, CRA is in effect – only its main obligations apply later. For companies this means one thing: the clock is already running and this is the official starting line for preparation.
This date is often underrated in CRA discussions. Reporting obligations start before full compliance. Manufacturers must report, within short deadlines:
Reports go to ENISA via a single platform and follow a multi-stage pattern – from an early warning to a detailed report. To meet these deadlines, a company needs processes and templates ready in advance, not only at the moment of an incident.
From this date, all products with digital elements placed on the EU market must meet CRA requirements, have complete technical documentation, a completed conformity assessment, the EU declaration of conformity and the CE marking. A product that does not meet these conditions cannot legally be placed on the market.
CRA compliance is not a document written at the last minute. It is the result of processes that must run for months in advance:
Related service
CRA Consulting
Without visibility into a product's components you cannot manage vulnerabilities. Why an SBOM is at the core of CRA compliance.
CRA splits obligations by role. Find out which one you are in – and when the role changes unexpectedly.
A free consultation will quickly show you where you stand and the shortest path to compliance.
Book a consultation