ISO 27001 Annex A 5.29 Information security during disruption
What it says
The organization shall plan how to maintain information security at an appropriate level during disruption.
Quoted as published. Everything else on this page is written by Control Stack.
What it means
In plain EnglishPlan how to maintain information security at an appropriate level during disruption, with your organisation deciding the level from its risks and context.
Your organisation must plan how to maintain information security at an appropriate level during disruption, such as an outage, loss of a site or a major incident. Your organisation decides what level is appropriate, based on its risks and context, and the level can differ from normal operations. The plan covers confidentiality and integrity as well as availability. Annex A 5.30 deals with ICT readiness, keeping technology services running; this control deals with keeping information protected while that happens.
Free. Save your status, tasks and notes.
Why it matters
Recovery pressure tempts people to share administrator accounts, switch off logging or put sensitive files on personal devices, and those shortcuts can outlast the disruption or give an attacker an opening. A plan decides which controls must hold and what replaces those that cannot.
How to implement
List likely disruptions and the critical processes they affect.
Start from your continuity plans or, if you have none, the processes you cannot run without. Consider an outage, loss of a site, a cyber attack and loss of a supplier. Note what each could do to confidentiality and integrity as well as availability.
Decide the appropriate security level for each disruption.
Go through key controls, such as access control, logging, encryption and backups. Mark each as must stay, can reduce for a time, or needs a substitute, based on your risks. Record who approved each decision.
Plan substitutes for controls that cannot keep running.
Examples are emergency accounts (protected, logged and reviewed afterwards) for when central sign-on is down, local logs when central logging fails, and locked storage for paper records during a manual workaround. Make sure each substitute works without the failed system.
Plan security for outages of services you buy.
Read what the provider says about security during its failover or outage. You usually cannot change this, so decide what you will do on your side, such as limiting what information goes in during the event or switching to a manual process.
Write the security steps into your continuity plans.
If you have none, write a short stand-alone plan. Put the steps where responders will see them during recovery. Include the return to normal: remove temporary access, review emergency account use and restore any reduced control. Walk through the plan with those who would use it.
Keep it running
Update the plan when continuity plans, critical systems or suppliers change, and after a real disruption. After any disruption, remove temporary access and workarounds, then review what was done under them.
Evidence and audit
- Check 1 of 4What an auditor asks for
Ask for
The plan for maintaining security during disruption, usually part of the continuity plans.
Look at
Whether it states the security level to keep during each disruption, and covers confidentiality and integrity, not only recovery of services.
Good evidence
The plan says which controls stay, which may be reduced and which have substitutes, and who decided the level was appropriate.
- Check 2 of 4What an auditor asks for
Ask for
A demonstration of one planned substitute, such as an emergency account with central sign-on unavailable.
Look at
Whether it works as the plan says, and whether its use leaves a record.
Good evidence
The substitute works with the normal control out of action, and its use is recorded for review.
- Check 3 of 4What an auditor asks for
Ask for
The list of critical bought services, matched to the plan.
Look at
Whether each appears, with what you would do on your side during its outage.
Good evidence
Every critical bought service appears in the plan with the security arrangements for its outage.
- Check 4 of 4What an auditor asks for
Ask for
Records of a real disruption or, if there has been none, a walk-through of the plan.
Look at
What happened to security controls during the event and whether temporary access and workarounds were removed afterwards or, in a walk-through, whether the plan gives those steps.
Good evidence
After a real disruption, the planned level was held or each departure was approved, and no temporary access remains. In a walk-through, the plan gives each step for holding the level and removing temporary access, and those named can carry them out.
Mappings
Closest match in ASD Essential Eight: E8-MF-ML2.12, Cyber security incident response plan enacted after incident identification, which partially overlaps with this control.
ASD Essential Eight: 1 mapping
- E8-MF-ML2.12Cyber security incident response plan enacted after incident identificationPartially overlaps
This control partially overlaps E8-MF-ML2.12.
Annex A 5.29 requires planning to maintain information security during disruptions. E8-MF-ML2.12 overlaps by requiring that, once a cyber security incident is identified, the incident response plan is enacted, which is an operational step that maintains security during a disruptive incident. E8-MF-ML2.12 is narrower because it triggers only after incident identification, while Annex A 5.29 also requires pre-planned arrangements for maintaining security across broader disruption types and timeframes.
ASD Information Security Manual: 5 mappings
This control partially overlaps ISM-0043.
Annex A 5.29 requires planning to maintain information security at an appropriate level during disruption. ISM-0043 overlaps by mandating system cyber security incident response plans, including contingency measures, which are a common type of disruption planning to preserve security during and after incidents. The overlap is partial because Annex A 5.29 also covers non-incident disruptions (e.g. outages, disasters) and broader continuity of security controls beyond incident response procedures.
This control partially overlaps ISM-0576.
Annex A 5.29 requires the organisation to plan for maintaining information security during disruptions. ISM-0576 relates by requiring an incident management policy and incident response plan, which supports maintaining security when disruptions are caused by cyber incidents. The primary control is broader because it covers disruption scenarios beyond incidents and expects planning for maintaining security levels across operations, not just incident handling governance and playbooks.
This control partially overlaps ISM-0734.
Annex A 5.29 requires the organisation to plan how to maintain information security at an appropriate level during disruptions. ISM-0734 relates by requiring the CISO to contribute to business continuity and disaster recovery planning so business-critical services remain supported during a disaster, which is a key mechanism for sustaining security controls when operations are disrupted. However, Annex A 5.29 is broader in that it is not limited to the CISO role or to DR/BCP artefacts, and it focuses on maintaining information security (not just service continuity).
This control depends on ISM-0570.
ISM-0570 requires that backup or alternative email gateways are maintained to the same standard as the primary email gateway to avoid security gaps when switching gateways during outages or maintenance. Annex A 5.29 requires organisations to plan how to maintain information security at an appropriate level during disruption, and maintaining hardened, up-to-date alternate gateways is a specific way to preserve email security controls during a disruption scenario. Annex A 5.29 is broader and planning-focused across all disruption types and services, while ISM-0570 is a targeted operational requirement that supports that planning by addressing a common disruption dependency (email gateway failover).
This control depends on ISM-2006.
Annex A 5.29 requires the organisation to plan for maintaining information security at an appropriate level during disruptions. ISM-2006 supports this by ensuring executive leadership plans for major cyber security incidents and participates in exercises, improving governance, decision making and readiness during disruptive events. ISM-2006 is focused on board/executive preparedness for cyber incidents, while Annex A 5.29 covers the full set of disruption scenarios and the operational arrangements needed to sustain security controls.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.
Get help with this control
ISO 27001 training
Mindset Cyber, a PECB Authorised Titanium Partner, sells official PECB ISO/IEC 27001 courses that map directly to the controls in this library.




