EU Cyber Resilience Act Guide for Railway Signalling & Train Control Vendors
Default class for most products, including ETCS, CBTC, interlocking, train protection and level crossing systems. Important Class I for a product whose core functionality is a router, switch or wireless access point (Annex III, point 12)
Railway signalling and train control systems represent some of the highest-consequence digital products in EU critical infrastructure, and their manufacturers face both CRA obligations and stringent rail-specific safety certification requirements under the ERA framework. Vendors of ETCS, CBTC, interlocking systems, and level crossing controllers must navigate the intersection of functional safety requirements and the CRA's cybersecurity mandate. Most signalling and train control products are default-class products, because Annex III lists no railway, signalling or safety category and classification follows core functionality (Article 7(1)). Safety integrity raises the risk that the Article 13(2) cybersecurity risk assessment has to address. It does not change the class.
Last updated 26 October 2026
CRA Scope and Classification for Railway Systems
Railway signalling and train control products placed on the EU market - including European Train Control System (ETCS) on-board units and wayside equipment, communications-based train control (CBTC) systems, electronic interlocking systems, automatic train protection (ATP) systems, and level crossing control equipment - are products with digital elements subject to the CRA. Classification follows core functionality (Article 7(1)). Annex III lists no railway, signalling, train protection or safety category. ETCS units, CBTC systems, interlocking systems, ATP systems and level crossing controllers are therefore default-class products. Passenger information displays and ticketing equipment are also default class. Direct control of train movements, enforcement of speed restrictions, SIL (Safety Integrity Level) designations under EN 50128 and the role of a product in the safety management system do not change the class. They raise the risk that the Article 13(2) cybersecurity risk assessment has to address. A product whose core functionality is a router, a switch or a wireless access point, such as a trackside network switch, is Important Class I (Annex III, point 12). Integrating such a component does not by itself change the class of the signalling product (Article 7(1)). Vendors must document the classification analysis for each product. CRA classification is independent of functional safety certification status.
Technical Security Obligations for Safety-Critical Rail Products
Annex I security requirements apply to railway signalling products with particular rigour. Core obligations include: segregating safety-critical processing from diagnostic and maintenance interfaces; ensuring all remote access for maintenance purposes uses authenticated, encrypted channels with multi-factor authentication; implementing firmware integrity verification on all field components; providing tamper-evident audit logs for safety-relevant operations; eliminating unauthenticated access to any interface that could influence train movement authority; and documenting the interaction between security controls and functional safety mechanisms. The SBOM must cover both the application software and any real-time operating system components. Vendors must also address supply chain security, given that rail signalling systems often incorporate components from multiple specialist suppliers. Security controls must be demonstrated not to introduce failure modes that could compromise the safety case.
CVD Policy Requirements Under Article 13
Article 13 requires rail signalling vendors to establish and publish a coordinated vulnerability disclosure policy. The rail sector has historically relied on a small community of specialist engineers with implicit security knowledge, but the increasing software complexity of modern ETCS and CBTC systems opens these products to a broader research community. The CVD policy must establish a dedicated reporting channel, define response timelines, and address the specific challenge of vulnerabilities in safety-critical systems: security patches for EN 50128-certified software may require re-certification before deployment, which can extend remediation timelines significantly. The CVD policy should explicitly acknowledge this constraint and commit to providing interim mitigations - configuration changes, network isolation measures - while re-certification is in progress. Coordination with the European Union Agency for Railways (ERA) and national safety authorities (NSAs) should be built into the CVD process.
Article 14 Incident Reporting for Rail Signalling Vendors
Active exploitation of a vulnerability in railway signalling equipment requires notification to the relevant national CSIRT within 24 hours under Article 14. For safety-critical signalling systems, vendors must also consider parallel reporting obligations to national rail safety authorities and, for cross-border rail corridors, ERA. A single compromised signalling component could affect multiple EU member states on pan-European corridors. Vendors must maintain 24/7 incident response capability with clear escalation paths to both cybersecurity and functional safety teams, as a security incident in signalling equipment may trigger both CRA notification requirements and safety management system incident procedures. Pre-established communication templates for regulatory notifications will reduce response time under pressure.
Conformity Assessment and Interaction with Rail Safety Certification
A default-class signalling product can use Module A internal control under the CRA (Article 32(1)). This CRA assessment is separate from and additional to the assessment by a notified body under Directive (EU) 2016/797 and the applicable TSIs. A Class I product, such as a trackside network switch, can use Module A only when it fully applies a harmonised standard, a common specification or a European cybersecurity certification scheme at assurance level substantial or higher (Article 32(2)). No CRA harmonised standard is cited in the Official Journal yet, so a Class I product needs a notified body for now (Module B plus Module C, or Module H). A CRA notified body and the rail interoperability notified body (NoBo) can be the same organisation, but their assessments operate under different regulatory frameworks and produce separate documentation. Manufacturers should seek to align assessment timelines where possible. The CRA technical file must include a cybersecurity case demonstrating that security controls are compatible with the functional safety case - this is a novel document type that bridges the safety and security disciplines and requires dedicated engineering resource to prepare. IEC 62443 and EN 50159 (safety-related communication in railway systems) provide the closest available standards basis. Neither is a cited CRA harmonised standard, so neither gives a presumption of conformity.
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
Security patches for our EN 50128-certified software require re-certification. How does this interact with the CRA's requirement to issue updates without undue delay?+
The CRA acknowledges that some industries have extended remediation timelines due to regulatory requirements. 'Without undue delay' is interpreted in context - re-certification requirements are a legitimate reason for extended patch timelines, provided vendors take all possible interim mitigation steps (network segmentation, configuration hardening, monitoring) and communicate these to operators. Document the re-certification timeline in your security advisory, provide interim mitigations, and notify the relevant CSIRT of the expected patch availability date. Proactive communication with national safety authorities and ERA is strongly advisable for vulnerabilities in safety-critical components.
Our ETCS equipment is type-approved across multiple EU member states. Does this simplify CRA conformity?+
No - ETCS type approval and CRA conformity assessment address different regulatory requirements and neither substitutes for the other. ETCS approval under the relevant TSI (Control-Command and Signalling) verifies interoperability and functional performance. CRA assessment addresses cybersecurity design and vulnerability management. Both are required for EU market access from 11 December 2027, when the CRA conformity obligations apply. However, the system architecture documentation and test evidence gathered for ETCS approval will be useful inputs to the CRA technical file, reducing the cost of preparing cybersecurity documentation.
Who is responsible for CRA compliance when our signalling system is integrated into a turnkey project by a systems integrator?+
The CRA places responsibility on the manufacturer who places the product with digital elements on the market. If your signalling components are sold to a systems integrator who incorporates them into a larger installation, you remain responsible for CRA compliance for your individual components. The systems integrator may assume additional obligations as a 'manufacturer' if they make substantial modifications to your product or if they are the entity placing the integrated system on the market. This distinction should be addressed explicitly in supply contracts, with clear allocation of CRA obligations between component vendors and integrators.
Key CRA articles for Railway Signalling & Train Control 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 Railway Signalling & Train Control Vendors?
Download a free CRA-compliant vulnerability disclosure policy and deploy it in minutes.