On June 11, 2026, the Cyber Resilience Act (CRA) will activate its Chapter IV, which focuses on the designation of bodies responsible for the conformity assessment of digital products. This milestone establishes the infrastructure necessary for compliance without imposing immediate obligations on manufacturers. The first significant deadline for businesses will come on September 11, when they will be required to notify authorities about actively exploited vulnerabilities. For Chief Information Officers (CIOs) and Chief Information Security Officers (CISOs), the coming months will revolve around distinguishing between these compliance infrastructure milestones and the actionable obligations, amidst a European regulatory landscape that includes NIS2, DORA, the CRA, and the AI Act, all culminating by 2028.
Since its adoption, the European regulation on cyber resilience has been reshaping the security of products incorporating digital elements, ranging from embedded software to connected devices. Its implementation is not a one-time event but unfolds gradually over several years, with each phase activating distinct obligations. This staggered approach has led to misunderstandings, as a single date for enforcement does not mean all provisions of the regulation become applicable simultaneously.
The June 11, 2026 date has been widely regarded as a pivotal moment. However, it merely triggers a preparatory mechanism that is essential for the operational framework, without imposing any direct requirements on manufacturers of digital products. Understanding what this date entails—and what it does not—is crucial for effectively allocating compliance efforts within IT departments.
What June 11 Actually Activates
Chapter IV of the regulation organizes the setup and notification of conformity assessment bodies. In France, the National Cybersecurity Agency (ANSSI) will act as the notifying authority responsible for evaluating, overseeing, and notifying these bodies, based on an accreditation issued by the French Accreditation Committee. The period from June to December 2026 will see the accreditation process undertaken, followed by the commencement of notifications to these bodies by the agency.
Essentially, this phase constructs the necessary infrastructure for the compliance regime rather than imposing obligations on product manufacturers. Without authorized bodies to assess compliance, future requirements for marking and evaluation would remain unenforceable. Thus, June 11 will establish the players who will operationalize the system, with tangible effects for manufacturers only materializing when substantive obligations come into force in 2027.
The confusion arises from a cursory reading that equates this date with the general applicability of the regulation. For IT departments, the distinction is clear: mobilizing resources now for compliance marking would be premature, while preparing for the incident notification channels has become urgent.
The September Deadline: The One That Binds Companies
On September 11, 2026, a direct obligation will take effect for manufacturers. By this date, they must notify authorities of actively exploited vulnerabilities and significant incidents affecting the security of their products. The notification regime operates under strict deadlines, requiring an early warning within twenty-four hours, an incident report within seventy-two hours, and a final report within one month.
These notifications will be processed through a single platform managed by the European Union Agency for Cybersecurity (ENISA), which will then forward the information to the appropriate national coordinators, such as CERT-FR for France. This architectural element is crucial for CISOs, as it centralizes the reporting of vulnerabilities at a European scale and raises questions about the confidentiality of information shared regarding unpatched vulnerabilities.
The notification timelines of twenty-four hours, seventy-two hours, and one month align with those already familiar to entities regulated under the NIS2 directive. This alignment of notification formats has been pursued by European authorities, with the NIS2 cooperation group adopting common models for incident reporting on May 26, 2026, to reduce administrative burdens by enforcing a uniform format.
An Overlapping European Calendar
The CRA cannot be viewed in isolation; it joins a broader regulatory framework with deadlines that overlap and cascade. The NIS2 directive is awaiting transposition into French law through the Resilience Act, with enactment expected in the first half of 2026, following France’s previous deadline extension past the original European target of October 2024. This Act joins NIS2 and DORA as pillars of European cyber resilience, with key dates cascading through 2028.
DORA, meanwhile, has been directly applicable in the financial sector since January 17, 2025, without national transposition since it is a regulation. Its requirements for small financial entities will become applicable from January 17, 2027. One noteworthy change is the direct supervision of critical third-party providers, placing major cloud platforms, service providers, and digital infrastructure suppliers under the scrutiny of European financial authorities.
The AI Act adds further complexity, with a phased rollout of obligations. Requirements for high-risk AI systems will become enforceable in August 2026, as businesses have been preparing for these regulatory requirements for several months. For IT departments, the challenge lies in interpreting these texts in tandem, as they share a notification and risk governance logic without aligning perfectly in scope or timelines.
French support for NIS2 provides a useful anchor. The agency released its cybersecurity framework on March 17, 2026, detailing recommended measures to meet the security objectives set forth by the directive. A dedicated portal, now operational on the agency’s site, offers regulated entities a path for identification, self-assessment tools, and documentation templates. These resources, designed for NIS2, indirectly aid preparations for the CRA, as the notification logic overlaps with that of the directive.
However, the overlap of these calendars poses a risk of misinterpretation. Each regulation has its own scope, entities covered, and thresholds, and an organization may fall under multiple regimes based on its activities. A financial entity that also manufactures connected products finds itself at the intersection of DORA, NIS2, and the CRA, confronting differing notification triggers. Mapping these overlapping obligations is a prerequisite for organizing coherent compliance efforts.
What CIOs and CISOs Must Prepare Now
Operational priorities are shifting from distant compliance marking to the now imminent incident notification chains. Organizations that manufacture or integrate products containing digital elements should begin mapping their notification surface, identifying vulnerabilities that may be actively exploited, and establishing internal procedures to comply with the twenty-four and seventy-two-hour deadlines.
The alignment of formats between the CRA and NIS2 provides a rationalization lever. A company already subject to NIS2 has a reusable procedural foundation for the CRA, provided it has clearly defined which products and incidents are governed by each regulation. This cross-mapping avoids duplication of efforts and minimizes the risk of missed or misdirected notifications.
Governance remains a critical aspect. The centralization of notifications through the European agency’s platform necessitates that CISOs anticipate issues of confidentiality and information sharing regarding vulnerabilities. Mastering these signals aligns with managing vulnerabilities, a shared responsibility between CIOs and CISOs. The regulatory calendar that structures European cybersecurity extends through 2028, and while the upcoming milestones are not the most stringent, they are pivotal in establishing the foundational strength for future compliance.



