Telecommunications | Modelled case study
Inventory PKI dependencies across 5G network functions
Which network functions, vendors, and interfaces depend on shared trust anchors or non-agile certificate profiles?
The modelled organisation
A recognisable problem reaches the operating agenda
This composite scenario follows the Mobile Core Security · Network Architecture · PKI functions. It is grounded in the cited problem context but does not identify a real customer.
Operating environment
A telecommunications provider operates mobile-core, access, subscriber, provisioning, network-cloud, and vendor-managed systems at national scale.
What is at stake
Trust must rotate across enormous device and network populations without disrupting service, roaming, lawful operations, or long-term subscriber confidentiality.
Situation
Cloud-native 5G adds workload identities while legacy operations, roaming, vendor appliances, and management systems retain separate PKI paths.
Event that forces action
Standalone core rollout, vendor swap, certificate incident, or quantum-readiness assessment.
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.
5G core network functions
service-based interfaces
vendor certificate authorities
orchestration and trust-anchor distribution
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
Cloud-native 5G adds workload identities while legacy operations, roaming, vendor appliances, and management systems retain separate PKI paths.
Frame the decision the owners must make
Which network functions, vendors, and interfaces depend on shared trust anchors or non-agile certificate profiles?
Apply QNSI to the controlled boundary
Use QNSI to map certificate issuers, algorithms, endpoints, vendors, management domains, and rotation ownership.
Leave the team with a concrete result
A 5G trust-domain map highlighting shared roots, stranded functions, and testable migration cohorts.
Prove the result in the organisation's environment
The operator validates 3GPP profiles, vendor support, roaming interoperability, performance, and lawful operational requirements.
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 5G trust-domain map highlighting shared roots, stranded functions, and testable migration cohorts.
Independent validation boundary
The operator validates 3GPP profiles, vendor support, roaming interoperability, performance, and lawful operational requirements.
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.