The EU Cyber Resilience Act is usually framed as a product compliance regime: technical documentation, vulnerability handling, conformity assessment and market surveillance for products with digital elements. One part arrives earlier. From 11 September 2026, manufacturers must report actively exploited vulnerabilities and severe security incidents. The Act's broader product obligations phase in later. Companies will therefore be judged on how quickly and coherently they report while many processes meant to support the Act are still being built.
For legal teams, this is not a narrow security task to delegate to engineering. It is an exercise in evidence, timing and coordination across regulatory, commercial and governance functions. A manufacturer that can detect a vulnerability but cannot decide, document and notify within the required window has a legal problem, not merely a technical one.
An early duty ahead of the main regime
The reporting obligations are intended to give authorities and users early warning of security problems already being exploited. The Act distinguishes between actively exploited vulnerabilities and severe incidents affecting the security of a product, and it sets short clocks for initial notification, with fuller reporting to follow. The precise mechanics depend on implementing arrangements, but the direction is clear: notification must be fast and accurate enough to withstand later scrutiny.
This creates an awkward position. The reporting duty becomes live before the conformity assessment, documentation and lifecycle processes that the main obligations assume are fully operational. Companies may be reporting on products whose security governance is still being mapped, using untested escalation routes and relying on suppliers who have not been asked for information on the timetable the Act demands. Reporting is a legal act, not a security operations milestone.
One incident, several disclosure regimes
A serious security incident rarely engages a single legal regime. A ransomware attack affecting a connected product may also be a personal data breach under the GDPR, prompting notification to a supervisory authority within 72 hours where the threshold is met. If the manufacturer is also an essential or important entity within the scope of NIS2, separate incident reporting duties may apply, with their own timing and content requirements. Sector-specific rules for medical devices, financial services or telecommunications may add further layers.
Contractual obligations sit alongside the regulatory ones. Enterprise customers increasingly expect notification of incidents and vulnerabilities within defined periods, often shorter than statutory clocks, and service level agreements may impose cooperation duties and remediation timetables. The risk is inconsistency. A company that tells a customer one thing, a data protection authority another and a market surveillance authority something else creates a record that will be difficult to defend. Legal teams need a single incident assessment that maps the facts onto each applicable regime, identifies where the clocks start and records why particular notifications were or were not made. That assessment should be produced once and reused, not rebuilt by each function under time pressure.
The evidentiary record is the real deliverable
Reporting duties are usually analysed in terms of deadlines. The more durable requirement is documentary. Regulators, customers and courts will want to know when the manufacturer first became aware of a vulnerability or incident, what information was available at that moment, how significance was assessed, who was informed internally and externally, and what was done to contain and remediate the problem.
Those questions are difficult to answer after the fact unless records are created as the event unfolds. Security tools generate logs, but logs are not a decision record. A ticketing system may show that a vulnerability was triaged, but not why it was judged not to require notification. An email thread may capture a debate, but may also be incomplete, inconsistent or difficult to retrieve.
Legal teams should therefore treat the incident file as a legal artefact from the outset. That means a defined template capturing the timeline, the assessment against each reporting threshold, the notification decisions and the reasoning behind them, and the remediation steps taken. It means retaining underlying technical evidence in a form that can be produced later, and ensuring the record distinguishes facts, assessments and legal advice. Commercial exposure may also turn on what the manufacturer knew and when.
Supplier visibility and open-source dependencies
A manufacturer cannot report what it cannot see. Modern products embed third-party components, commercial libraries and open-source software maintained by communities with no contractual relationship to the manufacturer. The Act places obligations on manufacturers in respect of the whole product, including integrated components, which makes supply chain visibility a compliance prerequisite rather than a procurement nicety.
Contracts with suppliers should require prompt notification of known exploited vulnerabilities and security incidents affecting supplied components, cooperation with the manufacturer's reporting obligations, and sufficient technical information to allow assessment. Those requirements need to be enforceable and matched by a realistic expectation of how quickly information will flow. A supplier clause that promises notification within a period longer than the manufacturer's own reporting clock offers little protection.
Open-source components present a harder problem, because contractual leverage is often absent. Manufacturers need a documented approach to monitoring the projects they depend on, identifying critical components and assessing the significance of disclosed vulnerabilities. Where a commercial distributor or maintainer stands behind an open-source component, a contractual route may be available; where it does not, the manufacturer's own monitoring and assessment record becomes the primary evidence of diligence. Supplier notifications should be logged with the date and content preserved.
Ownership, escalation and privilege
Short reporting clocks expose governance weaknesses quickly. A decision that requires sign-off from several functions, or that waits for a weekly committee, will not survive a deadline measured in hours. Manufacturers need a named owner at board or executive level for the reporting process, a documented escalation route that operates at any hour, and pre-agreed criteria that allow front-line teams to recognise a potentially reportable event and route it immediately.
Legal should be embedded in that route rather than consulted at the end. Early involvement allows the company to assess all applicable regimes at once, consider whether legal advice should be sought in a manner that preserves privilege, and ensure the record distinguishes legal analysis from operational fact. Privilege questions are rarely straightforward in a multi-jurisdictional incident, and practical protections depend on how communications are structured and who is included.
Board-level ownership also matters because reporting decisions carry risk in both directions. Late or incomplete notification can attract regulatory sanction and customer claims; over-notification can create unnecessary exposure and erode confidence. A governance framework that records the reasoning behind both kinds of decision is more defensible than one that simply follows the most cautious path.
Preparing before the clock starts
The September 2026 deadline rewards preparation well before any incident. Manufacturers should map which products and components fall within scope, identify the regimes that could be engaged by a single event, and build a single assessment and notification workflow that serves all of them. They should test the escalation route, including out of hours, and confirm that supplier contracts deliver information quickly enough to be useful.
Above all, they should design the record now. The companies that manage the reporting duty well will be those that can show, months or years later, exactly what they knew, when they knew it and why they acted as they did. That is a legal capability as much as a security one, and it is the part of the Cyber Resilience Act that arrives first.
