34 Regular backups (Essential)
Regular backups of important new/changed data, software and configuration settings, stored disconnected, retained for at least three months. Test restoration initially, annually and when IT infrastructure changes.
4
artefacts
2
held by a system
1
at each review
easy
to go live
Cloud console / configuration management
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Configuration / tooling output demonstrating the strategy · Cloud console / configuration management
- Records showing ongoing operation · Document repository
periodic reviewEvidence produced at each review
- Evidence the mitigation strategy is implemented and maintained: Regular backups · Backup / DR tooling
governing documentDocuments that govern the control
- Coverage across in-scope systems · Policy repository / GRC workspace
First move
Automate the pull from your Cloud console / configuration management. Configuration snapshots and change history from the cloud console or IaC repository, diffed against the baseline.
Common gaps auditors find
- Strategy partially deployed (not all systems)
- No evidence of ongoing maintenance
- Effectiveness rating not met
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 sheet33 Capture network traffic (Limited) · 35 Business continuity and disaster recovery plans (Very Good)