Security
SecDT: A Profile-Based Security Layer for TRDP Communications
arXiv cs.NI0 views
arXiv:2609.03133v2 Announce Type: replace-cross Abstract: The Train Real-time Data Protocol (TRDP) is widely used on rolling stock but it provides limited native support for cryptographic protection. Furthermore, the multicast traffic profile used in TRDP Process Data to exchange critical information between onboard subsystems makes the introduction of cryptographic protection a challenge. This paper presents a lightweight security layer for secure TRDP communication that implements a number of security profiles built around modern cryptographic algorithms. This additional layer relies on an On-board Key Management System (OKMS) for both security profile negotiation, dynamic key distribution and key lifecycle management. The security profiles allow for cryptographic agility and flexibility, ranging from simple authentication to Authenticated Encryption with Associated Data (AEAD) algorithms. The security profile negotiation procedure guarantees all TRDP End Devices (ED) on a common Communication ID (ComID) share the same security profile and can therefore process each other's messages. A prototype implementation based on mbedTLS and Arm Platform Security Architecture (PSA) was developed and evaluated. Experimental results demonstrate manageable overhead, suitable for the real-time and time-sensitive communication found on rolling stock.
Source:https://arxiv.org/abs/2609.03133PreviousProjecting Latent RL Actions: Towards Generalizable and Scalable Graph Combinatorial OptimizationNextHow I built EasyShare: peer-to-peer file sharing in Java
Related posts
5 Stars for sale: Inside the underground fake review trade
0Hacker News New
Show HN: Hands-on security exercises for students and instructors
0Hacker News Show
Investors Dish on New Startups & What They'd Back Next
0Dark Reading

NVIDIA Brev security breach may have exposed SSH keys used to access customer VMs — investigation finds unauthorized activity spanning 16 days, but no evidence of misuse
0Tom's Hardware
Testing and rebuilding Node.js snapshot artifacts after CVE-2026-106074
0dev.to Node
From predictable IDs to workflow risk: analyzing Node.js CVE-2026-106074
0dev.to Node