A.8.14 Redundancy of information processing facilities
Build enough redundancy into processing facilities to meet availability requirements.
12
artefacts
2
held by a system
2
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
- Resource utilization monitoring reports · SIEM / log platform
- Recorded test execution logs · Backup / DR tooling
periodic reviewEvidence produced at each review
- Risk assessment report for single points of failure · Policy repository / GRC workspace
- Change management records for redundancy components · Ticketing / ITSM
governing documentDocuments that govern the control
- Redundancy architecture diagram · Policy repository / GRC workspace
- High availability design specification · Document repository
- Capacity forecast spreadsheet · Policy repository / GRC workspace
- Service level agreement availability matrix · Vendor register / contract repository
- Failover test plan · Policy repository / GRC workspace
- Post-test analysis and corrective action register · Policy repository / GRC workspace
- Scheduled maintenance calendar · Document repository
- Maintenance completion certificates · Document repository
First move
Mostly documents and reviews. Pull the 2 system-held artefacts from your SIEM / log platform on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.
Common gaps auditors find
- reliance on undocumented manual backups
- absence of regular failover drills
- capacity forecasts not aligned with business growth
- maintenance activities not tracked centrally
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 sheet