Penetration Testing of Automated Train Systems

Security Analysis of Networked Vehicle Platforms in the Railway Context

Automation in rail transport is advancing. Modern trains monitor their surroundings using cameras and other sensors, perform self-tests, communicate with edge systems along the route, and transmit large amounts of recorded data to data centers.

From a security perspective, this results in highly complex, distributed systems with the following characteristics:

  • On-board vehicle networks with industrial and automotive
  • components
  • Sensor boxes for environmental detection
  • High-availability wireless connections
  • Edge processing near the track
  • Centralized data storage in the data center
  • Vehicles that are partially physically accessible in public spaces

A penetration test of such systems differs significantly from traditional IT tests. It involves a combination of IT, OT, and embedded security analysis.

System Architecture of Automated Trains

Automated or semi-automated trains typically consist of several safety-critical components:

Inside the vehicle itself are sensor boxes equipped with cameras, environmental detection systems, and other measurement components. These are often installed at both the front and rear of the train to cover bidirectional travel.

The sensors detect:

  • The area surrounding the tracks
  • The condition of the infrastructure
  • Objects in the danger zone
  • Movements near platforms

The data is processed on the vehicle via a dedicated Ethernet network. Serial interfaces often exist for individual components. In many architectures, this network is logically or physically separated from the rest of the IT network.

For training, analysis, or maintenance purposes, the collected data is regularly transmitted to edge systems. From there, it is forwarded via dedicated fiber-optic links to central data centers.

Wireless backhaul connections represent a critical communication layer in this context.

Threat Model

The threat model in such projects encompasses several levels:

  1. In-vehicle manipulation
  2. Wireless attacks on the communication infrastructure
  3. Compromise of edge systems
  4. Data manipulation during transmission
  5. Data privacy and integrity risks
  6. Physical access to the vehicle

A key characteristic: Vehicles may be left unattended on track facilities for periods of time and be physically accessible. This significantly expands the attack surface.

In-vehicle networks and embedded security

Within the train, there is often a completely separate Ethernet network for connecting the sensors.

Security-related questions include:

  • Are default configurations used in sensors?
  • Are there hard-coded access credentials?
  • Are serial interfaces accessible or secured?
  • Can firmware versions be manipulated?
  • Are there debug or maintenance interfaces?

Components implemented by third-party vendors are particularly critical. If security configurations are not transparently documented, there is an increased risk due to incorrect assumptions or unhardened default settings.

A penetration test analyzes both network segmentation and the actual enforceability of isolation.

Wireless Communication and Backhaul Security

Vehicle data is often transmitted via wireless high-availability connections.

Security-related aspects include:

  • Enforcement of modern encryption standards
  • Protection against rogue access points
  • Authentication mechanisms
  • Protection against downgrade attacks
  • Manipulation of configuration parameters

Particularly for WiFi-based solutions in the 6 GHz band, it must be verified whether strong authentication is enforced and whether unauthorized devices can connect.

Multi-path TCP connections or tunneled SSH connections must also be checked for integrity and proper key management. An encrypted connection alone does not guarantee security if key management or host verification are inadequately implemented.

 

Data Transfer and Integrity

The recorded sensor data is transmitted regularly. In typical scenarios, large volumes of data are generated within a few hours,which are automatically fed into edge systems and then transmitted to the data center.

Critical areas for review are:

  • Can data be manipulated during transmission?
  • Is data replay possible?
  • Are hashes or signatures used?
  • Is an integrity check implemented?
  • Is it possible to inject synthetic sensor data?

Data integrity is essential, especially for systems that use environment detection for training purposes. Manipulated training data can have long-term effects on decision-making models.

Edge Systems and Access Control

Edge systems along the route often serve as caching or preprocessing nodes.

Typical questions in a penetration test:

  • Are there administrative accounts without sufficient hardening?
  • Are jump hosts properly secured?
  • Are roles and permissions clearly separated?
  • Are there only high-privileged accounts?

Systems without low-privileged user roles pose an increased risk, as every user potentially has extensive privileges.

Connections to storage systems must also be reviewed, especially if they are connected via client authentication mechanisms.

Physical Security

Physical access is a factor that is often underestimated. If a train is parked on a siding without video surveillance or physical security, the following scenarios must be considered:

  • Connecting a personal device to internal ports
  • Access to sensor boxes
  • Tampering with cabling
  • Replacement of components
  • Access to maintenance interfaces

Physical security is not a theoretical side issue in such projects, but a real component of the threat model.

Data Protection and Regulatory Aspects

In environmental detection systems, camera images are regularly captured that may show people on platforms or in the track area.

Unacceptable risks in this context include, in particular:

  • Uncontrolled long-term storage
  • Lack of access restrictions
  • Insufficient anonymization
  • Unclear data processing purposes

In addition to technical security, compliance with data protection requirements must therefore also be verified.

Special Considerations in Penetration Testing of Automated Train Systems

Such a penetration test differs methodologically from traditional IT tests:

  • Combination of IT, OT, and embedded testing
  • Analysis of wireless high-availability networks
  • Evaluation of integrity mechanisms for sensor data
  • Investigation of physical attack vectors
  • Review of rights and role concepts
  • Validation of network segmentation within the vehicle

In addition, parts of the architecture may still be adjusted during the project phase. Therefore, scope definition and risk assessment must be closely coordinated.

Key security finding

Automated train systems are not isolated vehicles, but networked, data-intensive platforms with:

  • Embedded systems
  • Wireless communication links
  • Edge computing components
  • Centralized data storage
  • Physical exposure in public spaces

The security-critical points lie not only in encryption or the transport channel, but in the entire chain comprising:

Collection → Processing → Transmission → Storage → Reuse.

A thorough penetration test must technically analyze this entire chain and assess whether the integrity, confidentiality, and availability of the systems are realistically guaranteed.

Archives

Security Analysis of Networked Vehicle Platforms in the Railway Context

Automation in rail transport is advancing. Modern trains monitor their surroundings using cameras and other sensors, perform self-tests, communicate with edge systems along the route, and transmit large amounts of recorded data to data centers.

From a security perspective, this results in highly complex, distributed systems with the following characteristics:

  • On-board vehicle networks with industrial and automotive
  • components
  • Sensor boxes for environmental detection
  • High-availability wireless connections
  • Edge processing near the track
  • Centralized data storage in the data center
  • Vehicles that are partially physically accessible in public spaces

A penetration test of such systems differs significantly from traditional IT tests. It involves a combination of IT, OT, and embedded security analysis.

System Architecture of Automated Trains

Automated or semi-automated trains typically consist of several safety-critical components:

Inside the vehicle itself are sensor boxes equipped with cameras, environmental detection systems, and other measurement components. These are often installed at both the front and rear of the train to cover bidirectional travel.

The sensors detect:

  • The area surrounding the tracks
  • The condition of the infrastructure
  • Objects in the danger zone
  • Movements near platforms

The data is processed on the vehicle via a dedicated Ethernet network. Serial interfaces often exist for individual components. In many architectures, this network is logically or physically separated from the rest of the IT network.

For training, analysis, or maintenance purposes, the collected data is regularly transmitted to edge systems. From there, it is forwarded via dedicated fiber-optic links to central data centers.

Wireless backhaul connections represent a critical communication layer in this context.

Threat Model

The threat model in such projects encompasses several levels:

  1. In-vehicle manipulation
  2. Wireless attacks on the communication infrastructure
  3. Compromise of edge systems
  4. Data manipulation during transmission
  5. Data privacy and integrity risks
  6. Physical access to the vehicle

A key characteristic: Vehicles may be left unattended on track facilities for periods of time and be physically accessible. This significantly expands the attack surface.

In-vehicle networks and embedded security

Within the train, there is often a completely separate Ethernet network for connecting the sensors.

Security-related questions include:

  • Are default configurations used in sensors?
  • Are there hard-coded access credentials?
  • Are serial interfaces accessible or secured?
  • Can firmware versions be manipulated?
  • Are there debug or maintenance interfaces?

Components implemented by third-party vendors are particularly critical. If security configurations are not transparently documented, there is an increased risk due to incorrect assumptions or unhardened default settings.

A penetration test analyzes both network segmentation and the actual enforceability of isolation.

Wireless Communication and Backhaul Security

Vehicle data is often transmitted via wireless high-availability connections.

Security-related aspects include:

  • Enforcement of modern encryption standards
  • Protection against rogue access points
  • Authentication mechanisms
  • Protection against downgrade attacks
  • Manipulation of configuration parameters

Particularly for WiFi-based solutions in the 6 GHz band, it must be verified whether strong authentication is enforced and whether unauthorized devices can connect.

Multi-path TCP connections or tunneled SSH connections must also be checked for integrity and proper key management. An encrypted connection alone does not guarantee security if key management or host verification are inadequately implemented.

 

Data Transfer and Integrity

The recorded sensor data is transmitted regularly. In typical scenarios, large volumes of data are generated within a few hours,which are automatically fed into edge systems and then transmitted to the data center.

Critical areas for review are:

  • Can data be manipulated during transmission?
  • Is data replay possible?
  • Are hashes or signatures used?
  • Is an integrity check implemented?
  • Is it possible to inject synthetic sensor data?

Data integrity is essential, especially for systems that use environment detection for training purposes. Manipulated training data can have long-term effects on decision-making models.

Edge Systems and Access Control

Edge systems along the route often serve as caching or preprocessing nodes.

Typical questions in a penetration test:

  • Are there administrative accounts without sufficient hardening?
  • Are jump hosts properly secured?
  • Are roles and permissions clearly separated?
  • Are there only high-privileged accounts?

Systems without low-privileged user roles pose an increased risk, as every user potentially has extensive privileges.

Connections to storage systems must also be reviewed, especially if they are connected via client authentication mechanisms.

Physical Security

Physical access is a factor that is often underestimated. If a train is parked on a siding without video surveillance or physical security, the following scenarios must be considered:

  • Connecting a personal device to internal ports
  • Access to sensor boxes
  • Tampering with cabling
  • Replacement of components
  • Access to maintenance interfaces

Physical security is not a theoretical side issue in such projects, but a real component of the threat model.

Data Protection and Regulatory Aspects

In environmental detection systems, camera images are regularly captured that may show people on platforms or in the track area.

Unacceptable risks in this context include, in particular:

  • Uncontrolled long-term storage
  • Lack of access restrictions
  • Insufficient anonymization
  • Unclear data processing purposes

In addition to technical security, compliance with data protection requirements must therefore also be verified.

Special Considerations in Penetration Testing of Automated Train Systems

Such a penetration test differs methodologically from traditional IT tests:

  • Combination of IT, OT, and embedded testing
  • Analysis of wireless high-availability networks
  • Evaluation of integrity mechanisms for sensor data
  • Investigation of physical attack vectors
  • Review of rights and role concepts
  • Validation of network segmentation within the vehicle

In addition, parts of the architecture may still be adjusted during the project phase. Therefore, scope definition and risk assessment must be closely coordinated.

Key security finding

Automated train systems are not isolated vehicles, but networked, data-intensive platforms with:

  • Embedded systems
  • Wireless communication links
  • Edge computing components
  • Centralized data storage
  • Physical exposure in public spaces

The security-critical points lie not only in encryption or the transport channel, but in the entire chain comprising:

Collection → Processing → Transmission → Storage → Reuse.

A thorough penetration test must technically analyze this entire chain and assess whether the integrity, confidentiality, and availability of the systems are realistically guaranteed.

Related

chevron-right