Independent thinking. Informed defence.

CISO Times

Intelligence for the people behind the defence.

The CISO Decision Brief

Control A.5.30ICT readiness for business continuity

ICT readiness must be planned, implemented, maintained and tested based on business continuity objectives and ICT continuity requirements.

New in the 2022 edition, and it draws an important line: business continuity sets the objectives — what must keep running, how quickly it must return, how much data may be lost — and ICT readiness is the capability to meet them.

The control asks for that capability to be planned against the stated objectives, implemented, maintained and tested. Without the business objectives it is arbitrary; without testing it is a claim.

The common failure is a recovery objective asserted rather than demonstrated. An organisation states a four-hour recovery time, holds backups under A.8.13 and redundancy under A.8.14, and has never restored the service end to end to see how long it takes. The test is the control. And as A.5.29 notes, restoring the service is not the same as restoring the security of the service.

How to put this in place

The business can only survive an outage for so long, and backups that have never been restored prove little. This control ties recovery to what the business needs.

  1. Run a business impact analysis to find critical services.
  2. Set recovery time and recovery point objectives for each.
  3. Design backups and redundancy to meet them.
  4. Test recovery of critical systems at planned intervals, for example every 12 months.
  5. Record times achieved against targets and fix the shortfalls.

Evidence an auditor usually looks for: the business impact analysis with objectives, and recovery test reports showing times achieved against targets.

What is in the packs for this

From ISO 27001 Implementation & Certification Readiness. Each one helps with this requirement.