The Blueprint

Backup, resilience and continuity.

Keeping going when things go wrong and recovering afterwards: backups you know will restore, plans for getting IT and critical activities back within agreed limits, and rehearsing them.

RES 18 requirements

Foundation

RW-RES-01Important data backed up

What
Back up your important data, together with the systems and settings needed to use it, on a regular schedule that runs without anyone having to remember it, and keep the backups long enough to go back to before an attack that went unnoticed for some weeks.
Why
Regular backups mean that data lost to ransomware, a failed disk, an accidental deletion or a stolen laptop can be brought back, so a single mishap or attack doesn't cost you weeks of work, money or your customers' trust.
Protects
Availability

RW-RES-02Cloud data kept in a second place

What
Back up the email, files and other data you keep in cloud services to somewhere separate from the service itself.
Why
Cloud providers keep their services running but seldom promise to recover data that you, or an attacker using one of your accounts, deleted, so an independent copy means a mistake, a malicious insider or a locked account doesn't leave you with nothing.
Protects
Availability

RW-RES-03A backup copy attackers can't reach

What
Keep at least one recent copy of your backups offline, or in a form that can't be altered or deleted, out of reach of the accounts used for everyday administration.
Why
Ransomware gangs hunt for backups and destroy them before encrypting anything else, so a copy that a stolen admin account can't touch is often the difference between recovering in days and paying a ransom or losing everything.
Protects
Availability

RW-RES-04Restores tried out

What
Restore data from your backups regularly as a test, and record how long each restore took.
Why
A backup that fails on the day you need it is no backup at all, and trying a restore finds missing files, broken jobs and lost encryption keys while there's still time to fix them, as well as telling you how long a real recovery would take.
Protects
Availability

RW-RES-05A written plan for getting IT back

What
Write down how you would restore your critical systems and data after a serious incident, including what to bring back first, who does each step and how to reach them.
Why
In the confusion after a ransomware attack or a major failure, a plan written in calm conditions saves hours of guesswork, stops people restoring things in the wrong order and means recovery doesn't rely on one person's memory.
Protects
Availability

RW-RES-18Critical services and what they rely on

What
Identify the services your organisation and your customers depend on most, record which systems, information, suppliers and people each one relies on, and have senior leadership agree their order of importance.
Why
Backups, recovery plans and monitoring all depend on knowing what matters most. If nobody has decided which services are critical, and what they need to keep running, effort is spread evenly and the things that would hurt most may be left least protected.
Protects
Integrity · Availability

Read the guide: When the platform everyone uses stops

Established

RW-RES-06Recovery limits agreed with the business

What
Agree with the people who run each critical activity how long it can be stopped and how much recent data it can afford to lose, and revisit this whenever the business changes.
Why
Knowing what the business can really tolerate lets you spend on recovery where it matters most, and saves IT from discovering in a crisis that the system it meant to restore last was the one everyone needed first.
Protects
Availability

RW-RES-07Recovery that meets the agreed limits

What
Check that each critical system can be recovered within the agreed time and data-loss limits, and close any gap you find.
Why
Limits only help if your backups and recovery arrangements can actually meet them, so comparing each system against them shows where a backup runs too seldom or a restore takes too long before an incident proves it for you.
Protects
Availability

RW-RES-08Continuity plans for critical activities

What
Keep a continuity plan for each critical activity that sets out how it would carry on if its systems, its premises or its key people were unavailable.
Why
Disruption rarely gives warning, and a plan prepared beforehand means staff know how to keep serving customers by other means while systems are repaired, rather than everything stopping until IT is back.
Protects
Availability

Read the guide: When the platform everyone uses stops

RW-RES-09Workarounds that stay secure

What
Make sure the workarounds in your continuity plans keep information as well protected as your normal ways of working do.
Why
Attackers often strike during a crisis, and fallbacks such as personal email, paper records or access handed out in a hurry can expose more than the original incident did, so thinking through the security of each workaround stops a disruption turning into a breach.
Protects
Confidentiality · Availability

Read the guide: When the platform everyone uses stops

RW-RES-10No single point of failure

What
Provide a fallback for any connection, server or storage device whose failure would stop a critical service for longer than the business has agreed it can tolerate.
Why
Equipment, lines and hosted services fail without warning, and with a fallback ready a broken part causes a short pause instead of a day without email, telephones or the systems your customers rely on.
Protects
Availability

RW-RES-11Enough capacity, planned ahead

What
Monitor how much storage, processing power and network capacity your critical systems use, and add more before they run short.
Why
Systems that run out of room slow down, stop or quietly fail to back up, so spotting the trend early lets you act on your own timetable rather than in the middle of an outage.
Protects
Availability

RW-RES-12Changes checked before they're made

What
Assess the security effect of every significant change to your systems, approve and test it before making it, with a quicker route for urgent changes that are reviewed afterwards, and have a way to undo it if it goes wrong.
Why
Many outages and security gaps are caused by well-meant changes rather than attacks, so looking at the effect of a change beforehand, and being able to reverse it, keeps a routine update from bringing down a service or silently turning off a protection.
Protects
Integrity · Availability

RW-RES-13Cover for key people

What
Make sure every critical task has at least one other trained person who can carry it out when the usual person is away.
Why
If only one person knows how to run the payroll, restore a server or renew a certificate, their illness, holiday or resignation can halt the business or leave a security task undone, and a trained deputy removes that dependence.
Protects
Availability

RW-RES-14Continuity plans exercised

What
Exercise your continuity and recovery plans with the people who would carry them out, using realistic scenarios such as ransomware or the loss of a building, and act on what you learn.
Why
An exercise shows whether people understand their part, whether the plans still fit how the business works and where they fall apart, so weaknesses are fixed during a rehearsal rather than discovered in a real crisis.
Protects
Availability

Advanced

RW-RES-15Backups checked before a restore

What
Check that a backup is complete and free of malware or tampering before you restore from it after an attack.
Why
Attackers can sit unnoticed in a network for weeks, so restoring an unchecked backup can bring the same malware or hidden way in straight back, and you would face the attack all over again.
Protects
Integrity

RW-RES-16Whole systems rebuilt in rehearsal

What
Rehearse rebuilding at least one critical system from nothing to a known clean state, using only your backups and your recovery plan.
Why
Restoring a few files proves little about recovering from ransomware that has wiped whole servers, and a full rehearsal brings to light the missing installation files, licence keys and undocumented settings that would otherwise hold up a real recovery for days.
Protects
Availability

RW-RES-17A second place to run critical services

What
Arrange a second location, or a second region of a cloud service, from which your critical services could be run if the main one were lost.
Why
A fire, a flood or a regional cloud outage can make a whole location unusable, and having somewhere ready to run critical services keeps the business going while the main site is put right, rather than waiting weeks for it.
Protects
Availability