Go back to blog

The Cyber Resilience Act Finally Has a Compliance Map

The  Cyber  Resilience  Act  Finally  Has  a  Compliance  Map

For nearly two years, European organisations preparing for the Cyber Resilience Act (CRA) have worked from a regulation long on principle and short on practical detail. On 27 July 2026, the European Commission closed much of that gap, publishing a communication and an accompanying guidance document that together clarify scope, timelines and reporting duties. For CISOs, compliance leads and IT leaders across the EU, this is the first material that reads like a route, not just a rulebook.

The timing matters. The CRA sits alongside NIS2, GDPR and DORA as part of the EU’s wider push to harden its digital supply chain from the ground up, rather than patch it after the fact. Unlike those frameworks, though, the CRA regulates the product itself โ€” the software and connected hardware an organisation buys, builds or resells โ€” which is precisely why its scope questions have proven so difficult to answer without official clarification.

What the guidance actually settles

The CRA covers “products with digital elements” sold into the EU: connected hardware, standalone software, and combinations of both. The new guidance narrows several grey areas that had stalled planning.

Open-source software is only in scope when supplied commercially, through pricing, monetised platforms, or data collection beyond security purposes. Purely community-maintained projects remain outside the regulation, though manufacturers embedding open-source components still owe due diligence and upstream vulnerability reporting.

“Substantial modification” โ€” the trigger for reassessing conformity โ€” is defined with concrete examples rather than abstract criteria, as is the expected length of vendor support periods, which manufacturers must state and justify rather than leave open-ended. The guidance also confirms that websites and remotely executed software generally sit outside scope, unless they are essential to a product’s core function โ€” a distinction many software vendors had been unable to resolve on their own reading of the regulation.

The timeline that now makes sense

Two dates anchor everything. From 11 September 2026, vulnerability and incident reporting obligations apply, ahead of full CRA application. Manufacturers who discover an actively exploited vulnerability or a severe incident must notify their national CSIRT and ENISA within 24 hours, follow up within 72 hours with an initial assessment, and file a final report within 14 days (vulnerabilities) or one month (incidents), via the EU’s Single Reporting Platform.

Full conformity requirements, including CE marking and risk assessment documentation, take effect on 11 December 2027. Non-compliance carries fines of up to โ‚ฌ15 million or 2.5% of global turnover.

Crucially, these duties apply regardless of where a company is established. A UK vendor exporting software into the EU market is as exposed as one headquartered in Frankfurt or Milan โ€” a reminder that CRA, like GDPR before it, projects EU standards well beyond its borders.

Why this reaches further than hardware

The CRA is easy to mistake for an IoT and industrial-devices regulation. It is not. Standalone security software โ€” including secure email gateways, authentication tools and detection platforms โ€” qualifies as a product with digital elements once sold commercially, which means vendors carry the same vulnerability-handling and reporting duties as any connected device maker.

For buyers, this matters directly. Business email compromise and account takeover increasingly exploit trust in a supply chain, not just a single inbox. A vendor’s CRA posture โ€” how it discloses vulnerabilities, how long it commits to support a product, how it documents conformity โ€” becomes a genuine indicator of the security discipline behind the tools an organisation relies on daily. Procurement and vendor-risk processes should start treating CRA compliance as a supply-chain signal, alongside SPF, DKIM and DMARC alignment for email-sending infrastructure.

For European organisations, obligations apply on the basis of where a product is placed on the market, not where the vendor is headquartered. A security team evaluating an email protection platform built outside the EU still needs to confirm that the vendor has a designated EU representative, a working vulnerability disclosure process, and a stated support commitment โ€” the same questions the CRA now expects manufacturers to answer for every connected product in scope.

What to do now, in order of impact

Map software and connected products against CRA scope first; this determines everything else and cannot be outsourced or estimated. Build the vulnerability and incident reporting workflow second, since the September 2026 deadline arrives well before full application and covers products already on the market. Align this workflow with existing NIS2 incident-reporting processes to avoid duplicated effort and conflicting timelines. Review contracts with software and security vendors for CRA flow-down clauses and support-period commitments. Finally, begin conformity assessment preparation for December 2027, rather than treating it as a later-stage concern.

A map, not a shortcut

Guidance does not reduce the obligation; it removes the excuse of ambiguity. Organisations that treat the coming months as preparation time, not a deadline to address later, will meet both the reporting and conformity milestones without disruption. Those waiting for a second document will find the map was the only thing missing.