← CRA Compliance Checklists
Industrial & ManufacturingDeadline: 11 December 2027

CRA Compliance Checklist: Industrial Controllers & PLCs

Default class for most PLCs, DCS, SCADA and other industrial controllers, because Annex III lists no industrial control category. Important Class I for an industrial router or switch (Annex III, point 12). Important Class II for an industrial firewall (Annex III, Class II, point 2)

Industrial controllers, PLCs, and SCADA components are default-class products under the CRA, because classification follows core functionality (Article 7(1)) and Annex III lists no industrial control category. They can use Module A internal control (Article 32(1)). These products have long operational lifetimes (10–20+ years), network connectivity, and significant safety implications. These facts raise the risk that the Article 13(2) risk assessment must address. Article 14 reporting applies from 11 September 2026, and the conformity obligations apply from 11 December 2027.

18
checklist items
17
high priority
11 December 2027
deadline
Industrial & Manufacturing
sector
CRA Classification:Default class for most PLCs, DCS, SCADA and other industrial controllers, because Annex III lists no industrial control category. Important Class I for an industrial router or switch (Annex III, point 12). Important Class II for an industrial firewall (Annex III, Class II, point 2)

Last updated 8 November 2026

1. Classification & Conformity Route

Confirm the class of each industrial automation and control product from its core functionality (Article 7(1))

highArticle 7(1), Annex III

Annex III lists no PLC, DCS or SCADA category, so these products are default class. An industrial router or switch is Important Class I (Annex III, point 12). An industrial firewall is Important Class II (Annex III, Class II, point 2). Safety effects and critical infrastructure use do not change the class.

Use Module A internal control for default-class controllers, and plan a notified body only for Class I or Class II products

highArticle 32

A default-class product needs no notified body (Article 32(1)). A Class I product can use Module A only when the manufacturer fully applies a harmonised standard, a common specification or a European cybersecurity certification scheme (Article 32(2)). No CRA harmonised standard is cited yet, so today a Class I product needs a notified body. A Class II product always needs a notified body or a certification scheme specified under Article 27(9) (Article 32(3)).

Prepare the technical documentation before the conformity assessment

highArticle 31, Annex VII

Include security architecture, SBOM, risk assessment, and CVD policy. Under Module A, you assess the documentation yourself. For a Class I or Class II product, the notified body reviews it.

2. Product Security (Annex I Part I)

Implement role-based access control for all HMI and engineering workstation interfaces

high

Industrial controllers must authenticate users at all access levels - operator, engineer, and administrator - with appropriate privilege separation.

Ensure secure firmware update process with signature verification and rollback protection

high

Industrial controller updates must preserve safety function integrity. Signed updates and rollback protection are strongly advised.

Disable all unused communication protocols and ports (Modbus, OPC-UA, EtherNet/IP)

high

Industrial protocols frequently lack authentication. Disable unused protocols to minimise attack surface.

Scan all firmware and software components against ICS-specific CVE databases (CISA ICS advisories, NIST)

high

SBOM must cover embedded RTOS, communication stack, protocol implementations, and any HMI software components.

Implement network segmentation support (industrial DMZ, OT/IT separation)

high

Controllers must support deployment in properly segmented OT networks.

Maintain tamper-evident security logs for audit and forensic investigation

high

Logs must capture all configuration changes, authentication events, and communication anomalies.

3. CVD Policy & Long-Lifecycle Management

Publish a CVD policy covering all active product lines and legacy products still in support

highArticle 13(1)

Industrial customers expect clear vulnerability reporting channels. Include product-specific scope in the CVD policy.

Define a support period that matches the expected use time. Article 13(8) sets at least 5 years, and industrial customers often expect 10 years or more

highArticle 13(8)

Industrial controllers often operate for 15–20+ years. Support periods must reflect this. Plan for long-term patch provision.

Establish a PSIRT (Product Security Incident Response Team) with defined escalation paths

highArticle 13, Annex I Part II

A dedicated PSIRT function helps meet the Annex I, Part II vulnerability handling requirements over long product lifetimes. Document roles, responsibilities, and escalation timelines.

Create a process for delivering security updates that works in air-gapped environments

high

Many industrial sites are air-gapped. Provide offline update packages (USB, DVD) alongside OTA updates.

4. Article 14 Incident Reporting

Monitor CISA ICS advisories and sector-specific threat intelligence for exploitation of your product lines

highArticle 14(1)

Industrial controller exploits are often state-sponsored and may target specific product models. Active monitoring is essential.

Establish and test the 24h early warning notification procedure with responsible personnel

highArticle 14(2)

Coordinate with ICS-CERT or sector CERT. Establish a communication protocol that can be executed within 24 hours even outside business hours.

Document supply chain notification procedures - notify downstream customers of critical vulnerabilities

highArticle 14(8)

Industrial customers may have critical infrastructure deployments. Notification procedures must reach them directly, not just via public advisories.

5. Legacy Product Management

Publish an end-of-life roadmap for all current product lines with security support end dates

high

Industrial customers need long advance notice of EOL to plan migration. Publish this proactively.

Develop a migration assistance programme for customers on end-of-life products

mediumArticle 13, Annex I Part II

CRA obligations extend to products throughout their supported life. Having a migration path available reduces liability.

Track your Industrial Controllers & PLCs compliance progress in CVD Portal.

Classify each product, build the Annex VII technical file and prepare Article 14 notifications. The disclosure portal that receives vulnerability reports stays free.

Frequently asked

Do all PLCs require third-party conformity assessment under the CRA?+

No. Annex III lists no PLC or industrial control category, and classification follows core functionality (Article 7(1)). Most PLCs and industrial automation controllers are default-class products and can use Module A internal control (Article 32(1)). An industrial router or switch is Important Class I (Annex III, point 12), and an industrial firewall is Important Class II (Annex III, Class II, point 2). Process control use, safety effects and critical infrastructure deployment do not change the class. They raise the risk that the Article 13(2) risk assessment must address.

How does the CRA interact with IEC 62443 for industrial cybersecurity?+

IEC 62443 is the primary industrial cybersecurity standard and aligns well with CRA Annex I requirements. Conformity with IEC 62443-4-2 (product security requirements) and IEC 62443-4-1 (secure development lifecycle) can serve as evidence of CRA compliance. IEC 62443 is not a CRA harmonised standard and gives no presumption of conformity.

My PLCs are deployed in air-gapped nuclear/defence sites - does the CRA apply?+

Products developed or modified exclusively for national security or defence purposes are outside the CRA (Article 2(7)). The same PLCs sold commercially for industrial use are in scope. Deployment at a nuclear or defence site does not change the class of a commercial PLC. Products placed on the EU commercial market must meet CRA requirements.

This checklist is part of the EU Cyber Resilience Act guide, which explains Regulation (EU) 2024/2847 article by article.

Need a CVD policy for Industrial Controllers & PLCs?

Download a free CRA-compliant disclosure policy template and deploy it in minutes.

Browse templates →