- Home
- Incident Response & Forensics
- Service continuity
Keep the business running
when the systems stop.
Continuity and disaster recovery planning built for the disruptions most likely to hit you: ransomware across the estate, a cloud outage, a critical supplier going dark. Business impact analysis, plans people can follow, and tests that show the plans work.
Plans written for the people who will use them.
Most continuity plans were written for floods and power cuts. The disruption you are more likely to face is ransomware encrypting the whole environment, a sustained cloud outage, a destructive wiper or a key vendor going offline. We plan for those, because we have responded to them.
We combine business continuity discipline with the technical reality of recovering from a modern attack. That means plans that are relevant to the business and actually achievable by IT: the right processes recovered first, from backups that are known to be clean, in an order that respects their dependencies.
Many organizations find that their real recovery capability does not match their stated objectives. We measure it, close the gap, and test it again.
- A business impact analysis with recovery objectives for each critical process
- A business continuity plan with alternate procedures and manual workarounds
- A disaster recovery plan matched to your RTO and RPO targets
- A measured comparison of actual recovery capability against those targets
- Backup and recovery architecture recommendations, including immutable and offline copies
- Exercise reports with findings fed back into the plans
Four steps, analysis to exercise.
Analyse impact
With business unit leaders we identify critical processes and dependencies, model the impact of disruption over time, and set recovery time, recovery point and minimum service objectives.
Plan continuity
Alternate operating procedures, manual workarounds, communication protocols and resource allocation, written for the people who will carry them out.
Design recovery
Backup strategy, recovery environments, identity-system recovery and application sequencing aligned to the targets from the analysis.
Test and improve
Tabletop walkthroughs, functional drills and full-scale recovery simulations, with every finding feeding back into the plan.
The disruptions that close businesses.
Ransomware
The whole estate encrypted, backups targeted, and identity systems that have to be rebuilt before anything else can come back.
Cloud and provider outage
A sustained loss of a platform or service you depend on, with failover and workarounds ready.
Supplier failure
A critical vendor or managed provider offline, and the alternatives to keep operating without them.
Destructive attack
Wipers and sabotage where data is gone, not encrypted, and recovery depends on clean, offline copies.
Who it is for
Organizations whose downtime is measured in hours, those with a continuity requirement from a regulator, insurer or customer, and anyone whose plan has not been tested since it was written.
- Crisis management, command and communications through the disruption
- Ransomware readiness, tested restores and the first six hours
- Cyber war gaming, Vigriðr, test the plan against real ransomware
- Supply chain and third-party risk, know which suppliers you cannot lose
What buyers ask.
We have backups. Isn't that a continuity plan?
Backups are one input. A continuity plan says which processes come back first, how the business operates while they are down, and whether the backups can actually be restored in the time you need. We test that last part.
Our plan was written for the auditor.
That is common. We rewrite it for the people who will execute it on a bad day, while keeping the evidence your auditor needs.
How often should we test?
Critical plans at least once a year, and after any significant change to your infrastructure or suppliers.
How does this fit with crisis management?
Continuity keeps operations going; crisis management runs the decisions and communications around them. The two plans should reference each other, and we build them to.
Find out if you can recover, before you have to.
Scope a continuity and recovery review with an engineer. No charge, no commitment.