Why CBTC Changes the Attack Surface
Communications-Based Train Control replaces fixed-block signalling with continuous, bidirectional data exchange between trains and the wayside. The result is moving-block operation, shorter headways, and in many deployments Grade of Automation 4 driverless service. It also means that train separation now depends on a data communication system that is, by design, reachable from the trackside environment.
Most deployed CBTC data communication systems use IEEE 802.11 radios in unlicensed 2.4 GHz or 5.8 GHz bands. Newer projects are migrating toward private LTE. Either way, the radio segment falls within what EN 50159 classifies as an open transmission system: one where the operator cannot rule out unauthorised access, and where the safety protocol must therefore defend against repetition, deletion, insertion, resequencing, corruption, delay, and masquerade.
Public reporting on confirmed, malicious CBTC compromises remains sparse. Responders should not read that silence as evidence of safety. Assessments by ENISA and transit-sector bodies such as APTA consistently identify wireless train-to-wayside communications, legacy maintenance access, and supplier connectivity as priority risks. Rail operators need a response capability that is ready before the first anomalous alarm, not one improvised during it.