Skip to content
LupoSec

Services 03 & 04 · Disaster recovery

Your backups are the first thing ransomware goes after. Can you still recover?

We help you plan, build and prove your recovery: from business impact analysis and RTO/RPO targets to immutable backups, failover automation and live drills.

The journey

From "we think we're covered" to "we've proven it"

  1. 01

    Analyse

    Business impact analysis: which systems matter, what downtime costs, and what depends on what.

  2. 02

    Target

    Realistic RTO and RPO targets per system, agreed with the business rather than guessed by IT.

  3. 03

    Plan

    A recovery strategy and step-by-step runbooks, including the ransomware scenario where your backups are the target.

  4. 04

    Build

    Immutable, isolated backups, cross-region replicas and failover automation, implemented with your team.

  5. 05

    Drill

    Tabletop exercises and live recovery drills that prove the plan works, with a written report and fixes.

03 · Planning & advisory

A plan built on how your business actually runs

Business impact analysis

We map critical processes to the systems, data and suppliers behind them, and put a cost on downtime.

RTO / RPO definition

Recovery targets per system that the business has signed off and the architecture can actually meet.

Backup & ransomware-resilience review

Are backups immutable, isolated, encrypted, monitored and restorable? We check, and we show you what an attacker would delete first.

DR plan & runbooks

Clear roles, communication trees and technical recovery steps, written for the people who will be on call.

04 · Implementation & testing

We build it with you, then we break it on purpose

Immutable & isolated backups

Object lock, separate accounts and credentials, and air-gap patterns, so one compromised admin cannot wipe your recovery.

Cross-region & cross-cloud recovery

Warm standby, pilot-light or active-active, sized to your RTO and your budget.

Failover automation

Infrastructure-as-code recovery environments and scripted failover that does not depend on the one person who remembers how.

Tabletop exercises

Facilitated scenarios such as ransomware, region outage or insider threat, run with leadership and technical teams.

Live DR drills

A controlled, real restore or failover. We measure actual RTO/RPO against target and fix the gaps.

Why security people should own your DR

Traditional DR assumes accidents: a disk fails, a region goes down. Modern disasters are often deliberate. Attackers wait in your network, find the backup console and delete it before they encrypt anything. Because we pen test too, we design recovery that holds up against someone who is actively trying to stop it.

FAQ

Common questions

We already have backups. Isn’t that disaster recovery?

Backups are one ingredient. DR is whether you can restore the right systems, in the right order, within a time the business can survive, including when an attacker has deleted or encrypted those backups. Most organisations only find the gaps during a real incident.

Do you only advise, or do you also build?

Both. Some clients want a plan and runbooks their own team implements. Others want us to build and test the recovery architecture alongside them. Most start with advisory and move to implementation.

How often should we run DR drills?

At least once a year for critical systems, and after any major architecture change. NIS2 and DORA both expect business continuity arrangements to be tested regularly.

Can a drill cause an outage?

Drills are planned with clear rollback steps and agreed windows, and usually start with a tabletop exercise and isolated restores before any production failover.

Find out if you could recover tomorrow.

Start with a DR readiness review: we will assess your current backups, plans and recovery targets and tell you honestly where the gaps are.