EU Cyber Resilience Act Reporting Is Live: A 24-Hour Readiness Plan for U.S. Software Makers
Since September 11, 2026, the EU CRA requires software makers to report exploited vulnerabilities within 24 hours. What U.S. vendors need ready now.
- Author
- Ackatec
- Published
- Reading time
- 6 min read
- Cyber Resilience Act
- Vulnerability management
- Product security
- Incident readiness
- Compliance readiness
- Penetration testing
Since September 11, 2026, manufacturers of software and connected hardware sold in the European Union have had to report actively exploited vulnerabilities and severe security incidents in those products within 24 hours of becoming aware of them. It is the first manufacturer obligation of the EU Cyber Resilience Act (CRA) to take effect, and it reaches U.S. vendors with EU customers, not only European firms. ENISA, the EU cybersecurity agency, launched the Single Reporting Platform (opens in a new tab) the same day to receive those reports.
The short answer: if your product is sold in the EU, you need a named person who can file a report on the EU platform within 24 hours, a fast way to decide whether a vulnerability is being exploited, and a plan to tell affected customers what to do.
What is the Cyber Resilience Act?
The Cyber Resilience Act, Regulation (EU) 2024/2847 (opens in a new tab), sets cybersecurity requirements for "products with digital elements," meaning hardware and software products and their remote data processing solutions, across their lifecycle. It applies in stages. Reporting obligations under Article 14 have applied since September 11, 2026. The main requirements, including the security and vulnerability handling requirements, conformity assessment, and CE marking, apply from December 11, 2027.
The design and documentation work can be planned over the next year. The reporting duty cannot wait.
Does the CRA apply to U.S. companies?
Yes, when they place products with digital elements on the EU market, wherever they are headquartered. A U.S. company that ships desktop software, a mobile app, firmware, or a connected device to EU customers is generally a manufacturer under the CRA, unless a sector exclusion applies, such as for medical devices or motor vehicles covered by their own EU rules.
Pure software as a service is generally outside the CRA. Recital 12 (opens in a new tab) of the regulation explains that cloud services designed outside a product manufacturer's responsibility are not in scope and that the NIS2 Directive covers SaaS, PaaS, and IaaS instead. Cloud features that make a product work, such as the backend a manufacturer runs so customers can control its device remotely, are in scope. Many vendors sell both, so scope needs to be decided product by product.
What must be reported, and when?
Two kinds of events trigger a report:
- Actively exploited vulnerability: a vulnerability for which there is reliable evidence that a malicious actor has exploited it in a system without the owner's permission.
- Severe incident: an incident that affects, or could affect, the product's ability to protect the availability, authenticity, integrity, or confidentiality of sensitive or important data or functions, or that has led or could lead to malicious code running in the product or in a user's systems.
Under Article 14, as summarized in ENISA's platform FAQ (opens in a new tab), the deadlines run from the moment you become aware:
- Early warning, within 24 hours: an initial alert, including where known the EU countries the product is sold in.
- Notification, within 72 hours: general information, an initial assessment, and mitigations users can take.
- Final report for an exploited vulnerability, 14 days after a fix or mitigation is available: severity, impact, attacker information if known, and the fix.
- Final report for a severe incident, 1 month after the 72-hour notification: root cause, severity, and applied mitigations.
When does the 24-hour clock start?
The clock starts when the manufacturer becomes aware of the exploitation or incident. ENISA's FAQ adds two practical points. A vendor that learns of exploitation on or after September 11, 2026 must report it even if the underlying flaw was already known. And the duty covers in-scope products already on the market, not only new releases.
Signals of exploitation often arrive through a researcher's email, a customer support ticket, or a threat intelligence alert. Each of those channels needs a path to someone who can make the call within hours.
Who files the report, and where?
Reports go through the Single Reporting Platform to the national CSIRT (computer security incident response team) designated as coordinator and reach ENISA at the same time. The ENISA FAQ flags details U.S. vendors should plan for:
- Choosing the right CSIRT. Without a main establishment in the EU, you pick the member state in this order: where your authorised representative acts for the most products, then where your importer places the most products, then where your distributor sells the most, and finally where you have the most users. Picking the wrong CSIRT may invalidate the report.
- People, not systems. Filers are "Assigned Representatives" who sign in with a personal EU Login account protected by multifactor authentication. Each manufacturer has one Primary representative and up to 20 Secondary ones.
- No API yet. At launch, notifications must be submitted through the web interface.
- A conservative counter. The platform currently shows the 72-hour notification as due 48 hours after the early warning is submitted, so a report may appear overdue earlier than the legal deadline.
ENISA suggests registering the manufacturer only when you need to file, but EU Login accounts can be created in advance, which removes a step from your first 24 hours.
What about customers?
Article 14(8) (opens in a new tab) requires the manufacturer to inform impacted users, and where appropriate all users, about the vulnerability or incident and any mitigations they can apply, where appropriate in a structured, machine-readable format. It sets no hour count, but if the manufacturer does not inform users in a timely manner, the coordinating CSIRT may inform them instead. Your security advisory process is now part of your compliance posture.
How to get ready this quarter
Map products to the EU market
List every product sold or downloadable in the EU, who distributes it, and whether it is software you ship or a service you host. That map decides scope and your CSIRT. Compliance readiness work can turn it into an owned register that stays current as products change.
Name and rehearse your reporters
Pick a Primary and at least one Secondary Assigned Representative, create their EU Login accounts with multifactor authentication, and run a tabletop exercise that ends with a drafted early warning. Incident readiness exercises are the place to test the handoff from engineering to legal to the person filing, including on a weekend.
Write an exploitation triage rule
Define what "reliable evidence of exploitation" means for your team, such as a customer's forensic finding or credible threat intelligence, and document who decides and how fast.
Find the flaws before attackers do
A flaw fixed before release cannot be exploited in a customer's environment and trigger a report. Focused penetration testing of your product, its update channel, and its cloud backend shows where an attacker would start. Testing reduces risk but does not guarantee that no exploitable flaw remains.
Prepare customer advisories
Keep an advisory template, a customer contact list by product, and a channel for publishing mitigations quickly, ideally in a machine-readable format your customers can automate.
CRA reporting readiness checklist
- Which of our products are sold or downloadable in the EU, and which are pure SaaS?
- Which national CSIRT is our coordinator, and why?
- Who are our Primary and Secondary Assigned Representatives, and do they have EU Login with multifactor authentication?
- Who can declare a vulnerability actively exploited, and how quickly?
- Could we file an early warning within 24 hours on a weekend?
- How would we tell affected customers what to do?
- When did we last test the product as an attacker would?
If several answers are uncertain, talk with Ackatec before the first report is due.
References
- ENISA, The CRA Single Reporting Platform is launched (opens in a new tab) (September 11, 2026)
- ENISA, CRA Single Reporting Platform: Frequently Asked Questions (opens in a new tab) (updated October 15, 2026)
- EUR-Lex, Regulation (EU) 2024/2847, the Cyber Resilience Act (opens in a new tab)
- Cyber Resilience Act text, Preamble recitals 11 to 20 (opens in a new tab)
- OpenSSF Global Cyber Policy Working Group, CRA Reporting Obligations for Manufacturers (opens in a new tab)
