Aviation | Modelled case study
Inventory certificates across airport operational technology
Which safety or continuity functions share issuers, expired trust, or unmanaged vendor certificates?
The modelled organisation
A recognisable problem reaches the operating agenda
This composite scenario follows the Airport CISO · Baggage Systems · Airfield Operations functions. It is grounded in the cited problem context but does not identify a real customer.
Operating environment
An airline, airport, or maintenance organisation coordinates loadable software, airport OT, maintenance records, crew identity, partners, and controlled configuration baselines.
What is at stake
Cryptographic change must preserve airworthiness evidence, operational continuity, approved configuration, and accountable access across a safety-regulated ecosystem.
Situation
Baggage, bridges, fuel, access, surveillance, airfield lighting, and facilities systems are procured separately but operate as one interconnected airport.
Event that forces action
Part-IS readiness, terminal expansion, or certificate-driven outage.
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.
baggage and airfield systems
building and security controls
vendor appliances
certificate issuers and dependencies
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
Baggage, bridges, fuel, access, surveillance, airfield lighting, and facilities systems are procured separately but operate as one interconnected airport.
Frame the decision the owners must make
Which safety or continuity functions share issuers, expired trust, or unmanaged vendor certificates?
Apply QNSI to the controlled boundary
Map airport OT certificates, algorithms, endpoints, vendors, owners, renewal paths, and operational criticality in QNSI.
Leave the team with a concrete result
An airport certificate concentration map with common roots, renewal failures, and safety-linked priorities.
Prove the result in the organisation's environment
The airport tests operational continuity, safety interfaces, supplier support, failover, and regulated change.
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
An airport certificate concentration map with common roots, renewal failures, and safety-linked priorities.
Independent validation boundary
The airport tests operational continuity, safety interfaces, supplier support, failover, and regulated change.
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.