Cloud & data centres | Modelled case study
Make service-mesh certificate rotation measurable before PQC change
Can every workload receive, activate, validate, and retire new trust without hidden static certificates?
The modelled organisation
A recognisable problem reaches the operating agenda
This composite scenario follows the Platform SRE · Service Mesh · PKI functions. It is grounded in the cited problem context but does not identify a real customer.
Operating environment
A cloud or data-centre operator runs multi-tenant key services, workload identity, certificate automation, regional infrastructure, and customer-facing assurance processes.
What is at stake
A shared trust failure can cross tenants or regions, while an unsafe rotation can interrupt many downstream services at once.
Situation
Automated issuance creates a false sense of agility when sidecars, batch jobs, appliances, bootstrap credentials, and offline workers escape normal rotation.
Event that forces action
Mesh migration, CA replacement, certificate outage, or post-quantum transport experiment.
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.
workload identities
service-mesh control plane
certificate issuers
rotation, validation, and retirement telemetry
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
Automated issuance creates a false sense of agility when sidecars, batch jobs, appliances, bootstrap credentials, and offline workers escape normal rotation.
Frame the decision the owners must make
Can every workload receive, activate, validate, and retire new trust without hidden static certificates?
Apply QNSI to the controlled boundary
Inventory workload identities, issuers, algorithms, TTLs, exceptions, and last-observed rotation in QNSI.
Leave the team with a concrete result
A mesh crypto-agility scorecard with stale identity owners, rotation SLOs, and blocked migration cohorts.
Prove the result in the organisation's environment
Platform teams test live rotation, failure modes, time skew, control-plane outage, and cryptographic negotiation.
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 mesh crypto-agility scorecard with stale identity owners, rotation SLOs, and blocked migration cohorts.
Independent validation boundary
Platform teams test live rotation, failure modes, time skew, control-plane outage, and cryptographic negotiation.
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.