Know what is on your site before a plaintiff’s firm does.Free website scanScan Your Site
Log in Sign up Book a demo
Home› Editorial› The EU’s Cyber Resilience Act Guidance Is Now…
COMPLIANCE

The EU’s Cyber Resilience Act Guidance Is Now in the Official Journal: What It Clarifies for Manufacturers

The European Commission’s first guidance on the Cyber Resilience Act appeared in the Official Journal of the European Union on November 17, 2026, as Communication C/2026/6013.

Nov 17, 2026 8 min read

Know what’s on your site before a plaintiff’s firm does

A free privacy audit shows which cookies, pixels and trackers are running — and which ones commonly appear in privacy claims.

Get My Free Audit

The European Commission’s first guidance on the Cyber Resilience Act appeared in the Official Journal of the European Union on November 17, 2026, as Communication C/2026/6013. The text is not new: the Commission adopted and posted it on July 27, 2026, after a public consultation on a draft that ran from March 3 to April 13. Formal publication still matters, because the 61-page document is now the reference point national market surveillance authorities and manufacturers will quote. It is not binding, and only the Court of Justice can give an authoritative reading of the law, but it sets out how the Commission itself reads the regulation, with 67 worked examples. For companies that make connected devices, apps or other software, it answers several questions that have been holding up compliance planning, and it explains where the CRA meets the GDPR and NIS2.

TL;DR

  • The Commission’s Cyber Resilience Act guidance, first released on July 27, 2026, was published in the Official Journal on November 17, 2026 as C/2026/6013 and is non-binding.
  • It covers scope, open-source software, substantial modifications, support periods, important products, risk assessment, remote data processing and the reporting duties that have applied since September 11, 2026.
  • It defines when a manufacturer “becomes aware” of an incident in line with NIS2 rules and EDPB breach-notification guidelines, and leaves the CRA’s interplay with the AI Act and DORA for possible future guidance.

Low-poly 3D router, security camera, thermostat and laptop linked by glowing lines under a translucent geometric dome deflecting red shards

Where the CRA timeline stands

Regulation (EU) 2024/2847 entered into force in December 2024 and sets mandatory cybersecurity requirements across the life of “products with digital elements,” from baby monitors and routers to desktop software and mobile apps. It phases in over three years:

  • June 11, 2026: rules on notifying conformity assessment bodies started to apply.
  • September 11, 2026: manufacturers became obliged to report actively exploited vulnerabilities and severe incidents affecting their products.
  • December 11, 2027: the main obligations apply, including the essential security requirements, vulnerability handling, conformity assessment and CE marking.

The reporting clock is already running, which is why the guidance’s chapter on reporting is the most urgent part for most teams.

Five clarifications manufacturers should act on

  1. Reporting covers products you shipped years ago. The guidance confirms that the duty to report applies from September 11, 2026 to every in-scope product, including those placed on the market before December 11, 2027, and that it continues after a product’s support period ends. There is no duty to report exploitation the manufacturer already knew about before September 11, 2026. But if a known vulnerability is first exploited, or first found to be exploited, after that date, it must be reported.
  2. “Becoming aware” has a test. A manufacturer is aware when, after a prompt initial assessment of a suspicious event, it has a reasonable degree of certainty that a vulnerability in its product is being actively exploited or that a severe incident has compromised the product’s security. From that moment it has 24 hours for an early warning and 72 hours for a fuller notification, both sent at the same time to the coordinating CSIRT and to ENISA. The final report is due 14 days after a fix or mitigation is available for an exploited vulnerability, or one month after the 72-hour notification for a severe incident.
  3. Third-party components count when the flaw is live in your product. If an actively exploited vulnerability comes from a component you integrated, you must report it. If the flaw cannot be exploited in your product, for example because the vulnerable code is unreachable, or has not been exploited there, mandatory reporting does not apply, although voluntary reporting is possible.
  4. Most security patches are not “substantial modifications.” A security update that does not change a product’s intended purpose or add new risks does not restart conformity obligations, even if it involves major technical changes. An update can cross the line if it materially changes data flows or adds new externally reachable interfaces. One example in the guidance: a fix that replaces on-device file encryption with a mandatory upload to the manufacturer’s remote encryption service.
  5. Five years is a floor, not a default. The support period must reflect how long people can reasonably be expected to use the product, and five years is not automatically right. Buyers must be told the end date, at least the month and year, at the time of purchase, and users should be notified when support ends where that is technically feasible.

Where the CRA meets the GDPR

The CRA is a product-safety law, not a data protection law, but the guidance links the two in places privacy teams will recognize.

  • One awareness standard for two clocks. The Commission says its definition of “becoming aware” is aligned with Section II(A) of the European Data Protection Board’s Guidelines 9/2022 on personal data breach notification. An incident that compromises a connected product and exposes personal data can trigger both the CRA’s 24-hour early warning and the GDPR’s 72-hour notice to a supervisory authority. Using the same trigger in both workflows reduces the risk of missing one deadline while debating the other.
  • Personal data can make open source “commercial.” Free and open-source software falls outside the CRA unless it is supplied in the course of a commercial activity. The guidance says that requiring users to allow processing of their personal data for purposes other than security, compatibility or interoperability is a form of monetization. Its example is a free fitness app whose use depends on data processing for targeted advertising or analytics; that app is in scope.
  • Telling users is risk-based. The CRA requires manufacturers to inform affected users about exploited vulnerabilities and severe incidents. The guidance says this does not always mean public disclosure: for sensitive deployments, details can be limited to the customers concerned until a fix is out.

None of this replaces GDPR duties. It does mean the security-by-design work the CRA demands overlaps heavily with privacy by design, and that product security and privacy incident playbooks should be written together.

NIS2, cloud back ends and other EU rules

The longest new chapter covers “remote data processing solutions” (RDPS), the cloud side of a connected product. Data processing at a distance counts as part of the product when its absence would stop the product performing one of its functions and the software was designed and developed by the manufacturer or under its responsibility. A website that only hosts manuals is not an RDPS; an authentication portal that issues the tokens a device needs to operate can be. Manufacturers should declare their RDPS and any third-party remote services in each product’s technical documentation.

Cloud providers themselves are regulated under NIS2, and the guidance draws on that. As evidence of a cloud supplier’s security, manufacturers can rely on compliance with NIS2 Implementing Regulation (EU) 2024/2690, DORA, a European cybersecurity certification scheme, or ISO/IEC 27017 or 27001. It also suggests writing security guarantees, including vulnerability handling, into service level agreements. Teams that already vet API security and vendor controls for privacy reasons can extend that work.

Two other interactions are worth noting:

  • Radio equipment certificates carry over. Where a product already holds an EU type-examination certificate under the Radio Equipment Directive’s cybersecurity delegated act (Regulation (EU) 2022/30), that certificate stays valid for the risks it covers. Manufacturers only need to assess and mitigate any CRA gaps it does not address.
  • The AI Act and DORA are still open. Contrary to some summaries, this guidance does not settle how the CRA fits with the AI Act or DORA. The Commission says it may address those questions in future guidance under Article 26.

Companies tracking the growing number of EU digital laws, each with its own representative and contact rules, should treat the CRA as another layer rather than a replacement.

Practical steps for the next twelve months

  • Map every product on the EU market, including discontinued lines, against the reporting duty, since support status does not end it.
  • Write down your “awareness” decision point and make the CRA, NIS2 and GDPR clocks start from the same triage record.
  • Inventory third-party and open-source components and record whether known flaws are reachable in each product.
  • Set support periods from expected use time and get the end date onto packaging and product pages.
  • List the cloud services each product depends on and collect evidence of their security.
  • For legacy designs you will keep selling after December 11, 2027, run the Article 13 risk assessment now. The guidance says redesign is not automatically required if existing controls address the risks.

Device categories that have already drawn scrutiny, such as surveillance cameras and other smart-home systems, are a sensible place to start.

FAQ

Is the November 17 publication a new set of rules?

No. It is the Official Journal publication of guidance the Commission released on July 27, 2026. It interprets the CRA and is not legally binding.

Do we report a vulnerability in a library we use if it is being exploited elsewhere?

Only if it is actively exploited in your product. If the vulnerable code cannot be reached in your product, or has not been exploited there, the mandatory duty does not apply, though you still have to handle the vulnerability.

Does a breach of a smart device mean two separate notifications?

It can. A CRA report goes to the coordinating CSIRT and ENISA, while a personal data breach goes to the data protection authority under the GDPR. The guidance aligns the moment of awareness so both can be started from the same assessment.

Is our product’s companion app or cloud dashboard covered?

If the product cannot perform one of its functions without it and you designed it or had it built for you, it is likely an RDPS and part of the product for CRA purposes.

Guidance first, enforcement later

The CRA’s biggest deadline is still more than a year away, but its first obligation is already live and its interpretive rulebook is now formally on the record. Manufacturers that use the next twelve months to align product security, incident response and privacy work will find December 2027 a checkpoint rather than a scramble.

Put this into practice

Turn privacy guidance into working controls.

Captain Compliance helps teams discover tracking technologies, enforce consent, manage privacy requests and document the evidence behind every decision.

Book a demo Run a free scan