A passenger rail operator asked ioSENTRIX to test the security of its communication-based train control system. A successful attack could stop operations for days and put passengers at risk.
Engagement details
Client
Passenger rail operator
System
Communication-based train control (CBTC) in service for several years
Segmented networks, proprietary equipment and several ICS systems
Environment
Lab replica of production, without live trains
Engagement
A multi-week engagement
Verified
Fixes re-assessed by ioSENTRIX
Tested by
ioSENTRIX ICS and network testers
Our approach
How did ioSENTRIX approach it?
There are no open testing standards for much proprietary rail and ICS software, so there was nothing for a scanner to check against. Finding this took learning how the equipment works and testing it by hand in a production-like lab.
Severity was rated against NIST standards. The report gave the operator a risk assessment of the whole system and recommendations it could act on without stopping a live service.
What we found
What did ioSENTRIX find?
From an exposed segment to the nodes that control train communications.
Theme · NetworkFinding 1
Unpatched bridging nodes let testers cross segments
The nodes that connected several segments ran unpatched Windows, left unpatched because the network was air-gapped. From an exposed segment, our testers compromised those nodes, then pivoted from them into other segmented networks.
Business impact. Segmentation slowed an attacker down but did not stop one from reaching operational systems.
Theme · ICSFinding 2
Train communication nodes could be reached and shut down
Our testers gained access to sensitive nodes that control train system communication. In the lab replica, simulated shutdowns of several trains produced an outage across different operating regions.
Business impact. An attack of this kind could halt service, cost days of downtime and put passenger safety at risk.
One chain from an exposed segment to a simulated multi-region outage
One chain · segment to train control
1Exposed segmentinitial foothold
2Pivot nodessegments connected
3Train commscontrol nodes reached
Outcome: Simulated outage (trains stopped across regions)
The impact
What changed as a result?
Starting from one exposed network segment, our testers pivoted across segmented networks to the nodes that control train communications, and simulated shutdowns that caused an outage across operating regions in the lab. The client fixed the findings and ioSENTRIX re-assessed them.
1
exposed network segment was enough to start
35+
findings, 4 of them Critical
0
live trains touched: every test ran in a lab replica
How many findings, and how severe?
35+ findings in total, including 4 Critical and 10 High.
Critical 4
High 10
Medium
Low
What changed after the test?
What changed in the train control environment
Area
Before the test
After remediation
Segmentation
Unpatched Windows on bridging nodes allowed pivoting between segments
Fixes implemented by the operator’s technical staff
Train communications
Control nodes were reachable; simulated shutdowns caused a multi-region outage in the lab
Fixes implemented, then re-assessed by ioSENTRIX
Incident response
The plan did not account for these attack paths
The new threats were added to the incident response plan
✓Verification: Fixes re-assessed by ioSENTRIX.
Key insight
Built to fail safe, the system had not been built to keep an attacker out.
Lessons
Lessons for operators of industrial systems
01
Air-gapped is not patched
The nodes bridging segments ran unpatched Windows because the network was air-gapped. Isolation delayed patching; it did not remove the risk.
Details in this case study are anonymised and generalised. Methods that could harm other products are withheld.
FAQ
Frequently asked questions
What did ioSENTRIX test in this case study?
A passenger rail operator asked ioSENTRIX to test the security of its communication-based train control system. A successful attack could stop operations for days and put passengers at risk.
What was the most serious issue?
Unpatched bridging nodes let testers cross segments. Segmentation slowed an attacker down but did not stop one from reaching operational systems.
How many findings were there, and how severe?
35+ findings in total, including 4 Critical and 10 High.
Were the fixes verified?
Fixes re-assessed by ioSENTRIX.
Which ioSENTRIX service does this case study cover?
ICS, IoT and IIoT penetration testing, delivered by the ioSENTRIX ICS and network testers.
Which standards does this align with?
NIST SP 800-82 Rev. 3, Guide to Operational Technology (OT) Security. These are cited as alignment guidance, not a compliance claim.
How to get started
Ready to strengthen your security? Fill out our quick form, and a cybersecurity expert will reach out to discuss your needs and next steps.