Cookies on this site. Help us understand what works and improve your experience. Essential cookies keep the site working. With your permission, our visit insights and Google Analytics measure usage, and Google Ads measures advertising. Optional cookies are not required to use the free kit. Change your choice anytime in Cookie settings. Privacy policyCookie policy
Back up information, software and systems regularly and test that restores work.
Is it mandatory? Not automatically. You must consider this control in your Statement of Applicability (6.1.3 d). Include it if your risk assessment, laws, contracts or business needs require it; if you exclude it, write down a justification an auditor will accept.
Why this control matters
Teams should turn backup intentions into an operated recovery process, not just a storage routine. The practical challenge is to connect scope, retention, restore testing, and accountability so the process can survive a real loss event and still produce traceable evidence for management and auditors. Distinguish backups from redundancy and incident response, because those controls solve different availability problems and often fail when treated as interchangeable.
Common auditor findings to check for
Potential gaps to test in your own environment, not a claim about observed audit frequency.
Critical databases are backed up, but application configuration, keys, and virtual machine images are omitted, leaving restore points incomplete after an outage.
Restore testing exists in name only; the team records that a backup job succeeded, but no one verifies application start-up, data integrity, or recovery time.
Backup retention, offsite copy, and immutable storage settings are inconsistent across platforms, creating avoidable exposure if ransomware encrypts both primary and secondary copies.
How you can implement it
Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.
Assign the system owner, infrastructure lead, and business process owner to define backup scope by recovery point target, legal retention, and restore priority. Include software, configuration, secrets vault exports, and dependencies such as databases and storage snapshots. Record exceptions with risk acceptance and review them after major changes or supplier changes.
Use the Backup & Recovery Log to record job success, failed runs, media location, encryption status, and immutable copy checks. Add a restore-test record that captures date, tester, target system, steps performed, integrity checks, and whether the restored system met the intended recovery window and data completeness expectations.
Separate operational monitoring from recovery assurance. A daily automated check can confirm that scheduled jobs ran, but only a controlled restore test demonstrates usability. Include a quarterly sample of critical systems and a full-path exercise for at least one high-value service after infrastructure redesign, major patching, or storage migration.
When failures occur, open corrective action rather than simply rerunning the task. Capture root cause, affected datasets, lost backup window, temporary compensating actions, and the decision on whether to re-seed backups. Keep the procedure aligned to continuity plans so escalation, vendor contact, and declaration criteria are already defined before disruption happens.
What an auditor will ask to see
Completed Backup & Recovery Procedure showing scope, RPO/RTO assumptions, and named responsibilities for backup administration and restore approval.
Backup & Recovery Log entries with job IDs, success or failure status, media location, immutable-copy confirmation, and retained period.
Restore test report demonstrating restoration of a sample database or server, integrity validation, application check, and signed business acceptance of results.
Baseline documents in the kit
These free kit documents help you document or evidence A.8.13. Each one is tailored to your organization when you build your kit.
Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.
For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.
Get these documents tailored to your organization
109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.