What is offline secure storage?

Offline secure storage (OSS) is a data protection method where data is physically disconnected from the internet when not in use. Unlike cloud storage, data stored offline has zero remote attack surface — it cannot be hacked, ransomed or accessed remotely because it is not connected to any network. Firevault provides this through hardware-encrypted vaults that are physically isolated.

How does Firevault protect against ransomware?

Firevault protects against ransomware by physically disconnecting your data from the internet. Ransomware can only encrypt data it can reach over a network. When your data is stored offline in a Firevault, ransomware attacks cannot reach it. Even if your entire network is compromised, your offline vault remains untouched and intact.

How much does Firevault cost?

Firevault Vault starts from £75 per month (inc VAT) for individuals. Business Storage starts from £360 per month (inc VAT). Enterprise Platform pricing is available on request. All plans include hardware encryption, identity verification, and physical disconnection by default.

Who is Firevault designed for?

Firevault is designed for individuals protecting passports, wills and crypto keys; professionals such as solicitors, accountants and consultants protecting client data; SMEs and businesses protecting crown jewel data; and regulated industries including healthcare, financial services and legal sectors requiring offline backup for compliance with GDPR, NIS2, DORA and FCA regulations.

Is Firevault GDPR compliant?

Yes. Firevault is designed to support GDPR compliance by keeping sensitive personal data physically isolated and offline. Physical disconnection ensures data is not exposed to network-based attacks, supports data minimisation principles, and provides an audit trail of access. Firevault is also designed to support NIS2, DORA, FCA and SRA compliance requirements.

What is a physical air gap?

A physical air gap is a security measure where a computer or storage device is completely isolated from the internet and all unsecured networks. Unlike a logical or software air gap, a physical air gap cannot be bridged remotely. Firevault uses a Layer 1 physical air gap — your data is stored on hardware that is physically disconnected from any network when not in active use.

Control Module

FV-Execute: Verified Recovery Operations

Recovery is only valuable if you can trust the data you are restoring. Execute automates recovery from air-gapped copies with cryptographic integrity verification, ensuring every restored system returns to a known-good state.

Back to Control

Control Module

Recovery without integrity verification is guesswork. Execute ensures that every restored asset is cryptographically verified against its known-good state before it enters production.

Verified

Cryptographic integrity check on every restored asset

Air-gapped

Recovery copies physically disconnected from production

Automated

Recovery orchestration with multi-party authorisation

Full

Recovery audit trail on tamper-proof storage

The Problem

Backups you cannot trust are not backups at all.

Compromised Recovery Assets

Network-connected backups are encrypted by ransomware, corrupted by insiders, or silently tampered with during extended dwell times. When you need them, they are unusable.

Unknown Integrity

Without cryptographic verification, you cannot confirm that restored data matches the original. Backdoors, tampered configurations, or corrupted records may survive the recovery process.

Manual Recovery Failures

Complex manual recovery procedures introduce human error under extreme pressure. Steps are missed, systems are restored in the wrong order, and the recovery takes days instead of hours.

The Scenario

Scenario: Verified Recovery After Ransomware

Following a ransomware incident that encrypted 340 systems across four sites, the recovery team activates Execute. The module retrieves air-gapped copies from the Vault, cryptographically verifies each system image against its pre-incident hash, and orchestrates restoration in the correct dependency order. Database servers are restored first, followed by application servers, then user-facing systems. Each restored system is verified before the next phase begins. By hour 8, all critical systems are operational with confirmed integrity. The alternative — manual recovery from network-connected backups — would have taken 5 days and provided no integrity assurance.

"We restored 340 systems in 8 hours with cryptographic verification of every single one. Without Execute, our last recovery test took 5 days and we still were not sure the data was clean."

Module Overview

Recovery you can trust, at the speed you need.

FV-Execute transforms disaster recovery from a manual, error-prone process into an automated, verified operation. Air-gapped copies are cryptographically verified, systems are restored in the correct order, and every step produces tamper-proof evidence.

Cryptographic verification of every restored asset
Air-gapped recovery copies beyond network reach
Automated dependency-ordered restoration
Isolated staging environment before production reconnection
Multi-party authorisation at each recovery phase
Complete audit trail for regulatory compliance

Execute — How It Works

Module 1 of 4

Execute orchestrates automated recovery from air-gapped copies. Each recovery asset is cryptographically verified against its known-good hash before restoration. Systems are restored in the correct dependency order with automated validation at each stage.

View all nine modules

Featured In

Key Capabilities

Cryptographic Integrity Verification

Every recovery asset is verified against its pre-incident cryptographic hash before restoration. Tampered or corrupted assets are flagged and excluded.

Dependency-Ordered Restoration

Systems are restored in the correct order based on dependency mapping. Databases before applications, infrastructure before services.

Automated Orchestration

Recovery proceeds automatically through defined stages with validation gates at each transition, reducing recovery time from days to hours.

Isolated Recovery Environment

Systems are restored in a physically isolated staging environment and verified before reconnection to production infrastructure.

Multi-Party Recovery Authorisation

Each recovery phase requires authorisation from designated parties, ensuring oversight and preventing unauthorised restoration of potentially compromised assets.

Complete Recovery Audit Trail

Every restoration action, integrity check result, and authorisation event is logged on tamper-proof storage for post-incident review and regulatory compliance.

Demo to Live

Adoption Guide

Step 1

Recovery Asset Inventory

Catalogue all systems and data that require recovery capability, map dependencies, and define recovery time objectives for each.

Step 2

Recovery Plan Design

Define the restoration order, integrity verification procedures, multi-party authorisation requirements, and staging environment specifications.

Step 3

Recovery Drill

Conduct a full recovery drill to an isolated staging environment, measuring restoration times and verifying integrity of all air-gapped copies.

Step 4

Production Readiness

Finalise recovery procedures with automated orchestration, SIEM integration for incident-triggered recovery, and quarterly drill scheduling.

Step 1

Recovery Asset Inventory

Catalogue all systems and data that require recovery capability, map dependencies, and define recovery time objectives for each.

Step 2

Recovery Plan Design

Define the restoration order, integrity verification procedures, multi-party authorisation requirements, and staging environment specifications.

Step 3

Recovery Drill

Conduct a full recovery drill to an isolated staging environment, measuring restoration times and verifying integrity of all air-gapped copies.

Step 4

Production Readiness

Finalise recovery procedures with automated orchestration, SIEM integration for incident-triggered recovery, and quarterly drill scheduling.

Organise a Demo

Questions

Frequently Asked

Ready to take the next step?

See how Control can govern your data paths with physical enforcement no software exploit can bypass.

View the nine modules

FV-Execute: Verified Recovery Operations

Backups you cannot trust are not backups at all.

Compromised Recovery Assets

Unknown Integrity

Manual Recovery Failures

Scenario: Verified Recovery After Ransomware

Recovery you can trust, at the speed you need.

Execute — How It Works

Key Capabilities

Cryptographic Integrity Verification

Dependency-Ordered Restoration

Automated Orchestration

Isolated Recovery Environment

Multi-Party Recovery Authorisation

Complete Recovery Audit Trail

Adoption Guide

Recovery Asset Inventory

Recovery Plan Design

Recovery Drill

Production Readiness

Recovery Asset Inventory

Recovery Plan Design

Recovery Drill

Production Readiness

Explore More

FV-Vault

FV-Fracture

Ransomware Containment

Frequently Asked

Ready to take the next step?

Your privacy matters