PS-02 Redundancy model
Deliver the cloud service from two mutually redundant sites that both satisfy the provider's physical security requirements, sit far enough apart to give operational redundancy meeting agreed availability levels, and tes
4
artefacts
0
held by a system
1
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Failover test report from the most recent annual redundancy exercise · Backup / DR tooling
governing documentDocuments that govern the control
- Site pair topology diagram showing the separation distance between redundant locations · Policy repository / GRC workspace
- Availability clauses of the service level agreement mapped onto the redundancy design · Policy repository / GRC workspace
- Capacity figures proving the surviving site can carry full production load · Policy repository / GRC workspace
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- Second site sized only for partial load so failover silently degrades the service
- Redundancy asserted on paper but never exercised within the last twelve months
- Locations placed too close together to survive a single regional event
- Secondary location held to weaker physical security controls than the primary
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 sheetPS-01 Physical Security and Environmental Control Requirements · PS-03 Perimeter Protection