6.14.2 Redundancies
Availability of information processing facilities through redundancy applies as the base guidance requires, read as covering the facilities that process personal data.
3
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
- Testing evidence · Document repository
governing documentDocuments that govern the control
- Redundancy design for facilities processing personal data · Policy repository / GRC workspace
- Assessment that redundant copies are protected to the same standard · 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
- Redundancy achieved by replicating personal data into a location whose controls were never assessed
- Redundant copies falling outside the retention and deletion regime
- Redundancy assumed from the provider with no evidence
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 sheet6.14.1 Information security continuity · 6.15.1 Compliance with legal and contractual requirements