# ISO/IEC 27001:2022 A.5.30 — ICT readiness for business continuity - Source: https://support.icompaas.com/compliance/iso-27001-2022/a-5-30-ict-readiness-for-business-continuity - Section: [Compliance](https://support.icompaas.com/compliance) › [ISO/IEC 27001:2022 Annex A Controls](https://support.icompaas.com/compliance/iso-27001-2022) › Organizational controls - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **ISO/IEC 27001:2022**·Annex A `A.5.30`·high·Component: **Organizational controls** ## What this control requires > Information and Communication Technology (ICT) readiness shall be planned, implemented, maintained and tested based on business continuity objectives and ICT continuity requirements. > > — ISO/IEC 27001:2022, Annex A A.5.30 ### In plain English Information and Communication Technology (ICT) readiness shall be planned, implemented, maintained and tested based on business continuity objectives and ICT continuity requirements. In practice, this means you can prove you policy management-level controls on a defined cadence. ## Why it matters ISO 27001 certification depends on showing each Annex A control is either implemented or explicitly justified for exclusion in the Statement of Applicability (SoA). Certification bodies sample controls during surveillance audits, and a missing SoA entry — or implementation that doesn't match the SoA wording — is a finding. This control is rated **high**. Auditors expect a named owner, a remediation SLA, and a tooling artefact that evidences continuous operation. ## What an auditor looks for An ISO 27001 lead auditor looks for: (1) an SoA entry covering the control with justification, (2) a documented procedure or policy implementing it, (3) records that prove the procedure runs (logs, tickets, training records) and (4) management-review evidence that effectiveness is monitored. Within **Organizational controls**, the assessor will trace your implementation back to the catalogue reference (Annex A A.5.30) and look for objective evidence on the latest two assessment cycles. ## How to implement #### Business Continuity **BC/DR.** Define RTO/RPO per service, test backup restoration quarterly, and run a tabletop of full-region failover annually. **Backups.** Immutable backups (S3 Object Lock / Azure immutable storage / GCS bucket lock) plus an air-gapped copy for ransomware resilience. #### Policy Management **Docs.** Keep each policy in version-controlled Markdown alongside the code that implements it; ship a signed PDF snapshot at each annual review and link the SHA into the SoA. ### Operational checklist - **Policy.** Document the trigger, the owner and the cadence. - **Management.** Document the trigger, the owner and the cadence. - **Scope:** management. ## Evidence to collect - **Policy Document.** A signed and version-controlled policy / standard / procedure document. - **Infra Scan.** Continuous infrastructure-posture telemetry — AWS Config, Azure Policy compliance, GCP Organisation Policy, Wiz / Prisma findings. Signed policy or standard documents the safeguard. Focus: ICT readiness for business continuity. ## Common pitfalls - DR plans that have never been tested in earnest, or that depend on an MFA token only one person can produce. - Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced. ## How it maps to other frameworks Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit. - [**SOC 2 (2017 TSC) CC2.3** — External Communication on Internal Control Matters](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc2-3-external-communication-on-internal-control-matters) - [**NIST SP 800-53 Rev. 5 CP-7(2)** — Accessibility](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/cp-7-2-accessibility) - [**ISO/IEC 42001:2023 A.2.2** — Policies for the responsible development or use of AI systems](https://support.icompaas.com/compliance/iso-42001-2023/a-2-2-policies-for-the-responsible-development-or-use-of-ai-systems) - [**HIPAA (45 CFR Part 164) 164.308(a)(5)(i)** — Security Awareness and Training](https://support.icompaas.com/compliance/hipaa/164-308-a-5-i-security-awareness-and-training) - [**NIST SP 800-171 Rev. 3 3.13.15** — Session Authenticity](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-13-15-session-authenticity) ## Related controls in ISO/IEC 27001:2022 - [**Annex A A.5.5** — Contact with authorities](https://support.icompaas.com/compliance/iso-27001-2022/a-5-5-contact-with-authorities) - [**Annex A A.5.13** — Labelling of information](https://support.icompaas.com/compliance/iso-27001-2022/a-5-13-labelling-of-information) - [**Annex A A.5.37** — Documented operating procedures](https://support.icompaas.com/compliance/iso-27001-2022/a-5-37-documented-operating-procedures) - [**Annex A A.5.1** — Policies for information security](https://support.icompaas.com/compliance/iso-27001-2022/a-5-1-policies-for-information-security) - [**Annex A A.5.3** — Segregation of duties](https://support.icompaas.com/compliance/iso-27001-2022/a-5-3-segregation-of-duties) - [**Annex A A.5.4** — Management responsibilities](https://support.icompaas.com/compliance/iso-27001-2022/a-5-4-management-responsibilities) ## References - [ISO/IEC JTC 1/SC 27 — ISO/IEC 27001:2022](https://www.iso.org/standard/27001) - Catalogue identifier: `Annex A A.5.30` Topics: governance riskbusiness continuitypolicy management ## Related compliance guidance - [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): Start with the full ISO 27001 implementation guide — scope, roadmap, evidence and how the assessment runs. - [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Most companies that hold ISO 27001 also need a SOC 2 report for North American customers, and the two share most of their technical controls.