Colour theme
Book a consultation

Preparing for both prevention and recovery

Plan security controls and incident recovery together, with owners, tested backups and response decisions in place before an incident.

An illustration of a glowing shield with a keyhole, drawn in network lines on a dark blue background.

Security planning needs both everyday protection and a way to respond when something goes wrong. Recovery work depends on preparation done while systems are still operating.

The terms “left of boom” and “right of boom” describe prevention and post-incident response. They’re loose planning shorthand. Backups, response contacts and recovery tests belong in the work before an incident.

Fund everyday protection

List the controls your essential services need: supported software, managed access, strong authentication, device protection and secure configuration.

Assign an owner to each operating task. Check that updates go out on schedule and that a departing employee’s access is removed on time, even when the person who normally does it is away.

NIST CSF 2.0 includes Govern, Identify, Protect, Detect, Respond and Recover. Use those functions to find missing responsibilities across the whole plan.

Prepare detection and reporting

Determine which events your monitoring covers and who responds. Check the information the responder needs to identify the affected service.

Give staff a simple reporting route. Practise a harmless example and confirm someone receives it.

Judge training by what you can check: whether staff report a suspicious message, and whether someone acts on the report.

Build recovery before it’s needed

Identify essential records, applications and dependencies. Agree on recovery priorities with the business owners.

Keep backups protected from the same account and system failures they’re meant to address. Test a representative restore and record what wasn’t covered.

The backup-and-continuity guide helps turn those test results into a working plan.

Define incident decisions

Name the coordinator and the people who can approve containment, recovery expenditure and communications. Keep provider and adviser contacts available outside the affected system.

Use a tabletop exercise to practise uncertain information, an absent decision-maker and a service that can’t immediately be restored.

Include privacy and contract obligations in the plan. Restoring a file doesn’t tell you whether information was stolen. Under PIPEDA, a breach of personal information that creates a real risk of significant harm must be reported to the Office of the Privacy Commissioner and the people affected.

Return systems with evidence

During recovery, have the responsible technical people verify the restoration and containment work before the business accepts the service.

Record remaining uncertainty, temporary access and follow-up corrections. Don’t reconnect a restored system solely because it starts successfully.

Afterward, review the timeline and funded controls. Give each lesson an owner and an acceptance check. Keep prevention and recovery work together in the next budget review.


Featured Image Credit