Cloud & data centres | Modelled case study
Prove tenant separation in a multi-tenant cloud key service
Can an operator, software defect, or compromised tenant cross the intended cryptographic boundary?
The modelled organisation
A recognisable problem reaches the operating agenda
This composite scenario follows the Cloud Platform · Security Architecture · SaaS Assurance 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
Per-tenant key labels do not prove separate authorization, wrapping hierarchy, audit visibility, backup, and deletion behavior.
Event that forces action
Enterprise onboarding, shared-service redesign, or a customer asks for customer-managed custody.
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.
tenant key namespaces
authorization and policy engine
operator control plane
backup and recovery key paths
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
Per-tenant key labels do not prove separate authorization, wrapping hierarchy, audit visibility, backup, and deletion behavior.
Frame the decision the owners must make
Can an operator, software defect, or compromised tenant cross the intended cryptographic boundary?
Apply QNSI to the controlled boundary
Use QNSI key and policy records to identify tenant ownership, provider boundary, operations, access roles, and lifecycle evidence.
Leave the team with a concrete result
A tenant-custody assurance map with tested isolation cases, privileged paths, and residual shared dependencies.
Prove the result in the organisation's environment
The provider must perform adversarial authorization tests, recovery tests, deletion verification, and independent architecture review.
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 tenant-custody assurance map with tested isolation cases, privileged paths, and residual shared dependencies.
Independent validation boundary
The provider must perform adversarial authorization tests, recovery tests, deletion verification, and independent architecture review.
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.