The Cyber Resilience Act (CRA) is Regulation (EU) 2024/2847, which sets cybersecurity requirements for hardware and software products with digital elements sold in the EU. Manufacturers have had to report actively exploited vulnerabilities since 11 September 2026.
What CRA means
The CRA entered into force on 10 December 2024 and applies in stages. Article 14 reporting has applied since 11 September 2026. For an actively exploited vulnerability, the manufacturer sends an early warning within 24 hours, a notification within 72 hours and a final report within 14 days of a fix being available, through the single reporting platform run by ENISA.
The main obligations, including the essential requirements in Annex I and CE marking, apply from 11 December 2027. They fall on manufacturers, with lighter duties for importers and distributors. Buyers are not in scope unless they place products on the market. Pure software-as-a-service generally falls outside, but a vendor's desktop client, agent, mobile app or device may be covered.
The CRA gives buyers a baseline to ask about, not an individual right. Annex I requires an SBOM, a coordinated vulnerability disclosure policy and security updates, and Article 13(8) requires a support period of, in principle, at least five years. Contract terms turn these into obligations owed to you.
What to check in vendor documents
- Which of the vendor's products and versions are in CRA scope, and who the manufacturer is.
- A documented process for the 24-hour, 72-hour and final reports, with a named owner.
- How the vendor will inform users about exploited vulnerabilities and the fixes available.
- The declared support period for the version you run.
- Whether an SBOM is available to you, at least for top-level dependencies.
- A contractual duty to notify you of exploited vulnerabilities and incidents.
Related terms
- NIS2 Directive (NIS2)NIS2 is the EU directive, Directive (EU) 2022/2555, that sets cybersecurity risk management and incident reporting duties for essential and important entities in critical sectors, including supply chain security for their direct suppliers and service providers.
- Penetration test reportA penetration test report is the written result of an authorised simulated attack on a system, documenting the scope, method, findings with severity and recommendations. Vendors usually share a summary or a letter from the tester rather than the full report.
- Continuous vendor monitoringContinuous vendor monitoring is the ongoing tracking of a vendor's risk between formal assessments, using triggers such as new reports, incidents, contract or sub-processor changes, financial events and external signals, so reviews happen when risk changes.
- Vendor due diligenceVendor due diligence is the assessment an organisation carries out before contracting with a vendor, and again at renewal, to confirm the vendor can deliver the service safely and meet the legal, security, financial and operational requirements that apply.
Sources
- Regulation (EU) 2024/2847 (Cyber Resilience Act)eur-lex.europa.eu/eli/reg/2024/2847/oj
- European Commission, Cyber Resilience Actdigital-strategy.ec.europa.eu/en/policies/cyber-resilience-act
Summarised for practitioners, not legal advice. Check the source text for your own obligations.