A modern railway is no longer only a mechanical and electrical system.
Train movement, signalling, supervision, communications, passenger information, maintenance and operational control increasingly depend on interconnected digital systems.
That connectivity creates a difficult engineering question:
How do you protect railway operational technology without compromising the availability, safety and reliability of the railway itself?
This is the central problem behind railway OT cybersecurity.
It is not simply about installing firewalls, scanning IP addresses or protecting office computers. Railway cybersecurity requires an understanding of the operational systems that support signalling, train control, communications, supervision, wayside equipment, onboard systems and maintenance activities.
For metro and urban rail systems, this becomes even more important as digital command and control systems support increasingly automated operations. IEC 62290:2025 covers urban guided transport management and command/control systems, including applications ranging from GOA1 through GOA4. The standard defines system, functional and interface requirements, while explicitly noting that the IEC 62290 series does not specifically address security issues.
Cybersecurity therefore has to be considered alongside the operational architecture rather than assumed to be provided by the signalling standard itself.
What Is Railway OT Cybersecurity?
Railway OT cybersecurity is the protection of operational technology and connected digital infrastructure that supports railway operations.
Depending on the railway, this may include:
- Signalling systems
- Train control systems
- CBTC systems
- Automatic Train Protection
- Automatic Train Operation
- Automatic Train Supervision
- Interlocking systems
- Wayside equipment
- Onboard train systems
- Train communication networks
- Operations Control Centre systems
- Station systems
- Maintenance systems
- Remote access infrastructure
- Engineering workstations
- Industrial network infrastructure
The exact architecture differs between mainline railways, metros, automated people movers, light rail and other guided transport systems.
Railway Cybersecurity Is Different From Ordinary IT Security
In a conventional IT environment, a compromised workstation may result in data loss, credential theft or business interruption.
In a railway OT environment, the consequences can extend into operational functions.
Corporate IT
|
v
Applications
|
v
Business Operations
Railway OT
|
v
Control / Monitoring
|
v
Railway Operations
|
v
Physical Movement
|
v
Operational Consequence
This does not mean that every railway cyber incident will affect train movement.
It means that cybersecurity analysis must understand where a digital system sits within the operational chain.
The Railway OT Environment
A useful way to understand railway OT is to separate the environment into functional layers.
RAILWAY SYSTEM
|
+------------------+------------------+
| | |
v v v
OPERATIONS SIGNALLING MAINTENANCE
| | |
v v v
OCC CONTROL ENGINEERING
| | |
+------------------+------------------+
|
v
COMMUNICATION
NETWORKS
|
+-------------+-------------+
| |
v v
WAYSIDE ONBOARD
SYSTEMS SYSTEMS
| |
+-------------+-------------+
|
v
TRAIN MOVEMENT
This is a conceptual model rather than a universal railway architecture. Actual systems depend on the operator, signalling technology, supplier architecture, automation level and operational requirements.
Why Signalling Security Matters
Signalling systems exist to support the safe and controlled movement of trains.
They may incorporate equipment and software distributed between control centres, stations, wayside locations and trains.
Cybersecurity therefore has to consider more than individual computers.
The important question is:
What happens when trust between railway components is compromised?
A security assessment should examine authentication, authorization, communications, system boundaries, configuration management, monitoring, recovery and the potential operational consequences of compromise.
Where CBTC Fits Into Railway OT
Communications-Based Train Control, commonly known as CBTC, is used in many modern metro and urban rail environments.
CBTC relies heavily on communication between onboard and wayside components to support train supervision and control.
OPERATIONS CONTROL
CENTRE
|
|
Control Network
|
v
Wayside Systems
|
+----------+----------+
| |
v v
Trackside Equipment Communication
|
v
TRAIN
|
+--------+--------+
| |
v v
Onboard Train Systems
Control
The exact CBTC architecture varies by supplier and deployment.
From a cybersecurity perspective, the important issue is the collection of communication paths and trust relationships connecting these components.
Why CBTC Creates a Cybersecurity Challenge
Greater connectivity can provide operational advantages.
- Continuous data exchange
- Centralized supervision
- Operational automation
- Real-time monitoring
- Remote diagnostics
- Maintenance visibility
But connectivity also creates additional relationships that need protection.
More Connectivity
|
v
More Communication Paths
|
v
More Trust Relationships
|
v
More Security Boundaries
|
v
More Cybersecurity Requirements
The objective is therefore not to eliminate connectivity.
The objective is to make necessary connectivity controlled, understood and defensible.
Train Control Is a Cybersecurity Concern
Train control environments can contain several functions with different operational responsibilities.
| Function | General Purpose | Cybersecurity Concern |
|---|---|---|
| ATP | Supports train protection | Integrity and availability |
| ATO | Supports automated train operation | Integrity and availability |
| ATS | Supports supervision and management | Availability and access control |
| Interlocking | Controls signalling routes | Integrity and unauthorized control |
| Wayside systems | Interfaces with trackside infrastructure | Communication and physical process integrity |
| Onboard systems | Supports train-side functions | Integrity, availability and communication security |
The exact implementation depends on the railway technology and supplier architecture.
Onboard and Wayside Security
A railway should not be viewed as a collection of isolated onboard and trackside devices.
The communication between them is part of the security boundary.
WAYSIDE
|
|
Communication Link
|
|
TRAIN
|
Onboard Network
|
+------+------+
| |
v v
Control Other Systems
Equipment
A security assessment should therefore examine both endpoints and the communication path between them.
Train Communication Networks Are Becoming More Important
Train communication networks provide the infrastructure for data exchange within vehicles, between vehicles and, depending on the architecture, between trains and ground systems.
IEC 61375-1:2026 addresses the general architecture of train communication networks and covers communication within vehicles, between vehicles and train-to-ground communication. The 2026 edition also introduces a dedicated cybersecurity clause for train communication networks.
This is important for cybersecurity professionals because the train communication layer is not simply a transport mechanism. It can become an important trust boundary between onboard functions and external communication environments.
The Railway Attack Surface
A railway attack surface can extend far beyond the public internet.
RAILWAY
|
+------------------+------------------+
| | |
v v v
Internet Remote Access Physical
| | Access
v v |
Corporate IT Maintenance |
| | |
+---------+--------+------------------+
|
v
Railway Network
|
+---------+---------+
| | |
v v v
OCC Wayside Onboard
| | |
+---------+---------+
|
v
Train Systems
Potential entry points can include:
- Remote maintenance
- Vendor access
- Engineering workstations
- Corporate IT systems
- Network gateways
- Wireless infrastructure
- Maintenance laptops
- Removable media
- Internet-facing services
- Train-to-ground communications
- Third-party connections
Remote Maintenance Is a Major Security Boundary
Railway operators depend on suppliers and maintenance organizations to support complex equipment.
Remote access can reduce maintenance time and provide faster technical support.
It can also create a path from an external environment toward railway OT.
Vendor
|
v
External Network
|
v
Remote Access Gateway
|
v
Security Boundary
|
v
Railway Network
|
v
Engineering System
|
v
OT System
Every step in this path should have an explicit security purpose.
Questions to Ask About Remote Railway Access
- Who can connect?
- Why is access required?
- Which systems can the user reach?
- Is access enabled continuously?
- Can access be restricted to maintenance windows?
- Are individual accounts used?
- Is strong authentication implemented?
- Are sessions logged?
- Can vendor access be disabled?
- Can remote users reach critical OT directly?
- Is a controlled gateway or jump host used?
- Are remote activities reviewed?
Railway Network Segmentation
Segmentation is one of the most important concepts in railway OT security.
The objective is not to isolate every system from every other system.
The objective is to control communication according to operational requirements.
RAILWAY NETWORK
|
+---------------+---------------+
| | |
v v v
IT OT Public
| |
| +------+------+
| | |
| v v
| Signalling Engineering
| |
| v
| CBTC
|
v
Business
Systems
The exact segmentation model depends on the railway architecture, operational requirements and risk assessment.
Why Flat Railway Networks Are Dangerous
A flat network can create unnecessary trust relationships between systems.
Imagine an engineering workstation becoming compromised.
Compromised
Engineering Workstation
|
v
Broad Network
|
+----+----+----+
| | |
v v v
HMI Server OT
|
v
Signalling
If the workstation can communicate with systems that it does not legitimately need to access, the potential attack surface becomes larger.
Segmentation can reduce unnecessary paths and limit the potential spread of a compromise.
Railway OT Security Should Follow the Architecture
There is no single network diagram that represents every railway.
A metro using CBTC may have a different architecture from a conventional railway using interlocking, track circuits and conventional signalling.
An automated metro may have different security requirements from a manually operated regional railway.
Therefore:
Security controls should follow the operational architecture rather than forcing every railway into the same template.
IEC 62290 and Metro Cybersecurity
IEC 62290:2025 is particularly relevant when discussing urban guided transport management and command/control systems.
The series covers UGTMS system principles, functional requirements and system requirements for urban guided passenger transport lines and networks. It supports new lines as well as upgrades to existing signalling and command/control systems and covers operational grades from GOA1 through GOA4.
However, IEC 62290 explicitly does not specifically address security issues.
That distinction matters.
A railway cybersecurity assessment should understand the UGTMS architecture while using appropriate cybersecurity requirements and risk-management methods alongside the functional and safety requirements.
CENELEC TS 50701 and Railway Cybersecurity
CENELEC TS 50701 is specifically concerned with cybersecurity for railway applications.
It provides a railway-specific cybersecurity framework and connects cybersecurity activities with the railway lifecycle and security management process.
This makes it fundamentally different from simply applying a generic vulnerability scanner to a railway IP range.
A serious assessment needs to consider lifecycle, architecture, threats, assets, security controls and evidence.
IEC 62443 and Railway OT
IEC 62443 provides a widely used industrial automation and control systems cybersecurity framework.
Railway cybersecurity work increasingly references IEC 62443 alongside railway-specific requirements.
Europe’s Rail cybersecurity specification, for example, references IEC 62443, CENELEC TS 50701 and emerging railway cybersecurity work as part of its approach to secure railway components and communications.
The important point is not to treat one standard as a universal replacement for the others.
Railway cybersecurity requires the correct relationship between railway requirements, OT security engineering and applicable regulatory obligations.
Railway Cybersecurity Assessment Methodology
A practical railway OT assessment should begin with understanding rather than scanning.
1. Define Scope
↓
2. Understand Railway Operations
↓
3. Identify Critical Functions
↓
4. Build Asset Inventory
↓
5. Map Architecture
↓
6. Identify Trust Boundaries
↓
7. Review Remote Access
↓
8. Review Configurations
↓
9. Analyse Network Evidence
↓
10. Correlate Vulnerabilities
↓
11. Controlled Validation
↓
12. Assess Operational Impact
↓
13. Prioritize Risk
↓
14. Remediation Roadmap
Step 1: Define the Scope
Before touching a technical system, define what is actually being assessed.
- Railway line
- Metro line
- Train fleet
- OCC
- Wayside systems
- Onboard systems
- CBTC environment
- Signalling network
- Maintenance network
- Remote access infrastructure
Testing authorization, operational restrictions and assessment windows should also be established before active testing is considered.
Step 2: Understand the Operational Function
An asset should never be assessed only by its hostname or IP address.
Ask what it actually does.
- Does it monitor trains?
- Does it control a process?
- Does it support signalling?
- Does it communicate with onboard systems?
- Does it support maintenance?
- Does it provide operational information?
- What depends on it?
- What happens if it becomes unavailable?
Step 3: Build the Asset Inventory
| Asset | Function | Location | Network | Criticality |
|---|---|---|---|---|
| OCC server | Operational management | Control centre | OT | High |
| Engineering workstation | Configuration and maintenance | Control centre | OT | High |
| Wayside controller | Trackside function | Wayside | Signalling | High |
| Onboard controller | Train control function | Train | TCN/OT | High |
| Network switch | Connectivity | Equipment room | OT | High |
This table is illustrative. Actual criticality should be determined from the railway’s operational and safety architecture.
Step 4: Map Trust Boundaries
One of the most valuable activities in railway OT security is identifying where trust changes.
Corporate IT
|
| Trust Boundary
v
Railway IT
|
| Trust Boundary
v
Railway OT
|
| Trust Boundary
v
Signalling
|
| Trust Boundary
v
Train Control
|
v
Physical Operation
Each boundary should have a security purpose.
Step 5: Review Remote Access
Determine who can access railway OT remotely and what they can reach.
- Authentication
- Authorization
- Access duration
- Maintenance windows
- Vendor access
- Session logging
- Privileged access
- Remote administration
- Emergency access
Step 6: Review Network Architecture
Network architecture should be compared with the documented operational requirements.
- Segmentation
- Firewalls
- VLANs
- Routing
- Gateways
- DMZs
- Remote access gateways
- Wireless networks
- Train-to-ground links
- Wayside communication
Step 7: Review Vulnerabilities
Vulnerability assessment should correlate actual assets with authoritative vulnerability information.
- Vendor
- Product
- Version
- Firmware
- Operating system
- Exposed services
- Network location
- Known vulnerabilities
- Known exploitation activity
- Available mitigations
A CVE number alone does not establish railway risk.
The assessment must determine whether the affected component is actually exposed, reachable and operationally significant.
Step 8: Analyse Network Traffic
Where authorized network captures are available, passive traffic analysis can provide valuable evidence.
- Communicating hosts
- Protocols
- Unexpected connections
- Communication frequency
- Network boundaries
- Unexpected services
- Potentially abnormal traffic
Wireshark and other network analysis tools can support this process.
Passive analysis can be particularly useful before active testing because it can reveal how the railway actually communicates without necessarily interacting with operational equipment.
Where Nmap Fits
Nmap can be useful for authorized discovery and service identification.
But the tool should be selected after the environment has been understood.
| Environment | Assessment Approach |
|---|---|
| External infrastructure | Authorized exposure assessment |
| Corporate IT | Controlled active scanning |
| Railway laboratory | Controlled technical testing |
| Production OT | Passive or specifically authorized testing |
| Safety-related systems | Strictly controlled validation |
Running a generic scan across a live signalling network without understanding device sensitivity is not a professional railway security methodology.
Where Shodan Fits
Shodan can support authorized external attack surface intelligence.
- Internet-visible services
- Open ports
- Service banners
- Certificates
- Publicly visible infrastructure
- Potentially exposed technologies
But Shodan should never be treated as proof that an internal railway OT system is vulnerable.
The correct sequence is:
External Intelligence
↓
Potential Exposure
↓
Asset Attribution
↓
Technical Validation
↓
Architecture Context
↓
Risk Assessment
Tools Collect Evidence. Engineering Judgment Determines Risk.
This distinction should remain at the centre of a professional railway OT assessment.
| Tool / Method | What It Can Provide | What It Cannot Prove Alone |
|---|---|---|
| Shodan | External exposure intelligence | Internal exploitability |
| Nmap | Network and service discovery | Operational impact |
| Wireshark | Traffic analysis | Complete system risk |
| Vulnerability database | Known vulnerability information | Actual railway exposure |
| Configuration review | Security control information | Future attack behaviour |
| Threat modelling | Potential attack paths | Guaranteed exploitation |
The professional value comes from connecting these evidence sources into an engineering assessment.
Railway OT Vulnerability Prioritization
Not every vulnerability deserves the same remediation priority.
Technical Severity
+
Network Exposure
+
Asset Criticality
+
Attack Path
+
Operational Impact
+
Existing Controls
+
Recovery Capability
|
v
Risk Priority
This is more useful than simply sorting a report by CVSS score.
Example: Same Vulnerability, Different Railway Risk
| Asset | Network Position | Potential Risk |
|---|---|---|
| Office workstation | Isolated business network | Limited operational relevance |
| Engineering workstation | Connected to OT | Higher potential impact |
| Signalling component | Connected to critical control environment | Potentially significant operational concern |
The vulnerability itself has not changed.
The context has.
Railway Cybersecurity and Safety
Cybersecurity and functional safety are related but distinct disciplines.
A cybersecurity assessment should not claim that a system is “safe” simply because no cybersecurity vulnerabilities were found.
Likewise, a safety-certified system should not automatically be assumed to be secure against cyber threats.
The stronger engineering approach is to understand how security events could interact with operational and safety functions and then coordinate the appropriate disciplines.
Railway Cybersecurity and Availability
Availability can be particularly important in railway OT.
A security control that prevents an unauthorized action but introduces unacceptable operational instability is not necessarily an appropriate solution.
Security architecture therefore has to balance:
- Confidentiality
- Integrity
- Availability
- Operational continuity
- Safety requirements
- Maintainability
- Recoverability
Railway OT Incident Detection
Prevention is only one layer of railway cybersecurity.
The operator should also consider how abnormal activity would be detected.
- Unexpected remote sessions
- New network devices
- Unexpected communication paths
- Abnormal traffic patterns
- Repeated authentication failures
- Unauthorized configuration changes
- Unexpected services
- Communication across restricted boundaries
Network visibility can provide valuable evidence for incident investigation and response.
Railway OT Recovery
Cybersecurity does not end when an attack is detected.
A resilient railway needs to consider how affected systems can be restored.
- Configuration backups
- System images
- Validated recovery procedures
- Credential recovery
- Network configuration backups
- Spare equipment
- Incident isolation procedures
- Operational fallback procedures
The recovery strategy should reflect the operational importance of the affected system.
Railway Cybersecurity Should Be Lifecycle-Based
Cybersecurity should not begin only after a railway has been deployed.
Requirements
↓
Architecture
↓
Design
↓
Development
↓
Integration
↓
Testing
↓
Commissioning
↓
Operations
↓
Maintenance
↓
Upgrade
↓
Decommissioning
Railway cybersecurity requirements can therefore influence procurement, system architecture, supplier requirements, integration testing, maintenance and operational monitoring.
This lifecycle perspective is one of the reasons railway-specific cybersecurity frameworks are important.
Security by Design in Railway Systems
The strongest time to discover an architectural security problem is before the system is deployed.
Changing a network boundary during design is usually easier than redesigning an operational railway after commissioning.
A security-by-design process should consider:
- Asset identification
- Trust boundaries
- Communication requirements
- Authentication
- Authorization
- Segmentation
- Secure remote access
- Monitoring
- Vulnerability management
- Update mechanisms
- Recovery
Railway Cybersecurity Procurement
Cybersecurity should also be considered when railway operators purchase new systems.
Questions for suppliers can include:
- What communication protocols are used?
- Which interfaces are exposed?
- How is authentication implemented?
- How are privileged accounts managed?
- How is remote access controlled?
- How are vulnerabilities disclosed?
- How are security updates delivered?
- How is configuration backed up?
- What security logs are available?
- How is incident response supported?
- What cybersecurity documentation is provided?
Security requirements should be defined before procurement decisions are finalized rather than treated as an afterthought.
A Practical Railway OT Security Checklist
| Area | Assessment Question | Status |
|---|---|---|
| Asset inventory | Are railway OT assets identified? | ☐ |
| Architecture | Is the complete architecture documented? | ☐ |
| Segmentation | Are important trust boundaries controlled? | ☐ |
| Signalling | Are signalling systems appropriately protected? | ☐ |
| CBTC | Are CBTC communication paths understood? | ☐ |
| Onboard | Are train-side systems included? | ☐ |
| Wayside | Are wayside systems included? | ☐ |
| Remote access | Is vendor and maintenance access controlled? | ☐ |
| Firewall | Are rules aligned with operational requirements? | ☐ |
| Vulnerability | Are known weaknesses tracked? | ☐ |
| Monitoring | Can abnormal network behaviour be detected? | ☐ |
| Recovery | Can important systems be restored? | ☐ |
Common Railway OT Cybersecurity Mistakes
- Treating railway OT as ordinary corporate IT.
- Running aggressive scans before understanding the environment.
- Assuming a firewall automatically makes the architecture secure.
- Using broad network access between unrelated systems.
- Leaving vendor remote access permanently enabled.
- Ignoring onboard systems.
- Ignoring wayside communication.
- Ignoring maintenance networks.
- Ranking every vulnerability only by CVSS.
- Using Shodan results as proof of internal compromise.
- Assuming safety certification equals cybersecurity.
- Failing to document trust boundaries.
- Ignoring recovery requirements.
- Leaving cybersecurity until after deployment.
The Most Important Railway OT Security Question
Do not begin with:
“Which cybersecurity tool should we use?”
Begin with:
“Which digital systems support railway operations, how do they communicate, which trust relationships exist between them, and what could happen if one of those relationships were compromised?”
That question changes the assessment from tool selection to engineering analysis.
What a Professional Railway OT Security Assessment Should Deliver
| Deliverable | Purpose |
|---|---|
| Executive summary | Explain the overall security posture. |
| Asset inventory | Identify important systems. |
| Architecture map | Show communication and trust relationships. |
| Attack surface review | Identify potential exposure. |
| Remote access review | Assess external connectivity. |
| Vulnerability review | Identify relevant technical weaknesses. |
| Configuration review | Assess security controls. |
| Traffic analysis | Validate communication behaviour. |
| Risk assessment | Prioritize findings. |
| Remediation roadmap | Provide practical next steps. |
| Limitations | Clearly document what was not tested. |
From Vulnerability to Engineering Decision
A good railway cybersecurity report should not stop at:
“CVE detected.”
It should explain:
Finding
↓
Affected Asset
↓
Technical Evidence
↓
Network Position
↓
Attack Path
↓
Operational Relevance
↓
Risk Priority
↓
Recommended Control
↓
Verification
This is where cybersecurity becomes useful to engineering and operations teams.
Remote Railway OT Security Review
Not every railway cybersecurity assessment requires intrusive access to live operational equipment.
A significant amount of useful work can be performed remotely when the operator can provide appropriate evidence.
- Network architecture review
- Asset inventory review
- Firewall configuration review
- Remote access review
- External exposure assessment
- Software and firmware review
- Vulnerability intelligence correlation
- Network capture analysis
- Security control review
- Risk prioritization
- Remediation planning
This can provide an independent security perspective while minimizing unnecessary interaction with production railway OT.
When Active Testing Is Appropriate
Active testing can be valuable when properly authorized and controlled.
Suitable environments may include:
- Dedicated railway cybersecurity laboratories
- Development environments
- Test networks
- Staging environments
- Non-production systems
- Specifically approved assessment windows
For live operational railway systems, the testing method should be selected according to the equipment, operational constraints, authorization and potential consequences.
The Cautivra Approach
Cautivra’s approach to railway OT security should begin with evidence rather than assumptions.
Understand
↓
Map
↓
Measure
↓
Validate
↓
Prioritize
↓
Remediate
That means understanding the railway architecture before selecting technical tests, identifying the systems that matter, mapping communication paths, reviewing exposure, correlating vulnerabilities and translating technical findings into operational risk.
The tools are important.
But the engineering interpretation is more important.
Final Perspective
Railway OT cybersecurity is ultimately about protecting a connected operational system.
The railway is not just the train.
It is the interaction between onboard equipment, wayside infrastructure, signalling, train control, communication networks, operations centres, maintenance systems and people.
Protecting one component while ignoring the communication paths around it is not enough.
Map the architecture.
Identify the trust boundaries.
Understand the operational function.
Control remote access.
Segment where appropriate.
Monitor important communication paths.
Assess vulnerabilities in context.
And never allow the assessment itself to become an operational risk.
The strongest railway cybersecurity strategy is not the one with the most tools. It is the one that understands the railway deeply enough to know what must be protected, why it matters and how to reduce risk without compromising the operation it is designed to protect.
Need a Railway OT Cybersecurity Assessment?
Cautivra provides remote, evidence-based cybersecurity reviews for railway and metro operational technology environments.
Depending on scope, an assessment can examine railway OT architecture, signalling environments, CBTC communication paths, network segmentation, remote access, external exposure, software and firmware information, vulnerability intelligence, network evidence and existing security controls.
The objective is to identify meaningful weaknesses, explain their operational relevance and provide a prioritized remediation roadmap.
Request a Railway OT Cybersecurity Assessment
Frequently Asked Questions
What is railway OT cybersecurity?
Railway OT cybersecurity is the protection of operational technology and connected digital systems that support railway functions such as signalling, train control, supervision, communications, maintenance and operational management.
Why is railway cybersecurity different from IT cybersecurity?
Railway OT is connected to operational processes and physical infrastructure. Security decisions therefore need to consider availability, integrity, operational continuity and potential safety implications in addition to conventional information security concerns.
What is CBTC cybersecurity?
CBTC cybersecurity focuses on protecting the digital systems and communication paths involved in Communications-Based Train Control. This can include onboard systems, wayside systems, control centre infrastructure and the networks connecting them.
Is CBTC the same as railway cybersecurity?
No. CBTC is one type of railway train control architecture. Railway cybersecurity covers a much broader environment that can include signalling, interlocking, train communication networks, operations centres, maintenance systems, remote access and other operational technologies.
Can Nmap be used to assess railway OT?
Nmap can support authorized network discovery and service identification, but active scanning should be carefully evaluated before use against operational railway equipment. Passive analysis and configuration review may be more appropriate as an initial step.
Can Shodan find railway OT vulnerabilities?
Shodan can provide external attack surface intelligence, but it cannot by itself establish that an internal railway OT system is vulnerable or reachable. External findings require attribution and technical validation.
Can Wireshark be used for railway cybersecurity?
Yes. Where authorized network captures are available, Wireshark can help analyse protocols, communicating hosts, traffic patterns and unexpected network behaviour.
What standards are relevant to railway cybersecurity?
Relevant frameworks and standards depend on the railway and jurisdiction. CENELEC TS 50701 is specifically focused on railway cybersecurity. IEC 62443 can provide industrial control system cybersecurity principles, while railway system standards such as IEC 62290 address urban guided transport management and command/control systems. IEC 61375-1:2026 addresses train communication network architecture and includes a cybersecurity clause.
Does IEC 62290 cover railway cybersecurity?
IEC 62290 covers urban guided transport management and command/control system principles, functions and system requirements. The 2025 edition explicitly states that the series does not specifically address security issues, so it should not be presented as a standalone railway cybersecurity standard.
Can railway OT cybersecurity be assessed remotely?
Yes. Architecture documentation, asset inventories, firewall configurations, remote access information, software and firmware versions, network captures and external exposure information can support a remote assessment. Active testing of live operational systems requires separate authorization and appropriate controls.
What should a railway OT security assessment deliver?
A useful assessment should provide evidence-based findings, asset and architecture understanding, attack surface observations, vulnerability analysis, risk prioritization and practical remediation recommendations. It should also clearly state the assessment scope and limitations.
Sources and Further Reading
- International Electrotechnical Commission: IEC 62290 series for urban guided transport management and command/control systems.
- International Electrotechnical Commission: IEC 61375-1:2026 for train communication network architecture.
- CENELEC: CLC/TS 50701 Railway Applications — Cybersecurity.
- Europe’s Rail Joint Undertaking: Cybersecurity Specification and railway cybersecurity interoperability work.
