In most sectors, an unmanaged key is a security risk. In transport it is also a safety risk. Whoever can open a relay house, a traction substation or a tunnel service door is physically close to systems that keep vehicles moving and people safe. Knowing exactly who can be where is not an administrative nicety, it is part of operating responsibly.
The operational reality works against that knowledge:
Every gap between who should have access and who can get in is a gap in both your security posture and your safety case.
Transport is one of the sectors explicitly in scope of both the CER Directive and NIS2. CER requires critical entities to strengthen the resilience of their physical infrastructure against sabotage and other threats. NIS2 requires appropriate policies for access to premises, because physical entry to a relay house or control room can compromise the digital systems inside.
For a transport operator, the practical test is simple: can you show, for any location and any date, who held access rights, on whose authority, and when those rights changed? Key2XS makes that a query instead of a project. Every key right traces back to an identity, a role and an approval, in one tamper-evident audit trail.
Key2XS is middleware between the IAM system you already run and the digital locking system already on your infrastructure. Nothing about your locks, keys or locking plan changes.
A typical flow: a contractor is engaged for switch maintenance on a corridor. The crew members are registered in the IAM under the project, and Key2XS translates the project assignment into key rights for exactly the relay houses and technical buildings on that corridor. Crew composition changes mid-project: the change in the IAM updates the key rights in near real-time. When the project ends, every crew member's access ends with it, at every layer of subcontracting, because the rights follow the registration rather than the metal.
For your own field staff, access follows team and region assignments the same way, and the leaver process that disables accounts also closes every door on the network in the same movement.
Implementation respects operational tempo: a standard integration is live in under two hours through pre-built connectors, with no custom development and no downtime for running systems.
The platform is engineered for 99.99% availability, matching an environment where operations run around the clock, and all communication is encrypted with TLS 1.3 in transit and AES-256 at rest.
