ISO 27001 Control A.5.29: Information Security During Disruption

· 8 min read · Lyudmil Arkov

When a disruption hits, whether it is a fire, a ransomware attack, a supplier outage or a pandemic that sends everyone home, the pressure to get back to work is intense. That is exactly when security tends to slip. Someone emails a database to a personal account so the team can keep working, a firewall rule is opened “temporarily”, and the emergency workaround quietly becomes the new normal. A.5.29 is the 29th of 37 organizational controls in our walk through Annex A, and it asks you to plan for that moment.

The point is not that security should win over continuity. It is that you decide in advance which safeguards must hold, which can be relaxed and for how long, so that recovery does not create a breach.

What the control requires

Annex A control 5.29 of ISO 27001:2022 states that the organization shall plan how to maintain information security at an appropriate level during disruption.

The key elements:

  • Plan - thinking and deciding before the disruption, not improvising during it
  • Maintain information security - confidentiality, integrity and availability all remain in scope, not only availability
  • At an appropriate level - not necessarily the normal level, but one justified by risk and agreed by management
  • During disruption - from the first moments of an interruption until normal operations resume

A.5.29 is a preventive and corrective control in the attributes of ISO/IEC 27002:2022. Annex A states the control; ISO 27002 gives guidance, including determining which information security requirements apply in a disruption, integrating them into business continuity management and keeping information security controls working in the alternative arrangements. Business continuity as a whole is a wider subject, which we touch on in our post about ISO 27001 and ISO 22301. This control is the information security slice of it.

How to implement security during disruption

Work out which security requirements survive a disruption

Start by asking, for each critical process: if we had to run this from a different place, with different systems or fewer people, which security measures could we never give up? Typical non-negotiables include protection of personal and client data, strong authentication for administrator access, logging of privileged activity and encryption of data leaving the building. Some measures may be relaxed temporarily with management approval, such as restricted access to a particular system, so long as a compensating safeguard exists and the relaxation has an end date.

Use your information security risk assessment as input. Disruption changes both likelihood and impact: staff are under stress, systems are unfamiliar, and attackers know that organizations in crisis make mistakes. Record the decisions in a short table that says what stays, what may change, who approves the change and how it is reversed. This table becomes a practical annex to your continuity plans.

Build security into the alternatives

Most continuity plans rely on alternatives: a secondary site, working from home, a backup system, manual procedures or a standby supplier. Each alternative needs its own security thinking.

  • Alternative premises. Does the backup location have the same physical protection, or equivalent compensating measures? Our posts on physical security perimeters and securing offices, rooms and facilities set out the questions to ask.
  • Remote working. Mass home working needs secure devices, protected connections and clear rules, as covered in remote working.
  • Alternative systems. Failover systems must receive the same patching, access control and monitoring as the primary ones. Backup environments are often the least maintained part of an estate.
  • Manual workarounds. Paper-based or ad hoc processes carry their own risks: who holds the paper, where does it go afterwards, who may see it?
  • Suppliers. If the disruption comes from a supplier, check what your contract and monitoring, review and change management of supplier services say about continuity and security duties. The same applies to information security for use of cloud services providers.

Connect it with incident management and continuity plans

Disruptions and incidents overlap. A cyber attack is both an information security incident and a business disruption, and the same people may be running both responses. Make sure your plans refer to each other and that roles do not conflict: one person cannot lead the technical recovery, speak to customers and decide on the security trade-offs all at once. Align with information security incident management planning and preparation and response to information security incidents, and make sure that the continuity plan does not tell people to skip steps that the incident process considers essential, such as preserving evidence.

Decide who has authority to approve a temporary security exception, how it is recorded, and when it expires. A simple rule helps: every exception is written down, has an owner and has a review date.

Test it and keep it current

A plan that has never been tested is a theory. Include security questions in your continuity exercises: can the team reach the backup, can they authenticate when the identity provider is down, is the emergency access account documented and secured, who can approve an exception at midnight? Review the plan after significant changes in systems, premises or suppliers, and at least once a year. Capture what you learn, in line with learning from information security incidents and your wider continual improvement process.

Keep the scenarios varied. Test the loss of a building, the loss of a key supplier, the loss of the identity provider and a ransomware event, because each stresses a different assumption. Write down the time it actually took to reach a workable state and compare it with what your plans promised. A gap between the two is valuable information for management, who can then decide whether to invest or to accept the longer recovery time. Involve the business owners as well as IT, since they know which processes cannot wait and which can survive a day or two on manual workarounds.

Also think about emergency access. Many organizations keep break-glass accounts that bypass normal controls so they can recover when something fundamental fails. These are powerful and dangerous. Keep them rare, protect the credentials in a way that works even during an outage, alert on any use and review every use afterwards.

A.5.24 connection. Information security incident management planning and preparation covers the incident side of disruption.

A.5.26 connection. Response to information security incidents applies when the disruption is caused by an attack.

A.5.21 connection. Managing information security in the ICT supply chain matters because disruptions often start with a dependency you did not control.

A.6.7 connection. Remote working is a common continuity strategy and needs its own safeguards.

Clause 6.1 connection. Actions to address risks and opportunities require you to plan actions to address risks, and disruption is one of the risks to consider.

Clause 8.1 connection. Operational planning and control expects the processes you need to be planned, implemented and controlled.

Forward reference. ICT readiness for business continuity (A.5.30) is the companion control that focuses on the technology, and later technological controls such as information backup and redundancy of information processing facilities supply the capability. We cover them next and in the technological section.

What auditors check

Documented requirements. Auditors look for a statement of which security requirements apply during disruption, linked to continuity plans.

Alternative arrangements. They examine whether secondary sites, systems and workarounds have been assessed for security.

Approval of exceptions. They check how temporary relaxations are authorized, recorded and ended.

Testing. Records of exercises that included security questions show the plan is more than paper.

Roles and authority. They ask who decides in a crisis and whether people know it.

Review. Evidence of periodic review and updates after changes shows the control is maintained.

Common mistakes to avoid

Treating continuity and security as separate worlds. A plan that restores service but exposes data has traded one problem for another.

Unprotected backup environments. The standby system that nobody patches is a favorite target, and you will be depending on it at the worst time.

Permanent temporary exceptions. A rule relaxed “for now” that nobody revisits quickly becomes a standing weakness.

No emergency access plan. Either nobody can get in during a crisis, or everyone shares the same powerful account. Both are bad.

Forgetting people. Staff under stress make mistakes. Short, clear instructions and practice help more than long documents.

Assuming the supplier has it covered. Check what is actually promised, and test it where you can.

How 27kay can help

We help organizations connect security with continuity so that one does not undermine the other. As part of ISO 27001 implementation, we help you identify the safeguards that must survive a crisis, review your alternatives and run exercises that test both. For the full picture, see our ISO 27001 knowledge hub.

If your main office were unavailable tomorrow, which security measures would you still be sure were working? Get in touch - we will help you work out the honest answer and close the gaps.