SEC-02 / Frameworks

Cyber Resilience Act for industrial manufacturers: what makers and plants need to do

The EU Cyber Resilience Act (Regulation (EU) 2024/2847) sets cybersecurity requirements for products with digital elements sold in the EU, from PLC-based machines to IIoT gateways. Reporting of actively exploited vulnerabilities and severe incidents has applied since September 11, 2026; the full requirements apply from December 11, 2027.

7 min read Updated Product managersOT engineersCISOsExecutives

Key takeaways

  • If you sell machines, controllers, drives, gateways or software with a data connection into the EU, you are probably a CRA manufacturer. If you only buy them, the CRA works in your favor.
  • Since September 11, 2026 manufacturers must report actively exploited vulnerabilities and severe incidents within 24 hours, including for products already on the market.
  • From December 11, 2027, products need secure-by-design properties, an SBOM, vulnerability handling for the support period, a conformity assessment and CE marking.
  • PLCs and industrial control systems are not a named category in the final Annex III, but industrial routers, switches, firewalls and operating systems can be important products by core function.
  • IEC 62443-4-1 and 4-2 are the closest existing match to CRA requirements. As of November 2026 no CRA harmonised standard had been cited in the Official Journal.

The Cyber Resilience Act (CRA) is the EU's product law for cybersecurity. It treats security the way CE marking already treats electrical and machine safety: if you place a product with digital elements on the EU market, it must meet essential requirements, you must document how, and you must keep it secure after it ships. For industrial manufacturers this matters twice. You may be a manufacturer under the CRA. You are almost certainly a buyer of products that will now have to meet it.

What the CRA is

The CRA is Regulation (EU) 2024/2847, dated October 23, 2024 and published in the Official Journal on November 20, 2024. As a regulation it applies directly in every member state, with no national transposition.

Key dates (checked November 17, 2026):

Date What applies
December 10, 2024 Entry into force
June 11, 2026 Rules on notification of conformity assessment bodies
September 11, 2026 Manufacturer reporting of actively exploited vulnerabilities and severe incidents
December 11, 2027 Full application: essential requirements, conformity assessment, CE marking

Does it apply to you?

The CRA covers products with digital elements: hardware and software products, including remote data processing solutions, whose intended use includes a direct or indirect logical or physical data connection to a device or network.

In an industrial context that includes, for example:

  • PLCs, safety controllers, drives and HMIs with Ethernet or fieldbus connectivity,
  • IIoT gateways, edge computers and industrial switches and routers,
  • engineering and SCADA software sold as a product,
  • machines and lines whose control system can connect to a network.

Some products are excluded because other EU law covers them, including medical devices and in vitro diagnostics, motor vehicles under the type-approval regime, marine equipment and certain aviation products.

Which role are you?

You are... Your CRA role What it means
A machine builder or OEM selling connected equipment in the EU Manufacturer Full obligations for the whole product, including due diligence on components you integrate
A maker of controllers, drives, gateways or industrial software Manufacturer Full obligations
An importer or distributor of these products Importer or distributor Check conformity, CE marking and documentation
A plant buying products for your own use Not a CRA economic operator You benefit: better security information, patches and SBOMs from suppliers
A plant that substantially modifies a product and makes it available on the market Can become a manufacturer Treat this carefully with counsel

Plant-floor reality: Many mid-market manufacturers are both. You run plants full of other people's controllers, and you also sell a machine or a connected product. Separate the two conversations: one is procurement, the other is product compliance.

Product classes: default, important, critical

Most products are in the default category. Manufacturers can use internal control (self-assessment) for those.

Important products (Annex III) need stricter conformity assessment.

  • Class I includes, among others: identity and access management products, VPN products, network management systems, SIEM, boot managers, PKI software, physical and virtual network interfaces, operating systems, routers, modems and switches, and microprocessors and microcontrollers with security-related functions. Self-assessment is possible only if you fully apply a harmonised standard, common specification or EU certification scheme. Otherwise a notified body is involved.
  • Class II includes hypervisors and container runtimes, firewalls and intrusion detection and prevention systems, and tamper-resistant microprocessors and microcontrollers. Third-party conformity assessment is required.

Critical products (Annex IV) are hardware devices with security boxes, smart meter gateways and other devices for advanced security purposes including secure cryptoprocessing, and smartcards and similar devices including secure elements.

What this means for industrial products. PLCs, DCS and industrial automation and control systems are not a named category in the final Annex III. A typical machine or controller will usually be a default product. But category is decided by the product's core functionality, so an industrial managed switch, an industrial router or a firewall built for OT networks can be an important product. Commission Implementing Regulation (EU) 2025/2392, adopted on November 28, 2025, gives technical descriptions of each important and critical category. Check your product against it before you decide your conformity route.

Watch out: Do not assume "industrial" means "out of scope" or "automatically important". Classify product by product, against the implementing regulation's descriptions, and record your reasoning.

What manufacturers must do

From September 11, 2026: reporting

Manufacturers must report through ENISA's Single Reporting Platform, which notifies the CSIRT of the member state where they have their main establishment.

What Early warning Notification Final report
Actively exploited vulnerability 24 hours 72 hours 14 days after a corrective measure is available
Severe incident affecting product security 24 hours 72 hours One month after the notification

This applies to products already on the market, not only those placed after 2027. You must also inform affected users.

From December 11, 2027: essential requirements

Annex I has two parts.

Part I, product properties. Products must be designed, developed and produced to an appropriate level of security based on risk. That includes no known exploitable vulnerabilities at release, a secure-by-default configuration, protection against unauthorized access, protection of data confidentiality and integrity, minimized attack surface, logging of relevant security events and the ability to receive security updates.

Part II, vulnerability handling. Manufacturers must:

  • identify and document components and vulnerabilities, including an SBOM in a commonly used, machine-readable format covering at least top-level dependencies,
  • address vulnerabilities without delay, including through security updates,
  • test and review security regularly,
  • publish information about fixed vulnerabilities,
  • have a coordinated vulnerability disclosure policy and a contact point,
  • distribute updates securely and, where possible, separately from functional updates.

Support period. You must handle vulnerabilities for a support period that reflects how long the product is expected to be used. The regulation sets at least five years unless the product's expected use is shorter. For industrial kit that runs 15 to 25 years, expect customers to push for longer.

Conformity and CE marking. Run the conformity assessment for your class, draw up technical documentation and an EU declaration of conformity, and apply the CE marking.

Fines

Breaches of the essential requirements and the manufacturer obligations can lead to fines of up to €15 million or 2.5% of worldwide annual turnover, whichever is higher. Lower ceilings apply to other breaches.

Relation to IEC 62443 and harmonised standards

Presumption of conformity comes from harmonised standards cited in the Official Journal. The Commission has asked the European standardisation organizations to develop CRA standards, both horizontal and product-specific. When we checked in November 2026, work was ongoing and no CRA harmonised standard had yet been cited.

Until then, IEC 62443 is the closest established match for industrial products:

CRA requirement area Closest IEC 62443 part
Secure development, testing, vulnerability handling, updates 62443-4-1 (secure product development lifecycle)
Product security capabilities (authentication, access control, logging, integrity) 62443-4-2 (component technical requirements)
System-level design for machines and lines 62443-3-3

A supplier with ISASecure SDLA and CSA certifications has done much of the underlying work. They still need CRA-specific items such as the SBOM, the reporting process, the support period and CE documentation.

If you build machinery, the CRA also sits next to the Machinery Regulation, which has its own cybersecurity-related safety requirements. See EU AI Act and Machinery Regulation.

For plants buying products

You have no CRA obligations as a user, but you can use it:

  • Ask suppliers now for their CRA plan: support period, SBOM availability, vulnerability disclosure contact, how they will notify you of exploited vulnerabilities.
  • Put support period and patch commitments into purchase contracts for equipment you will run for 15 years.
  • Ask for SBOMs for new controllers and gateways and feed them into your OT asset inventory so you can match future advisories.
  • Use the OT and AI vendor security questionnaire and the guidance on AI vendor due diligence for analytics and AI products, which are also products with digital elements.

If you are in NIS2 scope, CRA-compliant suppliers make your Article 21 supply chain duty easier to evidence.

Effort and cost (for a manufacturer)

  • Scoping and classification: 2 to 6 weeks for a mid-sized portfolio.
  • Reporting process (already due): a PSIRT-style intake, triage and 24-hour escalation. Many mid-market OEMs start with a small cross-functional team rather than a dedicated PSIRT.
  • SBOM tooling and process: weeks to set up, then part of each release.
  • Secure development lifecycle: 6 to 18 months to reach a 62443-4-1 level of practice if you are starting from scratch.
  • Notified body costs: only for important Class I products without full use of a harmonised standard, Class II and critical products.

Common mistakes

  • Thinking the CRA only starts in 2027. Reporting has applied since September 2026, for products already in the field.
  • Assuming machines are out of scope because they are "industrial".
  • Treating the SBOM as a one-off export instead of a maintained record per release.
  • Promising a support period engineering cannot deliver.
  • Waiting for harmonised standards before starting. 62443-4-1 and 4-2 are a sound base now.

Where to start: Monday-morning checklist

  1. List every product you place on the EU market that has software and a data connection.
  2. Classify each against Annex III, Annex IV and Implementing Regulation 2025/2392.
  3. Confirm your reporting process is live: who receives a vulnerability report, who decides, who files within 24 hours.
  4. Pick an SBOM format and generate one for your highest-volume product.
  5. Decide and document a support period per product line.
  6. Send your top ten suppliers a short CRA readiness questionnaire.

This page is not legal advice. Confirm product classification and conformity routes with counsel or a notified body.

Sources and further reading

  1. Regulation (EU) 2024/2847 (Cyber Resilience Act), summary and key dates (EUR-Lex)
  2. Cyber Resilience Act: reporting obligations (European Commission)
  3. CRA Single Reporting Platform (ENISA)
  4. Commission Implementing Regulation (EU) 2025/2392 on technical descriptions of important and critical products (EUR-Lex)

This guide is general information for manufacturers, not legal advice. Confirm regulatory obligations with qualified counsel.

FAQ

Frequently asked questions

Does the Cyber Resilience Act apply to machine builders?

Yes, if the machine is a product with digital elements, meaning it has software or firmware and a direct or indirect data connection to a device or network, and you place it on the EU market. A machine builder is the manufacturer of the whole machine and must exercise due diligence on integrated components, such as PLCs and HMIs bought from other suppliers. Some sectors, such as medical devices and type-approved motor vehicles, are excluded.

When do CRA reporting obligations start?

September 11, 2026. From that date, manufacturers must notify actively exploited vulnerabilities and severe incidents affecting the security of their products through ENISA's Single Reporting Platform. An early warning is due within 24 hours, a notification within 72 hours, and a final report later. This applies to products already on the market, not only to new ones.

Do I need an SBOM under the CRA?

Yes. Annex I requires manufacturers to identify and document components and vulnerabilities, including by drawing up a software bill of materials in a commonly used, machine-readable format covering at least the top-level dependencies. The SBOM is part of the technical documentation. You do not have to publish it, but market surveillance authorities can ask for it.

Does IEC 62443 certification mean CRA compliance?

Not automatically. IEC 62443-4-1 and 4-2 cover much of the same ground: secure development, vulnerability handling and technical security capabilities. They are a strong basis for CRA technical documentation. Presumption of conformity under the CRA comes only from harmonised standards cited in the Official Journal, and as of November 2026 none had been cited.

Related guides

Know where your plants stand

Score your AI governance, OT security and data readiness in about 10 minutes each. Results stay in your browser.