Choose what to restore

List the systems and data that keep the business operating. Include identity services, websites, databases, file shares, configuration and critical third-party dependencies. Ask each owner what must return first and how much data the business can afford to lose.

Select a small but representative restore test. Use an isolated environment so the restored system cannot affect production or connect to a hostile network.

Check protection and access

Confirm the backup schedule, retention period, encryption and access roles. Keep a recovery copy outside the normal administrator boundary where possible. An attacker who controls production credentials should not automatically control every backup copy.

Record who can approve a restore and where recovery credentials are stored. Test that the people who need access can retrieve them under the planned process.

Measure the result

Restore the selected data and services. Check that the data is usable, the application starts and required integrations work. Record the time, missing files, manual steps and any dependency that blocked recovery.

Update the plan and repeat the test after major system changes. CISA recommends protected backups and recovery planning for organisations. A security assessment can help identify weaknesses that could disrupt systems before a recovery plan is needed.