Firevault, offline secure storage, physically disconnected from the internet
Pricing
Knowledge Vault open-book iconTechnical whitepaper

How Firevault Meets 3-2-1-1-0 and CNI Standards

A technical whitepaper on physical disconnection, air-gapped storage, and compliance with NIS2, CAF 4.0, IEC 62443, and NCSC guidance. By Mark Fermor, CTO, CMO & Founder, Firevault, April 2026.

  • NIS2
  • CAF 4.0
  • IEC 62443
  • NCSC
Corridor of offline storage racks inside a Firevault bunker
01Executive summary

The offline requirement that most vendors fail

The 3-2-1-1-0 backup strategy is the current gold standard for data resilience.

It requires three copies of data, on two different media types, with one copy offsite, one copy offline or air-gapped, and zero errors after verification. Most backup vendors claim to meet this standard through software-defined immutability, but their storage remains network-attached and reachable via management planes, APIs, and administrative interfaces.

Firevault is the only commercial storage platform that fulfils the offline requirement through physical disconnection at OSI Layer 1. When not in use, Firevault storage has no electrical connection to any network. No standby power. No wireless interface. No management plane. This whitepaper explains how Firevault meets 3-2-1-1-0 requirements and aligns with Critical National Infrastructure (CNI) standards including NIS2, CAF 4.0, IEC 62443, and NCSC guidance.

What 3-2-1-1-0 Means

ElementRequirementPurpose
3Three copies of dataRedundancy against single-point failure
2Two different media typesProtection against media-specific failure
1 (offsite)One copy stored offsiteGeographic separation from primary site
1 (offline)One copy offline or air-gappedIsolation from network-based attacks
0Zero errors after verificationConfirmed recoverability

The fourth element (1 offline) is where most organisations fail. Placing a backup in a separate cloud region or behind a firewall does not satisfy this requirement. The storage must be disconnected through any digital path.

The Problem with Software-Defined Air Gaps

Software-defined immutable storage solutions from vendors such as Veeam, Commvault, Cohesity, and Rubrik provide important protections against accidental deletion and basic ransomware. However, they share a fundamental architectural limitation: the storage remains network-attached.

Attack vectors that bypass software-defined immutability:

  • Management plane compromise: administrative interfaces can be exploited to disable immutability settings, delete snapshots, or modify retention policies.
  • Credential theft: compromised admin credentials can override WORM policies through vendor support channels or emergency break-glass procedures.
  • Zero-day exploits: vulnerabilities in the storage platform software can bypass immutability controls before patches are available.
  • Supply chain attacks: compromised updates to the storage platform can introduce backdoors that circumvent immutability.
  • Insider threat: a privileged administrator with management plane access can modify or destroy data regardless of immutability flags.

A physical air gap removes all of these vectors simultaneously. If there is no network connection, there is no management plane, no API, no login page, and no attack surface.

How Firevault Fulfils the Offline Requirement

Firevault implements disconnection at OSI Layer 1 (the physical layer). This means:

  • The storage hardware has no electrical connection to any network when in its default (disconnected) state.
  • No standby power is supplied to network interfaces between access sessions.
  • No wireless, Bluetooth, or radio frequency communication is available at any time.
  • Connection is established only after identity verification, and only for a time-limited window.
  • Upon session completion, the physical connection is severed and the hardware returns to its default disconnected state.

Every access session is logged with the identity of the accessor, the time and duration, and what data was accessed. This creates documented evidence of appropriate technical measures under GDPR Article 32, NIS2, and CAF 4.0.

02Comparison and RPO/RTO

Firevault against software-defined immutable storage

A layer-by-layer look at how physical disconnection compares with logical controls.

Firevault vs Immutable Backup Vendors

CapabilityFirevault OSSSoftware-Defined Immutable Storage
Physical disconnectionYes (Layer 1)No
Network-attached when idleNoYes
Management plane accessNoneAlways available
API access when idleNoneAvailable
Vulnerable to credential theftNoYes
Vulnerable to zero-day exploitsNo (no software surface)Yes
Meets 3-2-1-1-0 offline requirementYes (physical)Partial (logical only)
Identity-locked accessYes (biometric + MFA)Password/SSO
Audit trail of physical stateYesNo
Hardware encryptionAES-256-XTS on deviceVaries

CNI Compliance Alignment

NIS2 Directive

NIS2 requires essential and important entities to implement appropriate technical measures including risk analysis, incident handling, business continuity, and supply chain security. Physical disconnection provides the strongest form of data isolation, satisfying measures under Articles 21(2)(a) through (d). The identity-verified audit trail addresses Articles 21(2)(e) and (g) on access control and security monitoring.

CAF 4.0 (Cyber Assessment Framework)

The NCSC Cyber Assessment Framework version 4.0 assesses operators of essential services across four objectives: Managing Security Risk, Protecting Against Cyber Attack, Detecting Cyber Security Events, and Minimising the Impact of Cyber Security Incidents. Firevault directly supports Objective B (Protecting Against Cyber Attack) by removing data from network-accessible systems, and Objective D (Minimising Impact) by providing physically isolated backup copies for recovery.

IEC 62443

IEC 62443 defines security requirements for industrial automation and control systems. Firevault supports Zone and Conduit modelling (IEC 62443-3-2) by providing a physically isolated zone with no conduits when disconnected. This represents Security Level 4 (SL4) for data at rest, the highest level defined in the standard.

NCSC Guidance

The NCSC recommends organisations maintain offline backups as part of their ransomware resilience strategy. NCSC guidance explicitly states that backups should be kept offline where possible, disconnected from the network and from the systems they back up. Firevault is purpose-built to meet this recommendation.

RPO and RTO Characteristics

ProductRPORTOAccess Model
LUV (300 GB)Last scheduled uploadSame-day remote accessOne nominated access day per week
Vault (300 GB - 8 TB)Last session syncMinutes (remote access)On-demand, identity-verified
Storage (8 TB+)Last session syncMinutes to hoursOn-demand, identity-verified
Enterprise (10-300 TB+)ConfigurableConfigurable24/7 managed access

RPO and RTO depend on the product tier and access configuration. All products are designed to remain physically disconnected between sessions.

03Architecture and mapping

Architecture overview and compliance mapping

How the layers separate storage from the network, and where each standard is satisfied.

The Firevault architecture separates storage from all networks using a physical disconnection layer:

LayerComponentState When Disconnected
ApplicationFirevault Portal / APINo path to storage
NetworkIdentity Verification GatewayNo session active
Physical DisconnectLayer 1 Air Gap ControllerElectrically severed
StorageAES-256-XTS Encrypted DrivesNo power to interfaces
AuditTamper-Evident Access LogSealed, read-only

When a verified owner initiates an access session, the Layer 1 Air Gap Controller establishes a physical connection for the duration of the session. Upon completion, the connection is severed, returning all layers above storage to their default disconnected state.

Compliance Mapping

StandardClauseHow Firevault Meets It
GDPRArticle 32Physical disconnection as an appropriate technical measure; identity-verified access logs
NIS2Article 21(2)(a-d)Air-gapped data copies for recovery; no network exposure during incidents
CAF 4.0Objective BData removed from network-accessible systems; no management plane when disconnected
IEC 62443Zone/Conduit (3-2), SL4Physically isolated zone with zero conduits when disconnected
NCSCRansomware guidancePurpose-built offline storage with physical disconnection
ISO 27001Annex A.11Dedicated hardware in secure bunker; tamper-evident environments
Cyber Essentials PlusSecure configurationZero standing privileges; identity-locked access
DORAICT risk managementPhysically isolated backup for operational resilience
PCI DSSRequirement 9Identity-verified access to dedicated hardware
SOC 2Security criteriaDocumented access controls; audit trail evidence
04Conclusion

The difference between reachable and unreachable

For CNI operators, the distinction between logical and physical air gaps is not academic.

The 3-2-1-1-0 backup strategy requires one genuinely offline copy. Software-defined immutability does not satisfy this requirement because the storage remains network-attached and reachable through management planes, APIs, and administrative interfaces.

Firevault is the only commercial storage platform that meets the offline requirement through physical disconnection at OSI Layer 1. When not in use, there is no network path, no management plane, no API, and no attack surface. This provides the strongest form of data isolation available and directly supports compliance with GDPR, NIS2, CAF 4.0, IEC 62443, NCSC guidance, and other CNI frameworks.

For organisations operating critical national infrastructure or handling sensitive data, the distinction between logical and physical air gaps is not academic. It is the difference between data that can be reached and data that cannot.

Need an evidence pack for your underwriter or auditor?

Mark Fermor and the Firevault team can issue a tailored compliance mapping for your environment, with bunker access logs and a sample restore plan.

    Get started