Rail & public transit | Modelled case study
Stage a PKI transition for rail signalling support systems
Which support, management, and communications components can change trust without affecting safe train movement?
The modelled organisation
A recognisable problem reaches the operating agenda
This composite scenario follows the Rail Cybersecurity · Signalling Engineering · Safety Assurance functions. It is grounded in the cited problem context but does not identify a real customer.
Operating environment
A transit operator runs signalling support, fare collection, station systems, fleet maintenance, mobile channels, depots, and supplier diagnostics.
What is at stake
Trust changes must not interfere with safe movement, rider access, revenue collection, maintenance release, or recovery from field connectivity gaps.
Situation
Long-lived signalling estates combine safety-certified equipment, vendor maintenance tools, control centres, and telecom links with limited test windows.
Event that forces action
Certificate expiry, signalling renewal, supplier change, or cryptographic modernization.
Concrete system boundary
Systems this case study puts in scope
The model is specific about the operational surfaces that must be discovered, changed, or independently checked.
signalling support systems
operations and maintenance networks
certificate authorities
staged trust and rollback boundary
Modelled case study walkthrough
How this organisation would use QNSI
The walkthrough connects the real-world problem to a bounded QNSI contribution and an independently reviewable result.
Recognise the operating condition
Long-lived signalling estates combine safety-certified equipment, vendor maintenance tools, control centres, and telecom links with limited test windows.
Frame the decision the owners must make
Which support, management, and communications components can change trust without affecting safe train movement?
Apply QNSI to the controlled boundary
Group certificates, algorithms, issuers, equipment baselines, safety criticality, and maintenance windows in QNSI.
Leave the team with a concrete result
A signalling-support trust transition plan with lab evidence, rollout cohorts, rollback, and deferred assets.
Prove the result in the organisation's environment
The operator and safety authority validate scope, fail-safe behavior, certification impact, test coverage, and operational acceptance.
What useful success looks like
A decision artifact plus proof from the real environment
The model stops at a target result. It becomes an actual case study only when a customer produces and independently validates this evidence in production.
Decision artifact
A signalling-support trust transition plan with lab evidence, rollout cohorts, rollback, and deferred assets.
Independent validation boundary
The operator and safety authority validate scope, fail-safe behavior, certification impact, test coverage, and operational acceptance.
Real-world problem grounding
Primary sources behind the model
These sources establish the external requirement, failure mode, or risk context used to model this case. They do not endorse HEOSSI or prove that QNSI completed the scenario.
Customer evidence status
This is modelled, not a customer claim
The organisation is a composite and the result is a target state. This page does not prove a deployment, customer outcome, certification, legal conclusion, regulator endorsement, or completed control.