OPS-24 Separation of Datasets in the Cloud Infrastructure
Separate cloud customer data stored and processed on shared virtual and physical resources strictly, following a documented approach derived from the risk analysis, so that the confidentiality and integrity of that data
4
artefacts
2
held by a system
1
at each review
easy
to go live
Document repository
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Risk analysis output that justified the chosen separation approach · Document repository
- Isolation configuration of tenant identifiers, network and storage for a sampled customer · Cloud console / configuration management
periodic reviewEvidence produced at each review
- Test results from a deliberate cross tenant access attempt · Source control / CI pipeline
governing documentDocuments that govern the control
- Tenant separation design describing the isolation mechanism at each layer · Document repository
First move
Automate the pull from your Document repository. Version-controlled document with owner, approval and review date as metadata.
Common gaps auditors find
- Isolation enforced in the application layer alone over a shared database with no row level control
- Separation design not revisited after a shared caching or messaging component was introduced
- Cross tenant access asserted in the design but never actually tested
- Administrative tooling able to traverse tenants without restriction or logging
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheetOPS-23 Managing Vulnerabilities, Malfunctions and Errors - System Hardening · PI-01 Documentation and safety of input and output interfaces