A metro train can move through a complex digital environment without the passenger ever seeing it.
Behind the train are onboard computers, wayside equipment, control centre systems, communication networks and operational software working together to support train supervision and control.
One of the most important technologies in this environment is Communications-Based Train Control, or CBTC.
CBTC can support functions such as Automatic Train Protection, Automatic Train Operation and Automatic Train Supervision through continuous communication between train and wayside systems. Europe’s Rail describes a typical CBTC environment as involving an onboard network, a train-to-trackside communication network and a trackside backbone network. [oai_citation:0‡Europe’s Rail](https://rail-research.europa.eu/wp-content/uploads/2025/02/FP1-MOTIONAL-D15.1-Requirements-for-the-deployment-of-TMS-linked-with-ATO-C-DAS.pdf?utm_source=chatgpt.com)
That connectivity creates operational advantages.
It also creates cybersecurity responsibilities.
CBTC cybersecurity is therefore not simply about protecting a computer. It is about protecting the communication and trust relationships that support a connected train control environment.
What Is CBTC?
Communications-Based Train Control is a railway control technology that uses continuous communication and train localisation information to support train supervision and control.
A CBTC deployment can include multiple components distributed between the train, trackside infrastructure and the operations control environment.
- Onboard train control equipment
- Wayside equipment
- Train-to-ground communication
- Trackside communication infrastructure
- Operations Control Centre systems
- Automatic Train Protection systems
- Automatic Train Operation systems
- Automatic Train Supervision systems
- Engineering workstations
- Maintenance systems
The exact architecture differs between suppliers and railway operators. A cybersecurity assessment should therefore work from the actual system architecture rather than assuming that every CBTC deployment is identical.
Why CBTC Cybersecurity Matters
CBTC depends on communication.
Communication creates connectivity.
Connectivity creates trust relationships.
Train
|
| Continuous Communication
v
Wayside
|
v
Trackside Network
|
v
Control Centre
Every connection creates questions about authentication, integrity, availability, access control, monitoring and resilience.
The security objective is not to remove necessary communication.
The objective is to make necessary communication appropriately controlled, monitored and resilient.
A Simplified CBTC Architecture
OPERATIONS CONTROL CENTRE
|
|
Control / Management
|
v
TRACKSIDE BACKBONE
|
+-------------+-------------+
| |
v v
Wayside Equipment Communication System
| |
+-------------+-------------+
|
v
TRAIN-TO-GROUND LINK
|
v
TRAIN
|
+---------+---------+
| |
v v
Onboard Control Train Network
|
v
Train Functions
This is a conceptual security model, not a supplier-specific CBTC architecture.
The purpose is to show where cybersecurity boundaries can exist.
The Three Important CBTC Communication Domains
A typical CBTC architecture can be understood through three major communication areas:
| Domain | Purpose | Security Consideration |
|---|---|---|
| Onboard network | Communication between train equipment | Segmentation, access control and integrity |
| Train-to-trackside | Communication between train and wayside infrastructure | Authentication, integrity, availability and resilience |
| Trackside backbone | Connects wayside and control infrastructure | Segmentation, monitoring and controlled access |
Europe’s Rail research identifies these three networks as a typical CBTC structure and notes that Ethernet is commonly used within the train and trackside backbone while wireless technologies can be used for train-to-trackside communication. [oai_citation:1‡Europe’s Rail](https://rail-research.europa.eu/wp-content/uploads/2025/02/FP1-MOTIONAL-D15.1-Requirements-for-the-deployment-of-TMS-linked-with-ATO-C-DAS.pdf?utm_source=chatgpt.com)
Onboard Network Security
The train itself can contain multiple connected systems.
TRAIN
|
+--------+--------+
| |
v v
Control System Train Network
| |
+-----+-----+ +----+----+
| | | |
v v v v
Controller HMI Gateway Other Systems
The onboard network should therefore be considered part of the railway’s security architecture.
- Which systems can communicate?
- Which systems require that communication?
- Which interfaces are exposed?
- Which systems can modify configuration?
- Are privileged interfaces protected?
- Can maintenance equipment connect to the network?
- Are wireless interfaces present?
- Are logs available?
Train-to-Trackside Communication
The train-to-trackside communication path is one of the most important parts of a CBTC security model.
TRAIN
|
|
| Wireless / Radio Communication
|
v
TRACKSIDE
|
v
Wayside Network
|
v
Control Systems
The communication technology can vary by deployment. Railway environments may use dedicated radio technologies or other wireless and wired communication technologies depending on the system design.
From a cybersecurity perspective, the important questions include:
- How are endpoints identified?
- How is communication authenticated?
- How is message integrity protected?
- How is unauthorized equipment prevented from joining?
- How is abnormal communication detected?
- How does the system behave when communication is interrupted?
- How is recovery handled?
Trackside Backbone Security
The trackside backbone can connect multiple railway components.
TRACKSIDE BACKBONE
|
+----------------+----------------+
| | |
v v v
Wayside Control Engineering
Equipment Systems Systems
| | |
+----------------+----------------+
|
v
Train Network
The more systems connected to a common backbone, the more important it becomes to understand communication requirements and trust boundaries.
CBTC and Automatic Train Protection
Automatic Train Protection, or ATP, is associated with functions that help enforce train movement constraints and protection logic.
Cybersecurity analysis should consider the integrity and availability of the systems supporting those functions.
The security question is not simply:
“Is the ATP computer vulnerable?”
The better question is:
“What systems can influence the information or communication on which the ATP function depends?”
CBTC and Automatic Train Operation
Automatic Train Operation, or ATO, supports automated train operation according to the architecture and automation level of the railway.
As automation increases, cybersecurity analysis needs to understand the digital dependencies behind that automation.
Digital Control
|
v
Train Information
|
v
Control Logic
|
v
Train Operation
|
v
Physical System
This does not mean that a cyber event automatically results in unsafe train operation. Railway systems are engineered with safety mechanisms and operational controls.
It does mean that cybersecurity assessment should understand where digital compromise could interact with operational functions.
CBTC and Automatic Train Supervision
Automatic Train Supervision, or ATS, supports higher-level supervision and management functions.
These systems may interact with operational information from trains and trackside infrastructure.
From a cybersecurity perspective, ATS environments should be assessed for:
- Unauthorized access
- Privilege management
- Network exposure
- Remote administration
- Configuration security
- Logging
- Network segmentation
- Availability
Why the Operations Control Centre Matters
The Operations Control Centre can become an important concentration point for railway information and control functions.
OCC
|
+---------+---------+
| | |
v v v
ATS Network Engineering
| | |
+---------+---------+
|
v
Trackside
|
v
CBTC
|
v
Train
Protecting the OCC therefore requires more than protecting its physical location.
- Account security
- Privileged access
- Network segmentation
- Remote access
- Endpoint security
- Application security
- Logging
- Backup and recovery
- Supplier access
Engineering Workstations: A High-Value Security Boundary
Engineering workstations can have legitimate access to systems that ordinary users cannot reach.
That makes them important from a cybersecurity perspective.
Engineering Workstation
|
v
Configuration Tools
|
v
Railway OT Network
|
v
CBTC / Wayside Systems
An assessment should determine whether the workstation has unnecessary network access, excessive privileges, insecure remote administration or uncontrolled removable-media pathways.
Vendor Remote Access
CBTC systems are commonly supported by specialist suppliers and maintenance organizations.
Remote support can be operationally valuable, but it creates an external trust relationship.
Vendor
|
v
Remote Access
|
v
Security Gateway
|
v
Maintenance Environment
|
v
CBTC Environment
The security assessment should establish exactly where this path terminates.
- Does the vendor reach the OT network directly?
- Is access enabled permanently?
- Is access restricted to maintenance windows?
- Are sessions authenticated?
- Are privileged actions logged?
- Can access be disabled quickly?
- Is the vendor connection isolated from unrelated systems?
Network Segmentation in CBTC
Segmentation is not simply a matter of creating VLANs.
The engineering question is whether the segmentation actually limits unnecessary communication.
Corporate IT
|
Firewall
|
DMZ
|
Firewall
|
Railway OT
|
+---------+---------+
| |
v v
Engineering CBTC
Zone Zone
|
+-----+-----+
| |
v v
Wayside Train
The exact zoning architecture should be based on system requirements and risk assessment.
What Should a CBTC Security Assessment Examine?
| Area | Assessment Focus |
|---|---|
| Architecture | System components and relationships |
| Onboard network | Internal train communication |
| Train-to-ground | Communication security |
| Wayside | Trackside components and interfaces |
| OCC | Supervision and management systems |
| Engineering | Privileged access and configuration |
| Remote access | Vendor and maintenance connectivity |
| Network | Segmentation and permitted communication |
| Vulnerabilities | Known weaknesses and exposure |
| Monitoring | Detection and logging |
| Recovery | Restoration and resilience |
CBTC Threat Modelling
A threat model helps transform a network diagram into an understanding of possible attack paths.
External Actor
|
v
Remote Access
|
v
Engineering Zone
|
v
CBTC Network
|
v
Wayside
|
v
Train Communication
|
v
Onboard System
This is not an assertion that every CBTC architecture contains this attack path.
It is an example of the type of relationship that should be examined during threat modelling.
Threat Modelling Questions
- What are the critical assets?
- Who can access them?
- Which systems trust each other?
- Which interfaces cross security boundaries?
- Where can an attacker potentially enter?
- Where could a compromised system communicate next?
- Which controls prevent lateral movement?
- How would abnormal activity be detected?
- How would the affected system be recovered?
CBTC Vulnerability Management
CBTC environments can contain operating systems, network devices, applications, embedded components and proprietary systems.
Some components may have long operational lifecycles, making conventional patching difficult.
Therefore, vulnerability management should consider:
- Vendor support status
- Software version
- Firmware version
- Known vulnerabilities
- Exploitability
- Network exposure
- Operational criticality
- Available compensating controls
- Maintenance windows
- Recovery options
Do Not Treat Every CVE as a CBTC Emergency
A vulnerability identifier tells you that a weakness exists under certain conditions.
It does not automatically tell you that a CBTC system is exploitable or operationally at risk.
CVE
|
v
Affected Product?
|
v
Correct Version?
|
v
Actual Deployment?
|
v
Network Exposure?
|
v
Attack Path?
|
v
Existing Controls?
|
v
Operational Impact?
|
v
Risk Decision
This is the difference between vulnerability enumeration and engineering risk assessment.
Where Nmap Fits Into a CBTC Assessment
Nmap can support authorized network discovery and service identification in suitable environments.
But a live CBTC environment should not be treated like an ordinary office network.
Before active scanning, the assessment team should understand:
- Device types
- Operational sensitivity
- Testing authorization
- Maintenance windows
- Available test environments
- Potential impact of active traffic
When uncertainty is high, passive discovery and documentation review can be the better starting point.
Where Wireshark Fits
Wireshark can be useful when authorized network captures are available.
- Identify communicating hosts
- Understand protocols
- Observe communication patterns
- Identify unexpected traffic
- Review network boundaries
- Support incident investigation
Passive network analysis can be particularly useful when direct interaction with live CBTC equipment is undesirable.
Where Shodan Fits
Shodan can support authorized external attack surface research.
For a railway operator, external intelligence may help identify publicly visible infrastructure that warrants further investigation.
However:
Public visibility is not the same as CBTC compromise.
Shodan Finding
|
v
Asset Attribution
|
v
Technical Validation
|
v
Architecture Review
|
v
Risk Assessment
IEC 62290 and CBTC Environments
IEC 62290:2025 is relevant to the wider urban guided transport command, control and management environment.
The series covers UGTMS and includes applications ranging from GOA1 non-automated operation through GOA4 unattended operation. IEC 62290-2:2025 defines functional requirements, while IEC 62290-3:2025 specifies system architecture and allocation of functions and requirements to UGTMS subsystems. [oai_citation:2‡IEC Webstore](https://webstore.iec.ch/en/publication/83773?utm_source=chatgpt.com)
There is an important qualification: IEC 62290 explicitly states that the series does not specifically address security issues.
Therefore, CBTC cybersecurity should not be presented as something automatically covered by IEC 62290.
The cybersecurity assessment needs to bring together the operational architecture and appropriate cybersecurity requirements.
CLC/TS 50701 and CBTC Security
CLC/TS 50701:2023 is specifically focused on railway cybersecurity and applies across Communications, Signalling and Processing, Rolling Stock and Fixed Installations domains. It provides guidance for managing cybersecurity within the railway RAMS lifecycle and uses concepts derived from the IEC 62443 series. [oai_citation:3‡Standards Store](https://shop.standards.ie/en-ie/standards/clc-ts-50701-2023-1265950_saig_cenelec_cenelec_3317488/?utm_source=chatgpt.com)
This is important because a CBTC security assessment should not be treated as a one-time penetration test.
Cybersecurity needs to be considered across the system lifecycle, from definition and risk assessment through requirements, assurance, operation, maintenance and eventual disposal.
IEC 61375 and Train Communication Networks
Train communication networks are another important part of the railway security picture.
IEC 61375-1:2026 covers communication architecture within vehicles, between vehicles and from train to ground. The fourth edition also introduces wireless train backbone and consist network options, virtual networks and a new clause addressing cybersecurity in train communication networks. [oai_citation:4‡IEC Webstore](https://webstore.iec.ch/en/publication/112567?utm_source=chatgpt.com)
This matters because a modern train is itself a connected computing environment.
CBTC Cybersecurity and Train Communication Networks
TRAIN
|
+-------+-------+
| |
v v
Train Backbone Consist Network
| |
+-------+-------+
|
v
Train Gateway
|
v
Ground Network
Security analysis should consider whether communication paths are appropriately separated and whether systems can reach functions they do not legitimately require.
Legacy CBTC and Long System Lifecycles
Railway infrastructure can remain operational for many years.
That creates a practical cybersecurity problem.
New Cyber Threats
+
Old Equipment
+
Long Lifecycle
+
Limited Patching
|
v
Compensating Controls
A system that cannot be immediately replaced should not simply be labelled “secure” or “insecure.”
The assessment should identify practical controls that reduce exposure.
- Network segmentation
- Restricted access
- Application control
- Monitoring
- Remote access restrictions
- Configuration hardening
- Physical security
- Backup and recovery
- Additional detection controls
CBTC Security and Availability
Security controls must be evaluated against operational requirements.
A control that introduces excessive latency, instability or operational complexity may require careful engineering evaluation before deployment.
Railway cybersecurity therefore needs to consider:
- Integrity
- Availability
- Confidentiality
- Operational continuity
- Maintainability
- Recoverability
For real-time railway control environments, security mechanisms should be evaluated for their effect on the system’s operational characteristics rather than added without consideration.
CBTC Incident Detection
A mature CBTC security architecture should consider how abnormal activity can be detected.
- Unexpected devices
- Unexpected communication paths
- Abnormal authentication activity
- Unexpected configuration changes
- Unusual remote sessions
- Unexpected network services
- Abnormal traffic patterns
Detection becomes particularly valuable when prevention cannot eliminate every possible attack path.
CBTC Recovery Planning
Cyber resilience also requires recovery.
- Configuration backups
- System images
- Known-good software versions
- Credential recovery
- Network configuration backups
- Replacement equipment
- Incident isolation procedures
- Tested restoration procedures
A vulnerability assessment should therefore ask not only how a system could be attacked, but also how the railway would recover if a critical component became unavailable or untrusted.
A Practical CBTC Security Assessment Model
DEFINE SCOPE
|
v
MAP CBTC ARCHITECTURE
|
v
IDENTIFY CRITICAL ASSETS
|
v
MAP TRUST BOUNDARIES
|
v
REVIEW COMMUNICATION PATHS
|
v
REVIEW REMOTE ACCESS
|
v
REVIEW CONFIGURATIONS
|
v
CORRELATE VULNERABILITIES
|
v
ANALYSE NETWORK EVIDENCE
|
v
CONTROLLED VALIDATION
|
v
ASSESS OPERATIONAL RISK
|
v
REMEDIATION ROADMAP
What Should a CBTC Security Report Contain?
| Section | Purpose |
|---|---|
| Executive summary | Explain the overall security posture |
| Scope | Define what was assessed |
| Architecture | Explain CBTC components and relationships |
| Asset inventory | Identify relevant systems |
| Trust boundaries | Identify important security boundaries |
| Attack surface | Identify potential entry points |
| Remote access | Assess maintenance and vendor connectivity |
| Vulnerabilities | Document relevant technical weaknesses |
| Evidence | Support technical findings |
| Operational impact | Explain why findings matter |
| Risk rating | Prioritize remediation |
| Recommendations | Provide practical controls |
| Limitations | Clearly state what was not tested |
Example CBTC Finding
Consider a hypothetical engineering workstation with access to a CBTC maintenance network.
A weak security configuration alone is not enough to determine the final risk.
Weak Configuration
|
v
Engineering Workstation
|
v
Network Reachability
|
v
CBTC Maintenance System
|
v
Access to Critical Environment?
|
v
Operational Impact
|
v
Risk Priority
The assessment should determine whether the communication path actually exists, whether access is authorized and what controls restrict the connection.
What a CBTC Assessment Should Not Do
- Run aggressive scans without authorization.
- Assume every CBTC architecture is identical.
- Treat public exposure as proof of compromise.
- Rank findings only by CVSS.
- Ignore vendor remote access.
- Ignore onboard networks.
- Ignore wayside systems.
- Ignore train communication networks.
- Assume safety certification equals cybersecurity.
- Recommend disruptive changes without understanding operational constraints.
The Difference Between a Tool Test and a CBTC Security Assessment
| Tool-Centred Approach | Engineering-Centred Approach |
|---|---|
| Scan the network | Understand the architecture first |
| List open ports | Understand why services exist |
| List CVEs | Correlate vulnerabilities with actual exposure |
| Report severity | Assess operational consequence |
| Recommend patches | Evaluate patching and compensating controls |
| Finish with a PDF | Finish with prioritized engineering decisions |
Tools collect evidence. Engineering judgment determines risk.
Remote CBTC Security Review
Not every CBTC assessment requires direct interaction with live train control equipment.
Depending on the project scope, a remote assessment can examine:
- CBTC architecture documentation
- Asset inventories
- Network diagrams
- Firewall configurations
- Remote access architecture
- Software and firmware information
- Vulnerability records
- Network captures
- Security logs
- Supplier documentation
- Existing risk assessments
This can provide meaningful independent analysis while reducing unnecessary interaction with production systems.
When Active CBTC Testing Is Appropriate
Active security testing can provide valuable evidence when performed in an appropriately controlled environment.
- Dedicated laboratory
- Development environment
- Test network
- Staging system
- Non-production equipment
- Approved maintenance window
For production CBTC systems, testing should be explicitly authorized and planned around operational risk.
The Cautivra Perspective
Cautivra approaches CBTC cybersecurity from an operational technology perspective.
UNDERSTAND
↓
MAP
↓
IDENTIFY
↓
ANALYSE
↓
VALIDATE
↓
PRIORITIZE
↓
REMEDIATE
The objective is not to generate the largest possible vulnerability list.
The objective is to identify meaningful weaknesses, explain the communication and trust relationships involved and provide practical actions that reduce risk without unnecessarily disrupting railway operations.
Final Perspective
CBTC is fundamentally a connected railway control environment.
The train communicates.
The wayside communicates.
The control centre communicates.
Engineering systems communicate.
Maintenance systems may communicate.
Every necessary connection must therefore have a security reason.
Know the assets.
Know the communication paths.
Know the trust boundaries.
Control remote access.
Understand vulnerabilities in context.
Monitor what matters.
Prepare for recovery.
A secure CBTC environment is not defined by how many security tools are deployed. It is defined by how well the railway understands and controls the digital relationships on which its operation depends.
Need a CBTC or Metro OT Security Review?
Cautivra provides remote, evidence-based security reviews for railway and metro operational technology environments.
Depending on scope, the review can examine CBTC architecture, onboard and wayside communication, network segmentation, remote access, engineering systems, external exposure, software and firmware information, vulnerability intelligence and available network evidence.
The objective is to identify meaningful security weaknesses, explain their operational relevance and produce a prioritized remediation roadmap.
Request a CBTC Security Review
Frequently Asked Questions
What is CBTC cybersecurity?
CBTC cybersecurity is the protection of the digital systems, communication paths and supporting infrastructure used by Communications-Based Train Control. It includes onboard systems, wayside equipment, train-to-ground communication, control centre infrastructure and relevant maintenance systems.
What systems are involved in CBTC?
A CBTC deployment can include onboard control equipment, wayside systems, train-to-ground communication, trackside networks, operations control systems, engineering workstations and maintenance infrastructure. The exact architecture depends on the supplier and railway.
Why is train-to-ground communication important for CBTC security?
CBTC depends on communication between onboard and trackside environments. That communication therefore becomes an important security boundary where authentication, integrity, availability, monitoring and resilience should be considered.
Can Nmap be used against CBTC systems?
Nmap can support authorized discovery and service identification, but live CBTC equipment should not be scanned as though it were an ordinary corporate network. Testing methodology should be selected according to device sensitivity, authorization and operational risk.
Can Wireshark help with CBTC security?
Yes. Authorized network captures can help security teams understand communicating hosts, protocols, traffic patterns and unexpected communication without necessarily interacting directly with operational equipment.
Can Shodan identify CBTC vulnerabilities?
Shodan can support authorized external attack surface research, but an internet-visible service does not establish that a CBTC system is vulnerable. External findings require attribution and technical validation.
Does IEC 62290 define CBTC cybersecurity requirements?
No. IEC 62290:2025 addresses urban guided transport management and command/control system requirements and includes applications from GOA1 through GOA4. The IEC states that the series does not specifically address security issues. Cybersecurity therefore requires additional appropriate security requirements and risk management.
What is CLC/TS 50701?
CLC/TS 50701 is a railway-specific cybersecurity technical specification. The current 2023 edition provides railway operators, system integrators and product suppliers with guidance and specifications for managing cybersecurity across railway lifecycle activities and applies to Communications, Signalling and Processing, Rolling Stock and Fixed Installations.
Does CBTC cybersecurity only concern the train?
No. A CBTC security assessment should consider the complete environment, including onboard systems, train-to-ground communication, wayside infrastructure, trackside networks, control centre systems and engineering or maintenance access.
Can a CBTC security assessment be performed remotely?
Yes. Architecture documentation, asset inventories, network diagrams, firewall configurations, remote access information, software and firmware records, vulnerability information and authorized network captures can support a remote assessment.
Sources and Further Reading
- IEC 62290-1:2025 — Urban guided transport management and command/control systems
- IEC 62290-2:2025 — Functional requirements
- IEC 62290-3:2025 — System requirements
- IEC 61375-1:2026 — Train communication network architecture
- CLC/TS 50701:2023 — Railway Applications: Cybersecurity
- Europe’s Rail — CBTC and train control communication research
