EU Cyber Resilience Act Guide for Pharmaceutical Manufacturing Automation Vendors
Default class for most products, including MES, batch, SCADA, PAT and LIMS. Important Class I for an industrial router, modem or switch (Annex III, point 12)
Pharmaceutical manufacturing automation vendors - supplying SCADA systems, batch management software, process analytical technology (PAT) platforms, and manufacturing execution systems (MES) to EU pharmaceutical manufacturers - must comply with the CRA for their products. The intersection of CRA cybersecurity requirements and EU GMP computerised systems validation (CSV) obligations creates a dual compliance framework that demands careful coordination between security and validation activities. CRA non-compliance by automation vendors directly threatens their customers' GMP compliance status and product supply security.
Last updated 26 October 2026
CRA Scope and Classification for Pharma Automation
Automation products sold to EU pharmaceutical manufacturers - including MES (manufacturing execution systems), batch record management software, SCADA systems for process control, process analytical technology (PAT) platforms, cleanroom environmental monitoring systems, and laboratory information management systems (LIMS) - are products with digital elements subject to the CRA. Classification follows core functionality (Article 7(1)). Annex III lists no MES, batch, SCADA, PAT or environmental monitoring category, so these products are default class. Direct control of critical process parameters, such as temperature, pressure and mixing ratios, does not change the class. The potential public health effect of a process control compromise raises the risk that the Article 13(2) cybersecurity risk assessment has to address. A router, a modem for connection to the internet or a switch is Important Class I (Annex III, point 12), and privileged access management for OT systems is Important Class I (Annex III, point 1). Vendors must document their classification analysis. The Article 13(2) risk assessment should be consistent with the EU GMP Annex 11 (computerised systems) risk assessment that customers will expect.
Technical Security and GMP CSV Intersection
Annex I security requirements must be implemented in a manner compatible with GMP computerised systems validation requirements under EU GMP Annex 11. Core security obligations include: implementing role-based access control with individual user accounts - shared accounts are incompatible with both Annex I and GMP audit trail requirements; ensuring all audit trails are tamper-evident and capture who did what and when for all operations affecting batch records or process parameters; encrypting data transmission between field devices, servers, and any cloud components; providing authenticated and logged remote access for vendor service purposes; and issuing security updates in a manner compatible with the customer's validated state - meaning that a security update must be accompanied by documentation supporting the customer's change control process. The SBOM must be maintained in machine-readable format and must cover all components including database engines, middleware, and any commercial off-the-shelf software components.
CVD Policy for Pharmaceutical Automation Vendors
Article 13 requires a published CVD policy. For pharmaceutical automation vendors, the CVD programme must be designed to accommodate: the extended patch deployment timelines inherent in GMP-validated environments, where security patches require change control, impact assessment, and re-qualification before installation; coordination with pharmaceutical customers' quality assurance teams who must approve changes to validated systems; and the potential public health implications of manufacturing system vulnerabilities, which may warrant notification of medicines regulatory authorities (EMA, national competent authorities) in serious cases. The CVD policy should commit to providing customers with: a detailed security advisory for each resolved vulnerability; a qualification impact assessment indicating whether the update affects validated functionality; and an interim mitigation package for customers who cannot immediately apply the patch due to validation cycle timelines.
Article 14 Incident Reporting in Regulated Manufacturing
Article 14 requires CSIRT notification within 24 hours of confirmed active exploitation. For pharmaceutical automation vendors, active exploitation of manufacturing systems - manipulation of batch parameters, falsification of batch records, disruption of cleanroom environmental controls - could constitute a serious public health risk requiring concurrent notification to medicines regulatory authorities. Vendors must establish incident response procedures that activate regulatory notification and pharmaceutical customer notification simultaneously. GMP customers experiencing a confirmed cyberattack affecting their manufacturing systems will themselves have incident reporting obligations to their medicines authority - vendor notifications must be rapid and comprehensive enough to support the customer's own regulatory response. Pre-incident table-top exercises with key pharmaceutical customers are strongly advisable.
Conformity Assessment and GMP Validation Coordination
Most pharmaceutical automation products are default class and can use Module A internal control (Article 32(1)). An Important 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 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 (Module B plus Module C, or Module H). The CRA technical file for a pharma automation system should be structured to complement the Design Qualification (DQ) and User Requirements Specification (URS) documentation that GMP customers require. Evidence of security testing - penetration tests, code review, vulnerability scanning - supports both the CRA technical file and the customer's Installation Qualification (IQ) assessment. Vendors who provide GMP qualification documentation packages as part of their product offering are well-positioned to extend this practice to CRA compliance documentation, providing customers with a security compliance pack alongside the standard IQ/OQ documentation. This approach differentiates CRA-compliant vendors in pharmaceutical procurement processes.
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
Our MES system is in GMP-validated state at customer sites. How do security patches work with the validated state?+
Security patches for GMP-validated systems require change control - the customer must assess the impact of the change, perform necessary testing, update validation documentation, and obtain quality assurance approval before installation. This process typically takes 4–12 weeks, which appears incompatible with the CRA's 'without undue delay' obligation. In practice, your obligation is to issue the patch promptly - the customer's obligation to install it within their validated change control process is a separate matter. You should provide customers with detailed patch documentation including: a summary of the security fix, an assessment of functional impact on validated workflows, and recommended test scripts for post-patch verification. This documentation enables customers to fast-track change control for critical security patches.
Our automation platform connects to the customer's enterprise network for reporting. Does this create CRA scope for the enterprise network components we don't manufacture?+
No. The CRA places obligations on the manufacturer of each product - you are responsible for your automation platform and any software you supply. The customer's enterprise network infrastructure is the responsibility of the entity who places that infrastructure on the market. However, the interfaces between your platform and the customer's enterprise network are within your scope for Annex I security purposes: you must ensure the connection interface is secured, documented in the technical file, and that your product does not introduce vulnerabilities into the enterprise network through the integration. Document all external interfaces in your threat model and specify security requirements for the connection point in customer deployment documentation.
How does the CRA affect our software subscription model for pharma MES customers on long-term contracts?+
Software supplied under subscription or long-term service contracts is in CRA scope when placed on the EU market. Each major software release placed on the market from 11 December 2027 must be CRA-compliant. Security update obligations apply for the declared support period - for MES products with long pharmaceutical customer contract cycles, this is typically 7–10 years. Subscription contracts should be reviewed to ensure security update delivery timelines, patch qualification documentation requirements, and incident notification obligations are clearly allocated between vendor and customer. Article 14 notification obligations remain with the vendor regardless of contractual arrangements.
Compliance checklists for your products
Key CRA articles for Pharmaceutical Manufacturing 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 Pharmaceutical Manufacturing Automation Vendors?
Download a free CRA-compliant vulnerability disclosure policy and deploy it in minutes.