On 11 September 2026, the EU Cyber Resilience Act’s first major operational deadline arrived on schedule, and so did the infrastructure meant to support it. Manufacturers of products with digital elements became legally required, under Article 14, to report actively exploited vulnerabilities and severe incidents, and on that same day ENISA brought the Single Reporting Platform (SRP) online at portal.cra-srp.enisa.europa.eu.¹² Most compliance commentary still points European buyers to 11 December 2027, when the CRA becomes generally applicable, and that remains the right date for most of the regulation. Article 14 was carved out fifteen months earlier, on its own separate application date, and it applies to products already placed on the EU market before 11 December 2027, not only to products introduced after the reporting deadline.³
That much is a genuine achievement: the obligation and the tool arrived on the same day. It also removes one excuse, though not the harder question of whether manufacturers can use the platform under real time pressure. ENISA calls the launch an initial operating capability it will keep expanding based on operational experience.² At launch, submission runs through a web form rather than a system-to-system interface, one notification per event even across several product lines, and in English only.⁴ A public URL is necessary, but it is not the same as a manufacturer with no prior incident-reporting experience finding the right CSIRT, assembling the right information, and filing a usable report within 24 hours of first becoming aware.
That gap matters most to a group that has had comparatively little written for it: the European companies importing electronics, industrial equipment, and embedded systems from Asian manufacturers, including SMEs in Taiwan, Vietnam, and elsewhere that may not yet have operationalised the September reporting requirement. Two features of the CRA pull the importer into this problem, whether or not the importer intended to own it.
Reporting duty, reporting route: not the same thing
Article 14 assigns the reporting duty itself to the manufacturer. A manufacturer with an EU-based main establishment reports through the CSIRT coordinator in that member state.³ For a manufacturer without one, a fallback cascade in Article 14(7) determines which member state’s CSIRT becomes the reporting destination: first, the state where the authorised representative acting for the manufacturer’s highest number of products is established; failing that, the state of the importer placing the highest number of that manufacturer’s products on the EU market; failing that, the largest distributor’s state; failing that, wherever the most users are located.⁵ Appointing an authorised representative is optional: Article 18 uses “may,” not “shall”.⁶ A manufacturer that judged 2027 comfortably far away may not have one, in which case the cascade quietly promotes the largest EU importer’s jurisdiction into that destination: call it the reporting anchor, shorthand for jurisdiction and CSIRT selection, not a transfer of legal responsibility.
To be precise about what that does and does not mean: it does not make the importer the Article 14 reporting party, and it does not transfer the manufacturer’s legal duty. It does make the importer’s jurisdiction the effective route by which the manufacturer’s notification reaches a CSIRT, giving the importer a direct, practical stake in whether the manufacturer can produce a report on time. On the live platform this is no longer abstract: it is a field the manufacturer’s representative fills in when registering, and getting it wrong there is itself an avoidable delay.
This discussion assumes the ordinary case: an EU company acting as importer of another company’s product. Where an importer places a product under its own name or brand, or substantially modifies it, Article 21 treats it as the manufacturer instead, with the fuller Article 13 and Article 14 obligations that follow.⁷
The obligations that have not arrived yet
It is tempting to reach next for Article 19, the importer’s own general obligations: verifying conformity assessment and CE marking, keeping the declaration of conformity on file for at least ten years after the product is placed on the market or for the support period, whichever is longer, informing the manufacturer of vulnerabilities without undue delay, and alerting market surveillance authorities where a product presents a significant risk.⁸ These are not live obligations on 11 September 2026. Under Article 71, only Article 14 and Chapter IV are pulled forward; Article 19 follows the CRA’s general application date of 11 December 2027.³⁸
The same is true, and easy to miss, of Article 13’s general obligations: a single point of contact for vulnerability reports, and the Annex I, Part II duties to maintain a coordinated disclosure policy and a public contact address.⁹ Neither is accelerated. A manufacturer with a live Article 14 clock has no separate statutory duty, yet, to have a named security contact or a documented policy; Article 14 imposes the notification deadline itself, and little else. That combination, a hard deadline with no attached process mandate, is why the practical question outweighs the legal one: a manufacturer cannot be found in breach of Article 13 today for lacking a formal policy, but it can still miss the Article 14 clock for want of a reliable way to notice a report, decide what it means, and route that decision to the right person within 24 hours. The controls Article 13 and Annex I will require by law from December 2027 describe, almost exactly, the capability a manufacturer needs today to hit that deadline voluntarily: a readiness benchmark worth asking about now, not yet a legal requirement to cite against a supplier.
Whether that information moves fast enough from importer to manufacturer to support the Article 14 clock is not an Article 19 or Article 13 question at all: it is operational. An importer is not itself the source of a vulnerability report, a customer or researcher usually is, but it may be the party through which such information first reaches the manufacturer, and whether it arrives in hours rather than weeks depends on whether an intake process like the one Article 13 will eventually mandate already exists in practice. The CRA does not prescribe how a manufacturer becomes aware of a reportable event, only what it must do once it does.⁹¹⁰
The CRA Supplier Readiness Test
None of what follows is a CRA legal checklist. Nothing in the regulation requires an importer to audit a supplier’s readiness, and Article 14 sets no manufacturer-to-importer escalation deadline of its own. This is the author’s own diagnostic, built to test whether the operational dependency above is actually manageable, and it does not require waiting for a supplier’s next audit cycle. Five questions, put to a supplier now, do most of the work:
- Security contact. Who at the manufacturer actually receives and triages a security report: a named role, not a general assurance that “we have a process”?
- Disclosure policy. Ahead of the 2027 requirement, does the manufacturer already maintain a documented coordinated vulnerability disclosure policy and a public contact address?
- Escalation speed. What is the manufacturer’s committed window for telling the importer once it becomes aware of something reportable: hours, or “whenever we get to it”?
- Reporting route. Has an EU authorised representative been appointed, and can the manufacturer state, not guess, which member state’s CSIRT its notifications would route to on the live platform?⁵
- The drill. Can the manufacturer walk through, concretely, the workflow it would run from first credible report to the right decision-maker, with clear ownership assigned for the 24-hour early warning, the 72-hour notification, and the applicable final report: 14 days after a corrective measure is available for an actively exploited vulnerability, or one month after the 72-hour notification for a severe incident?¹
The fifth question is the one that separates readiness from paperwork. “Yes, we have a process” is not evidence of anything. A supplier that can answer question five concretely gives an importer stronger evidence that the first four are actually operating, not merely documented, than any policy binder can. A supplier that cannot has not, whatever its policy documents say.
The stress test the launch does not settle
The platform going live on schedule closes one gap: before 11 September, it was fair to ask whether manufacturers were being held to a deadline no functioning system could meet. That question now has an answer: ENISA delivered. What it does not close is the gap no platform will ever fix: whether a given importer’s Asian supply chain can move information fast enough to support a legal clock now enforceable through a system that actually works. September 2026 did not test whether a supplier had finished CRA compliance; nothing requires that yet. It tested, and with every report filed continues to test, whether the supply chain can communicate under pressure, which makes Article 14, treated correctly, one of the earliest and most focused stress tests an EU importer can run, whether in-house or with outside advisory support, before the broader conformity regime arrives in December 2027.
References
¹ Regulation (EU) 2024/2847 of the European Parliament and of the Council of 23 October 2024 (Cyber Resilience Act), Article 14. Full text: https://eur-lex.europa.eu/eli/reg/2024/2847/oj/eng
² ENISA, “The CRA Single Reporting Platform is launched,” 11 September 2026: https://www.enisa.europa.eu/news/the-cra-single-reporting-platform-is-launched
³ Regulation (EU) 2024/2847, Articles 69(3) and 71.
⁴ Help Net Security, “ENISA launched the CRA Single Reporting Platform for actively exploited vulnerabilities,” 14 September 2026: https://www.helpnetsecurity.com/2026/09/14/enisa-cra-single-reporting-platform/
⁵ Regulation (EU) 2024/2847, Article 14(7).
⁶ Regulation (EU) 2024/2847, Article 18(1).
⁷ Regulation (EU) 2024/2847, Article 21.
⁸ Regulation (EU) 2024/2847, Articles 19 and 71.
⁹ Regulation (EU) 2024/2847, Article 13(8) and (17), Annex I Part II points (5)-(6), and Article 71 (confirming these obligations are not among the provisions accelerated ahead of 11 December 2027).
¹⁰ European Commission, “Commission publishes new guidance to support timely Cyber Resilience Act implementation,” 27 July 2026: https://digital-strategy.ec.europa.eu/en/library/commission-publishes-new-guidance-support-timely-cyber-resilience-act-implementation






