EU Cyber Resilience Act Guide for Chemical & Process Plant Automation Vendors
Important — Class II (DCS and SIS for major hazard sites); Class I (process monitoring)
Chemical and process plant automation vendors supplying distributed control systems (DCS), safety instrumented systems (SIS), and process SCADA platforms to EU chemical manufacturers face the highest tier of CRA obligations, given the catastrophic potential consequences of automation system failure in chemical production environments. The intersection of CRA cybersecurity requirements with Seveso III Directive major accident prevention obligations creates a complex dual regulatory framework. CRA compliance for chemical automation vendors is not only a market access requirement but a fundamental component of major hazard risk management.
CRA Scope and Seveso III Interaction
Automation products supplied to EU chemical manufacturers — including distributed control systems (DCS), safety instrumented systems (SIS), emergency shutdown systems (ESD), process SCADA platforms, and process historian systems — are products with digital elements under Article 3(1). For products deployed at Seveso III upper-tier sites, the risk profile is exceptional: a cyberattack causing loss of process control could trigger chemical releases with major accident consequences. DCS and SIS products are strong candidates for Class II Important Products given their role in both process control and safety function implementation. The Seveso III Directive requires major hazard operators to include malicious acts in their major hazard analysis — CRA-compliant automation equipment provides a documented security baseline that supports this requirement. Vendors must assess classification for each product, noting that the same hardware may function as either a DCS component or a SIS component depending on deployment configuration.
Technical Security for Chemical Process Control Systems
Chemical process automation systems present the most demanding security engineering challenge in the OT sector: security failures can have immediate life safety and environmental consequences. Annex I requirements include: segregating SIS (safety) networks from DCS (process control) networks with no direct IP connectivity between them; implementing authenticated access for all engineering workstation connections to DCS controllers; ensuring firmware updates to field controllers are authenticated and integrity-verified, and can be applied without bypassing safety shutdowns; providing tamper-evident audit logs for all setpoint changes, configuration modifications, and alarm acknowledgments; eliminating shared engineering workstation credentials; and implementing remote access security for vendor support connections equivalent to on-site access. The SBOM must cover DCS controller firmware, engineering workstation software, historian server components, and any third-party process optimisation or simulation modules integrated with the control system.
CVD Policy for Chemical Automation Vendors
Article 13 requires a published CVD policy. Chemical automation vendors operate in a sector where security vulnerabilities can have catastrophic consequences, and the CVD programme must reflect this risk. The policy must: establish accelerated response timelines for vulnerabilities affecting SIS or ESD systems; specify coordination procedures with the European Chemicals Agency (ECHA), national major hazard competent authorities (e.g. HSE in the UK context, national Seveso authorities in EU member states), and relevant ICS security organisations including ICS-CERT national equivalents; and define how security advisories are communicated to major hazard site operators with appropriate urgency. For vulnerabilities affecting safety-critical functions, interim mitigations — isolation of affected components, implementation of manual backup procedures, enhanced safety monitoring — must be specified in security advisories alongside the patch. Chemical sector customers require highly detailed security advisories to support their own major hazard risk assessments.
Article 14 Reporting: Major Hazard Implications
Article 14 requires CSIRT notification within 24 hours of confirmed active exploitation. For chemical automation vendors, exploitation of a DCS or SIS system is a major hazard event that triggers simultaneous notifications to: the relevant national CSIRT (Article 14); the relevant major hazard national competent authority (Seveso III); and potentially ECHA and cross-border affected authorities for Seveso upper-tier sites near national borders. A confirmed cyberattack on a major chemical site's control systems may trigger activation of national emergency response plans. Vendors must have pre-established communication protocols for this scenario, with authorised personnel identified and contact lists maintained for relevant national authorities across EU member states where products are deployed. The 24-hour CSIRT notification must communicate the potential for major hazard consequences to enable appropriate response coordination.
Conformity Assessment for Safety-Critical Process Control
Class II chemical process automation products require notified body assessment. Given the major hazard context, notified bodies with IEC 62443 and IEC 61511 (functional safety for process industry) expertise are preferred. The CRA technical file for chemical automation must include a security case that explicitly addresses the interaction between security controls and the functional safety case — demonstrating that security measures do not introduce common cause failures into the SIS, and that the SIS retains its protective function under cyberattack scenarios. This is the most technically demanding aspect of CRA conformity for this sector. IEC 62443-3-3 (system security requirements) and IEC 62443-4-2 (component security requirements) provide the most directly applicable security standards framework. Vendors with existing IEC 61511 certification will find the safety case methodology familiar but must extend it explicitly to address cybersecurity threats.
CVD Portal handles your CRA Article 13 obligations automatically.
Public CVD submission portal, 48-hour acknowledgment tracking, Article 14 deadline alerts, and CSAF advisory generation. Free forever for Chemical & Process Plant Automation Vendors.
Start your free portalFrequently asked
Our SIS is certified to IEC 61511 SIL 3. Does this functional safety certification address CRA requirements?+
IEC 61511 SIL 3 certification addresses functional safety — the ability of the SIS to perform its protective function on demand. It does not address cybersecurity requirements such as authentication, encryption, vulnerability management, or CVD policy. These are distinct and additive requirements under the CRA. However, the systematic development and documentation approach required for SIL 3 certification — hazard analysis, architecture documentation, design reviews, testing — provides an excellent foundation for the CRA technical file. A gap analysis comparing your existing SIL 3 documentation against Annex I requirements will identify the specific cybersecurity additions needed. IEC 62443-3-3 Security Level requirements should be aligned with your SIL classification in the cybersecurity-safety integration analysis.
We manufacture both the DCS and the SIS for the same process line. How do we address the security segregation requirement when both systems are ours?+
Annex I requires segregation of safety functions from process control functions as a fundamental security principle — this applies even when both systems are supplied by the same vendor. Your DCS and SIS must be architected with a security boundary that prevents an attacker who compromises the DCS from accessing or manipulating the SIS. This means: separate engineering workstation access for DCS and SIS configuration; no direct IP connectivity between DCS and SIS networks; unidirectional data diodes or read-only interfaces where status data from the SIS must be visible in the DCS; and separate authentication systems. The technical file must demonstrate this segregation and include a security architecture review confirming that DCS compromise cannot propagate to SIS function.
How does the CRA affect our legacy DCS products still running at Seveso sites where replacement is not feasible?+
The CRA applies to products placed on the market after September 2026 — legacy products already installed before that date are not directly subject to CRA requirements. However, any firmware update, significant software release, or materially updated product variant placed on the market after September 2026 triggers compliance obligations. For legacy products that will remain in service with no new market placements, your obligation is limited to what is contractually agreed with the site operator. That said, Seveso site operators' major hazard analysis obligations require them to manage cybersecurity risks in legacy control systems — you should provide customers with security hardening guidance and technical support even for out-of-scope legacy products, both as a safety obligation and as a customer retention matter.
Key CRA articles for Chemical & Process Plant Automation Vendors
Need a CVD policy template for Chemical & Process Plant Automation Vendors?
Download a free CRA-compliant vulnerability disclosure policy and deploy it in minutes.