ISO 27001 Control A.5.30: ICT Readiness for Business Continuity

· 7 min read · Lyudmil Arkov

Most businesses can say how long they could survive without their key systems. Fewer can say how long it would take to bring those systems back, or whether anyone has ever checked. A.5.30 closes that gap. It is the 30th of 37 organizational controls in our walk through Annex A, and one of the newer controls introduced in the 2022 revision. Its job is to make sure the technology is ready to support the continuity the business actually needs.

The control is a bridge between two worlds. The business says “we cannot be offline for more than four hours” and IT says “the restore alone takes two days”. Better to find that out in a planning meeting than in the middle of an outage.

What the control requires

Annex A control 5.30 of ISO 27001:2022 states that ICT readiness shall be planned, implemented, maintained and tested based on business continuity objectives and ICT continuity requirements.

The key elements:

  • ICT readiness - the ability of your information and communication technology to be recovered or kept running when something goes wrong
  • Planned, implemented, maintained and tested - four verbs, and each one matters; a plan that was never tested does not count as readiness
  • Business continuity objectives - what the business needs to keep delivering and how quickly it must be restored
  • ICT continuity requirements - the technical targets derived from those objectives, such as recovery times and acceptable data loss

A.5.30 is a corrective control in the attributes of ISO/IEC 27002:2022, supporting availability. Annex A states the control; ISO 27002 gives guidance, including performing a business impact analysis, defining recovery time and recovery point objectives, and documenting response and recovery procedures. It works hand in hand with information security during disruption, which covers the security side of the same events.

How to implement ICT readiness

Start from what the business needs

Begin with a business impact analysis. List your key services and processes, and for each one ask how long the business can tolerate being without it and how much recent data it can afford to lose. From these answers come the two numbers that drive most technical decisions:

  • Recovery time objective (RTO) - how quickly a service must be back
  • Recovery point objective (RPO) - how much data, measured in time, you can afford to lose

A customer-facing application might need an RTO of a few hours and an RPO of minutes, while an internal reporting tool might tolerate days. Be honest and get business owners to agree the numbers, because they will drive cost. Tighter targets mean more investment in redundancy, replication and staff on call. The inventory you keep under inventory of information and other associated assets helps you find the systems, data and dependencies behind each service.

Design and implement the capability

Compare your targets with reality. If the RTO is four hours and a full rebuild takes two days, you have a gap and a decision to make: invest, change the target or accept the risk, with management’s explicit agreement. Typical measures include:

  • Backups that are frequent enough for the RPO and stored where an attack on production cannot reach them
  • Documented, step-by-step recovery procedures, including the order in which systems come back
  • Redundant infrastructure or a standby environment for the most critical services
  • Alternative connectivity, power and facilities, as discussed in supporting utilities
  • Access to the credentials, licenses and configuration needed to rebuild, held somewhere that survives the outage
  • Support arrangements with suppliers, including information security for use of cloud services and the Managing information security in the ICT supply chain that your recovery depends on

Document the recovery steps in plain language so that someone other than the usual administrator can follow them. People are unavailable in crises, and the person who knows how the system fits together may be the one on holiday.

Test it in realistic ways

Testing is where this control earns its keep. A restore test shows whether backups actually work, how long recovery takes and what is missing. Start small: restore a single database to a test environment and measure the time. Then try restoring a whole application. Later, rehearse a larger scenario, such as the loss of a site or a key provider, with the business involved. For each test, record the objectives, what you did, how long it took, what failed and what you changed afterwards.

Be wary of tests that only prove the happy path. Restore from the actual backups, not from a copy prepared specially. Include the dependencies: the application may restore perfectly while the identity service, DNS or license server it relies on stays down.

Maintain it as your systems change

ICT readiness decays quickly. New systems are added, services move to the cloud, data grows and staff change, so a plan written two years ago may describe a world that no longer exists. Tie readiness to your change process: when a significant system is introduced or changed, ask whether its recovery targets and procedures are defined. Review the business impact analysis annually, and after major changes. Report results to management so that the gap between requirement and capability is visible and decisions about investment are made knowingly. This is a natural fit for management review and for the evaluation work in monitoring, measurement, analysis and evaluation.

Keep a short record of the gaps you decide to live with. If a system’s recovery takes longer than its objective and the cost of closing the gap is not justified, write that down with the owner’s name and a review date. This is risk acceptance done properly, and it is far better than an unspoken assumption. It also helps when customers ask about your continuity arrangements: you can describe what you have tested, what you have not and what you plan to improve, which builds more trust than a confident claim you cannot back up.

A.5.29 connection. Information security during disruption ensures security survives while ICT is being recovered.

A.5.9 connection. The inventory of information and other associated assets identifies what has to be recovered and what depends on what.

A.5.23 connection. Information security for use of cloud services covers exit and responsibility questions that affect recovery.

A.5.21 connection. Managing information security in the ICT supply chain addresses the dependencies on providers.

A.7.11 connection. Supporting utilities such as power and cooling underpin ICT availability.

Clause 8.1 connection. Operational planning and control requires you to plan and control the processes needed to meet your requirements.

Forward reference. The technological controls on information backup (A.8.13) and redundancy of information processing facilities (A.8.14) provide the specific technical measures. We cover them in the technological part of the series.

What auditors check

Business impact analysis. Auditors look for documented continuity objectives agreed with the business, and recovery targets for critical services.

Plans and procedures. They ask to see recovery procedures and check that someone other than the author could follow them.

Test records. Expect requests for evidence of restore tests and continuity exercises, including results and follow-up actions.

Gap handling. Where tests show the capability falls short of the objectives, they check that management knew and made a decision.

Backup evidence. Logs of successful backups, restore tests and off-site or isolated copies show the technical basis.

Maintenance. They look for reviews after changes and evidence that new systems are considered.

Common mistakes to avoid

Backups without restore tests. A backup that has never been restored is a hope, not a control.

Targets that nobody agreed. If the RTO was invented by IT alone, the business will be surprised in a real outage.

Everything is critical. If every system has the tightest target, you have not prioritized, and you will not be able to afford the result.

Ignoring dependencies. Identity, DNS, certificates, licenses and network services quietly decide whether recovery works.

Plans in the wrong place. A recovery guide stored only on the system that is down will not help. Keep an accessible copy.

Testing once. Readiness fades. Repeat the tests and update the procedures as the environment changes.

How 27kay can help

We help organizations turn vague continuity hopes into measurable targets and tested procedures. As part of ISO 27001 implementation, we help you run a proportionate business impact analysis, identify the gaps between need and capability and prepare the evidence an auditor will expect. For the full picture, see our ISO 27001 knowledge hub.

If your most important system failed this morning, could you say with confidence how long recovery would take? Get in touch - we will help you measure it, and then shorten it where it matters.