
Backup Requirements in ISO 27001, SOC 2 and PDPA
Every major framework asks the same three things of your backups: that they exist by design (a policy), that they run as designed (monitoring and alerts), and that they restore when needed (tested recovery).
Every major framework asks the same three things of your backups: that they exist by design (a policy), that they run as designed (monitoring and alerts), and that they restore when needed (tested recovery). Here is how ISO 27001, SOC 2 and Malaysia's PDPA each phrase those demands, and the evidence that satisfies all three at once.
The three demands every framework makes
Frameworks differ in vocabulary, not in substance. Strip the language away and each one wants proof of the same three layers:
Designed: a written, owned, current statement of what is backed up, how often, kept how long. (The policy.)
Running: evidence the design operates in practice: verification that backups arrive, and alerts when they don't.
Restorable: evidence of tested recovery: real restores, performed and recorded, with results checked.
Build those three layers once and you answer every framework below simultaneously. Build for one framework's wording and you'll rebuild for the next.
ISO 27001: the backup control, in plain English
ISO/IEC 27001:2022 addresses backups directly in Annex A control A.8.13 (Information backup): backup copies of information, software and systems are to be maintained and regularly tested in line with an agreed, topic-specific policy. Related controls reinforce it. A.5.30 (ICT readiness for business continuity) expects your recovery capability to meet continuity objectives, which is where your tested RTO/RPO numbers live.
The phrase that catches companies out is regularly tested. A certification audit will look past the backup schedule to the restore-test records; backups that have never been restored fail the control's intent regardless of how reliably they run.
SOC 2: availability criteria
SOC 2 has no single "backup control"; backups appear under the Availability trust services criteria, commonly A1.2 (environmental protections, software, data backup processes and recovery infrastructure are designed, developed, implemented, operated and maintained) and A1.3 (recovery plan procedures supporting system recovery are tested).
Two SOC 2 particulars matter for backups. First, a Type II report examines operation over a period (typically 6–12 months), so one heroic restore test the week before doesn't help; the evidence must show the control operating across the window. Second, the examiner samples: "show me the verification records for these specific weeks." Continuous, dated evidence is the only comfortable answer.
PDPA: the Security Principle
Malaysia's Personal Data Protection Act comes at backups from the data-protection side: the Security Principle requires practical steps to protect personal data from loss, misuse, modification and unauthorized access or disclosure. A backup you cannot restore is a foreseeable loss you failed to take practical steps against; equally, backup copies are personal data, so they need the same protection (encryption, access control) as the originals, and a retention story, since "keep everything forever" conflicts with the retention principle.
The 2024 amendments raised the stakes with mandatory breach notification and DPO requirements. The SME-focused detail is in our dedicated PDPA article.
One table: control → evidence → common gap
The three frameworks side by side
Framework Where backups live What it demands (plain English) Evidence that satisfies it Most common gap
ISO 27001:2022 Annex A: A.8.13 (backup); A.5.30 (ICT continuity readiness) Maintain backups per an agreed policy and test them regularly; recovery capability meets continuity objectives Topic-specific backup policy; backup register; dated restore-test records with verified outcomes; measured recovery times vs objectives Backups run for years, restore tested never ("regularly tested" unmet)
SOC 2 (Availability) A1.2 (backup & recovery operated); A1.3 (recovery tested) Backup processes and recovery infrastructure operate throughout the review period; recovery procedures are tested Continuous, dated verification records across the whole period; alert/response trail; recovery test documentation Evidence exists only for the weeks someone remembered; sampling finds the holes
PDPA (Malaysia) Security Principle; retention principle; 2024 breach-notification amendments Practical steps against loss of personal data; protect backup copies like originals; don't retain longer than needed; be able to assess and notify a breach Restorable, encrypted, access-controlled backups; defined retention; records showing what data a backup holds and its protection Backup copies treated as an IT artifact, not as personal data needing the same protection and retention discipline
The efficient way through
Read the table's evidence column again: it's the same short list three times: policy, continuous verification records, alert trails, dated restore tests. That evidence layer is exactly what Backup Governor generates as a by-product of verifying your backups, which means one working practice answers three frameworks and every customer questionnaire that borrows from them. We hold ISO 27001 and completed a Big-4 ITGC examination this year; what that audit actually asked is its own article.
Cite-check note: framework wording changes across versions. This page references ISO/IEC 27001:2022 Annex A, the SOC 2 trust services criteria as commonly applied, and Malaysia's PDPA including its 2024 amendments; verify current versions with your auditor or advisor before relying on specific clause numbers.
One evidence layer, three frameworks
Continuous verification, alert trails and dated restore tests, collected automatically, ready for whichever framework asks.
Request a demo