AIM SHIELD Emergency
Continuity plan · Free

If your system goes down tomorrow, can you keep working?

A one-page plan to keep going if a computer, email or a program goes down, your backup strategy and the record of a restore test: the evidence for measure c) of NIS2. Everything is written in your browser: nothing reaches us.

In five steps

  1. Choose what is critical. The processes you cannot work without (invoicing, getting paid, handling orders, payroll) and which systems and data each one needs.
  2. Set the times. For each one: how long it can be down (MTD), how soon it has to be back (RTO) and how much data you can lose (RPO). The backup timings come from here.
  3. Decide who is in charge and how people are alerted. Who decides in a crisis and their deputy, who is called and a channel for raising the alarm if email or the computer goes down.
  4. 3-2-1 backups. Three copies of what matters (the original and two copies), on two different media and one outside the company. Cloud copies, encrypted.
  5. Test that you can restore. A backup that has never been restored is a hope. Restore something for real, measure how long it takes and how old the data was, and keep the record.

Working from home is also continuity: see Remote access without open ports so as not to leave the door open to ransomware.

1. Your business and who decides

2. What is critical and its timings

MTD
Maximum tolerable downtime: how long a process can be stopped before the damage becomes serious.
RTO
Recovery time: how soon it has to work again, even under minimal conditions.
RPO
Recovery point: the most data you can lose (for example, the last 24 hours of work).
Process 1
Process 2 (if there is one)
Process 3 (if there is one)

3. Who to call and how to raise the alarm

4. Backups

Type of backup
3-2-1 rule and protection of the backups

5. The restore test

Result

None of this leaves your browser. If you close the page, it is lost: download or print the documents.

Continuity plan

Record of the restore test

Keep them as evidence for measure c) in your NIS2 file.

Frequently asked questions

Does this meet measure c) of NIS2?

Measure c) asks you to manage the continuity of activities: backups, disaster recovery and crisis management. This plan and the record of the test are evidence that you do it; what each country requires is set out in its national law, and whoever audits you will judge whether it is enough. Keep them in your NIS2 file.

How often should the restore be tested?

INCIBE says to set a regular schedule for restore tests, without saying what it should be, and to review the procedures at least once a year and whenever the inventory changes a lot. Our proposal: a test every six months, and always after changing system or backup provider.

What is the 3-2-1 rule?

Three copies of any important file (the original and two copies), on two different media so that the same failure doesn't affect both, and one of them outside the company, for example in the cloud.

What if my data is encrypted (ransomware)?

That is why a backup that is not always connected matters: if all of them are (including a cloud that syncs by itself), they can all be encrypted at once. INCIBE recommends isolating the computer from the network, never paying the ransom and keeping the encrypted disk; its Cybersecurity Helpline is 017. Check in the restore test that the backup can be used.

Is it stored anywhere?

No. Everything is written in your browser and nothing reaches us. Download or print the plan and the record before closing the page.