Skip to content
Organisational controls
ISO 27001A.5.29

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 English

Plan 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.

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

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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

  1. 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.

  2. 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.

  3. 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.

  4. 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.

Essential Eight

ASD Essential Eight: 1 mapping

ASD ISM

ASD Information Security Manual: 5 mappings

  • ISM-0734CISO role in disaster recovery planningPartially overlaps

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.