Skip to content
Black Fox Security

03 / Governance and risk

A recovery plan is a theory until you restore from it

We help you work out what must keep running, write the plans to keep it running, and test them before a real outage does it for you.

Overview

What business continuity and disaster recovery cover

Business continuity is about keeping critical activities going during a disruption: an outage, a ransomware incident, a lost site or a failed supplier. Disaster recovery is the technical part: restoring systems and data within the time the business can tolerate.

Both start with a business impact analysis. Which activities matter most, how long can each be down, and how much data can you afford to lose. Those answers become recovery time and recovery point objectives, and the plans are built to meet them. Then comes the part most plans skip: restoring from backup for real, and walking the people through a scenario at a table.

ISO 22301 is the certifiable standard for business continuity management, and certification comes from an accredited certification body. Continuity also appears in ISO/IEC 27001, NIS2 and DORA. Black Fox helps you build and test the plans; we do not issue the certificate, but we work with long-standing certification partners and coordinate the audit when you go for it.

Who it is for

Organisations whose clients, insurers or regulators ask for tested continuity plans, companies in scope of NIS2 or DORA, teams preparing for ISO 22301 or ISO/IEC 27001, and anyone whose backups have never been restored on purpose.

The work, from scoping to evidence.

What we do

  1. Business impact analysis

    The critical activities, their dependencies on people, systems and suppliers, and how long and how much loss each can tolerate.

  2. Business continuity plan

    Roles, decision points, communication and workarounds that keep critical activities going while systems are down.

  3. Disaster recovery plan

    The technical steps, order and responsibilities to restore systems and data within the agreed objectives.

  4. Backup and restore testing

    A review of backup design, including isolation from the systems it protects, and restores performed and timed against your objectives.

  5. Tabletop exercises

    A realistic scenario walked through with management and technical teams, to find the gaps in the plan before an incident does.

  6. Alignment with standards

    Plans structured so they can support ISO 22301, ISO/IEC 27001, NIS2 or DORA work where those apply.

How the engagement runs

  1. Kickoff

    We agree the scope, the scenarios that concern you and the people involved, and sign an NDA first if you need one.

  2. Proposal

    A business proposal with the method, the scope and the contract type that suits you.

  3. Impact analysis

    Interviews with business and IT owners, ending in agreed recovery objectives and a list of dependencies.

  4. Plans

    Continuity and recovery plans drafted with your teams and checked against the objectives.

  5. Testing

    Restore tests and a tabletop exercise, each with a written record of what worked and what did not.

  6. Results handover and closing

    The plans, the test reports and a list of improvements, followed by project close with your feedback.

What you receive

  • Business impact analysis with recovery objectives
  • Business continuity plan
  • Disaster recovery plan for the systems in scope
  • Backup and restore test report
  • Tabletop exercise report with lessons learned
  • Improvement plan with owners

Questions

What is the difference between a BCP and a DRP?

A business continuity plan keeps the business running during a disruption: people, decisions, communication and workarounds. A disaster recovery plan restores the technology. You need both, and they need to agree on the same recovery objectives.

Do you certify us to ISO 22301?

No. ISO 22301 certificates are issued by accredited certification bodies. We help you build the business continuity management system and the plans behind it, prepare you for the audit and coordinate it with one of our long-standing certification partners or a body of your choice.

Will you actually restore our systems?

Yes, if you want us to, in a controlled way and agreed in advance. A restore test can run in an isolated environment so production is not touched. A backup you have never restored is a hope, not a control.

Does this cover ransomware?

Ransomware is one of the scenarios we plan and exercise for, including backups the attacker cannot reach. Responding to an actual incident is covered by our forensics and incident response service.

Start with what must keep running

Tell us which activities you cannot do without. We will help you plan for their loss and test the plan.

Request a meeting

Send us a request to arrange a meeting, so you can tell us about your project and we can introduce ourselves and our experience properly.

§ A

Reading preferences

Adjust how this site looks and reads. Your choices apply at once and are kept on this device only.

Specimen

Good engineering is shown, not claimed. Read this line to judge your settings.

§ A.1Text

Text size
Line height
Letter and word spacing
TypefaceAtkinson Hyperlegible was designed for low vision; OpenDyslexic for some readers with dyslexia.
Align text leftRemoves justified text and hyphenation.

§ A.2Reading aids

Reading aidFollows your pointer to help you keep your place.
Highlight links
Highlight headings
Stronger focus outlineFor keyboard navigation.

§ A.3Colour and contrast

Contrast
Colour saturation
Hide decorative patternsRemoves the engraved line patterns behind content.

§ A.4Motion and pointer

Stop animationsAnimations are already reduced when your system asks for it.
Large pointer