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
Keep information protected even during a disruption or crisis – security must not be switched off when things go wrong.
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
Disruption planning fails when continuity arrangements restore availability but quietly weaken security. The control expects information security to remain active during crisis workarounds, emergency access, and temporary processing modes. Good practice is to predefine which protections stay mandatory, who may approve exceptions, and how those exceptions are monitored and later removed.
Common auditor findings to check for
Potential gaps to test in your own environment, not a claim about observed audit frequency.
Emergency operating steps allowed temporary access or alternate processing, but MFA, logging, or encryption requirements were not explicitly retained or verified.
The crisis team had no named security role, so decisions about shortcuts, emergency accounts, and vendor access were made without accountability.
Business continuity plans restored services, but there was no record of post-disruption review to remove temporary exceptions or confirm normal controls were reinstated.
How you can implement it
Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.
Build the business continuity policy and procedure around control continuity, not only service recovery. List the security measures that remain non-negotiable during disruption: identity verification, logging, backup protection, secure remote access, and encryption for portable media and recovery copies. For any exception, require time limit, approval, and compensating monitoring.
Assign a security lead in the crisis management structure with authority to challenge risky recovery steps. That role should confirm emergency accounts, vendor support access, and recovery workarounds are logged, reviewed, and revoked when normal operations return. Include an escalation route when operational urgency conflicts with security requirements.
Document recovery runbooks that separate operational restoration from security restoration. For example, bring systems online only after checking backup integrity, privileged access reviews, endpoint hardening, and network segmentation. When a control must be relaxed, state the reason, scope, owner, start and end time, and the review point.
Exercise disruption scenarios that include cyber, facility, and supplier failure. Capture whether staff can maintain secure communication, protect paper records, manage offline data, and recover from alternate sites without exposing information. Track actions in the continuity register so lessons feed into updated runbooks and training.
What an auditor will ask to see
Business Continuity Procedure section listing mandatory security controls during disruption and named approvers for exceptions.
Crisis team roster showing the security lead, deputy, and contact route.
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.