EU Cyber Resilience Act Guide for Oil & Gas Automation Vendors
Default class for most products, including SCADA, RTUs, PLCs and SIS. Important Class I for an industrial router, modem or switch (Annex III, point 12). Important Class II for an industrial firewall (Annex III, Class II, point 2)
Oil and gas automation vendors supplying SCADA systems, RTUs, and PLCs to EU operators fall within the CRA's scope as manufacturers of products with digital elements used in critical infrastructure. The regulation imposes mandatory vulnerability disclosure policies, secure-by-design requirements, and 24-hour incident reporting obligations that significantly expand existing IEC 62443 compliance programmes. Vendors must align security documentation, conformity assessment, and post-market monitoring with the CRA timetable, which applies Article 14 from 11 September 2026 and the remaining obligations from 11 December 2027.
Last updated 26 October 2026
CRA Scope and Classification for Oil & Gas Automation
Automation products supplied to EU oil and gas operators - including SCADA front-ends, remote terminal units (RTUs), programmable logic controllers (PLCs), historian servers, and safety instrumented system (SIS) components - qualify as products with digital elements under Article 3(1) of the CRA. Classification follows core functionality (Article 7(1)). Annex III lists no SCADA, RTU, PLC, historian or SIS category, so these products are default class. Safety and process-shutdown functions and physical actuation do not change the class. They raise the risk that the Article 13(2) cybersecurity risk assessment has to address. An industrial router, a modem for connection to the internet or a switch is Important Class I (Annex III, point 12). A secure remote access gateway whose core functionality is a VPN is Important Class I (Annex III, point 5), and privileged access management for OT systems is Important Class I (Annex III, point 1). An industrial firewall or an intrusion detection and prevention system is Important Class II (Annex III, Class II, point 2). Vendors should conduct a documented classification analysis before selecting their conformity pathway. Software-only products such as HMI applications also fall within scope if distributed commercially to EU operators, regardless of whether they are embedded in hardware.
Key Technical Security Obligations Under Annex I
Annex I Part I of the CRA requires oil and gas automation products to be designed with security as a fundamental property. For OT vendors this means: applying the principle of least privilege to all service accounts and remote access channels; enforcing authenticated and encrypted communications on all field protocols where the underlying standard permits (e.g. OPC-UA security profiles, DNP3 Secure Authentication v5); providing documented secure configuration baselines for each product; ensuring firmware and software update mechanisms are authenticated and integrity-verified; and supporting mechanisms to clear all sensitive operational data on decommissioning. Vendors must also maintain a software bill of materials (SBOM) in a machine-readable format covering all components including third-party libraries. Annex I Part II imposes ongoing obligations to actively monitor for vulnerabilities in distributed products and to issue updates without undue delay.
Coordinated Vulnerability Disclosure and Article 13 Requirements
Article 13 of the CRA mandates that manufacturers establish and publish a coordinated vulnerability disclosure (CVD) policy. For oil and gas automation vendors, this policy must specify a dedicated, publicly accessible reporting channel - typically a security contact email and a machine-readable security.txt file - and commit to acknowledging reports within defined timeframes. Because OT vulnerabilities in energy infrastructure are frequently reported by ICS security researchers and national CERT/CC teams, vendors should ensure their CVD policy explicitly accommodates coordinated multi-party disclosure, including interaction with ENISA and sector-specific CERTs. The policy must cover how discovered vulnerabilities are triaged, remediated, and communicated to affected operators. CVD Portal provides compliant hosted disclosure programmes that generate security.txt files and manage researcher communications, substantially reducing the administrative burden for vendors without dedicated product security teams.
Article 14 Incident and Vulnerability Reporting
Article 14 requires manufacturers to notify ENISA - via the relevant national CSIRT - within 24 hours of becoming aware of any actively exploited vulnerability in a product placed on the EU market, and within 24 hours of becoming aware of any severe incident having an impact on the security of the product. For oil and gas automation vendors, this obligation is operationally demanding: field-deployed products may be in service for 15–20 years, meaning vendors must maintain vulnerability tracking across legacy product lines long after active development has ceased. The 24-hour notification window requires vendors to have pre-established incident response procedures, a designated security officer authorised to make regulatory notifications, and direct contact details for relevant national CSIRTs in each EU member state where products are deployed. For an actively exploited vulnerability, the early warning must be followed by a vulnerability notification within 72 hours, and by a final report within 14 days after a corrective or mitigating measure is available, covering the vulnerability, its severity and impact, and the security update. For a severe incident, the early warning must be followed by an incident notification within 72 hours, and by a final report within one month after that incident notification, covering the incident, its severity and impact, the likely threat type or root cause, and the applied and ongoing mitigation measures.
Conformity Assessment Pathway
Default-class oil and gas automation products can use Module A internal control (Article 32(1)). An Important Class I product, such as an industrial router, can use Module A only when the manufacturer fully applies a harmonised standard, a common specification or a European cybersecurity certification scheme at assurance level at least substantial (Article 32(2)). No CRA harmonised standard is cited in the Official Journal yet, so today a Class I product needs a notified body under Module B plus Module C (EU-type examination plus conformity to type) or Module H (full quality assurance). An industrial firewall is Important Class II and always needs Module B plus Module C, Module H or a European cybersecurity certification scheme specified under Article 27(9) at assurance level at least substantial, for the requirements it covers (Article 32(3)). Vendors of Class I or Class II products should begin notified body engagement at least 12 months before their target market date, as assessment queues for OT products are expected to be lengthy. IEC 62443-4-1 (secure product development lifecycle) and IEC 62443-4-2 (component security requirements) are useful references for the Annex I requirements. They are not harmonised standards under the CRA and give no presumption of conformity. Regardless of pathway, vendors must compile a complete technical file including threat model, SBOM, vulnerability management procedures, security testing evidence, and the declaration of conformity. The CE marking and technical file must be maintained and updated for the entire product support period.
Transition Planning and Legacy Product Strategy
Oil and gas vendors face a distinctive challenge: large installed bases of legacy automation products that were never designed with CRA-compliant security features. The CRA requirements apply to products placed on the market from 11 December 2027. A product placed on the market before that date is subject to them only if it is substantially modified from that date (Article 69(2)). A new product variant placed on the market from that date must comply in full. Article 14 reporting applies from 11 September 2026 to all in-scope products, also to products placed on the market before 11 December 2027 (Article 69(3)). Vendors should conduct an inventory of all actively sold product lines, identify which will require CRA compliance work, and determine which legacy products will be end-of-life before 11 December 2027. For products that will remain in active sale, a structured security remediation roadmap - aligned with the IEC 62443-4-1 secure development lifecycle - should be established immediately. Customers should be proactively informed of the vendor's CRA readiness timeline.
Work through the CRA for each product in one workspace.
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 our products qualify as Critical Infrastructure under the CRA, and does that change our obligations?+
The CRA does not create a separate 'critical infrastructure' category. Classification follows core functionality (Article 7(1)), so components that perform safety or process-shutdown functions are default class unless their core functionality matches an Annex III category. A default-class product can use Module A internal control (Article 32(1)). Deployment in critical infrastructure raises the risk that the Article 13(2) cybersecurity risk assessment must address. Separately, the NIS2 Directive imposes cybersecurity obligations on energy sector operators - your customers - and their procurement requirements will increasingly demand CRA-compliant products as evidence of supplier due diligence.
Our PLCs use proprietary field protocols that predate modern cryptography. How does the CRA apply?+
Annex I requires security measures appropriate to the risks, which includes authenticated communications where technically feasible. Where legacy protocols cannot support encryption or authentication natively, vendors must implement compensating controls at the gateway or network layer and document these limitations in their technical file. The CRA does not prohibit legacy protocol support, but vendors must demonstrate that they have assessed the risk and implemented proportionate mitigations. Providing hardening guides and secure network architecture documentation to customers is also a Annex I Part II obligation.
How long must we support CRA-compliant products with security updates?+
The CRA requires manufacturers to support products with security updates for the length of time the product is expected to be in use, with five years as a floor rather than a target. Commission guidance C(2026) 5252 point 126 states that five years is not the default and that products expected to be in use for longer need correspondingly longer support periods. For industrial automation products in oil and gas, expected lifetimes routinely exceed 10–15 years. Vendors must declare the support period at point of sale and must not discontinue security updates before that period expires without providing a documented transition path for customers. Planning security update pipelines for long-lifecycle OT products is a significant engineering investment that must be budgeted into product roadmaps immediately.
Key CRA articles for Oil & Gas Automation Vendors
Guides for related sectors
Free CRA tools
This industry guide is part of the EU Cyber Resilience Act guide, which explains Regulation (EU) 2024/2847 article by article.
Need a CVD policy template for Oil & Gas Automation Vendors?
Download a free CRA-compliant vulnerability disclosure policy and deploy it in minutes.