The EU Cyber Resilience Act reaches its first 2026 application milestones
Notified-body provisions began applying in June 2026 and vulnerability-reporting provisions follow in September, while the regulation's general application remains December 2027.
Editorial figure by OT Defense Review. Source context: EUR-Lex.
What the source establishes
Regulation (EU) 2024/2847 is in force. Chapter IV applies from June 11, 2026. Article 14 applies from September 11, 2026, while the regulation generally applies from December 11, 2027. OT Defense Review records the named source, date, status, affected market layer, and evidence class separately so an announcement, authority record, or provider study is not silently converted into an independently verified operating conclusion.
This record abstracts dates and high-level scope from the official text; it is not legal advice or a conformity conclusion. The maintained record distinguishes the fact of the publication or event from forward-looking statements, provider characterization, later implementation, and conditions that the source does not establish.
The industrial-defense consequence
Industrial product manufacturers and their customers need role, product, classification, support-period, vulnerability-handling, reporting, conformity, technical-documentation, supplier, and market-placement records tied to the staged dates. A generic CRA-ready label cannot preserve those distinctions.
The practical review should follow the change into system boundaries, accountable roles, asset populations, architecture, data collection, access, detection, response, recovery, provider dependencies, retained evidence, and the operating constraints that could alter safety or reliability. That is where a headline becomes a defensible program decision.
What asset owners should test next
Require the supplier to name the legal entity, role, product and version population, scope rationale, applicable date, conformity path, support period, vulnerability intake, reporting responsibility, customer communication, update process, end-of-life treatment, and evidence available to the buyer.
Application to a specific product depends on the controlling text, exclusions, classification, economic-operator role, harmonized standards, later acts, and facts. Preserve which facts came from the authority or organization, which behaviors were independently observed under a disclosed method, which depend on configuration or services, and which remain not established. Do not use a public article as authorization to probe, scan, block, patch, isolate, or reconfigure a live industrial environment.
Enterprise buyer test
Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.
A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.
What we will watch next
OT Defense Review will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.