ISO 27001 Annex A 5.30: ICT readiness for business continuity

What auditors look for

Auditors check that 5.30 is either justified as not applicable in your Statement of Applicability or implemented and working. Typical evidence includes:

• Business impact analysis
• Recovery time and point objectives
• ICT recovery test results

How to implement 5.30 in practice

1. Base recovery targets on business impact
2. Test restores, not just backups
3. Include key cloud and SaaS services
4. Name an owner for 5.30, decide how often it runs and file evidence each time, so the control is audit-ready all year.

Recording 5.30 in the Statement of Applicability

List 5.30 with whether it applies, the reason (usually the risks it treats or a legal or contractual requirement), its implementation status and where the evidence lives. If you exclude it, explain why none of your risks or obligations require it.

Free resources

• ISO 27001 and GDPR readiness assessment
• 10 steps to implement ISO 27001
• Remote ISO 27001 consultant

More organizational controls

• 5.26 Response to information security incidents
• 5.27 Learning from information security incidents
• 5.28 Collection of evidence
• 5.29 Information security during disruption
• 5.31 Legal, statutory, regulatory and contractual requirements
• 5.32 Intellectual property rights
• 5.33 Protection of records
• 5.34 Privacy and protection of PII