
Mapping Offline Secure Storage to the NCSC Principles for Ransomware-Resistant Backups
A control-by-control mapping of Firevault Offline Secure Storage against the NCSC guidance on ransomware-resistant backups, written for UK government, CNI operators and regulated enterprises.
Mark FermorCTO, CMO & Founder, Firevault
Published 27 July 2026 · 2 min read
The National Cyber Security Centre (NCSC) publishes clear, non-negotiable guidance on how UK organisations should design backups that survive a ransomware attack. The guidance emphasises that at least one backup copy must be genuinely offline and out of reach of an adversary who has taken control of the production estate.
This whitepaper maps every NCSC principle for ransomware-resistant backups against Firevault Offline Secure Storage (OSS). It is written for accounting officers, senior information risk owners (SIROs), CISOs, and heads of resilience inside UK central and local government, the NHS, defence, critical national infrastructure, and regulated financial and legal services firms.
Principle 1 - Backups should be resilient to destructive action. OSS holds gold-copy records inside a Firevault bunker with no persistent network path from production. An attacker who compromises Active Directory, a hypervisor, or a cloud tenant cannot reach, encrypt, or delete the offline copy.
Principle 2 - At least one backup should be offline, off-site and offline-capable. Every OSS deployment satisfies this by design. Access is only possible during scheduled, identity-verified windows via the LUV (Locked User Vault) interface. Outside those windows the media is physically disconnected.
Principle 3 - Backups should have a separate identity, authentication and authorisation model. OSS never reuses production identity. Access is bound to hardware-backed passkeys, sanctioned devices, and a separate authorisation flow that cannot be pivoted to from a compromised corporate SSO.
Principle 4 - Backups should be regularly tested. OSS ships with structured restore rehearsals, evidence packs suitable for NIS Regulations, DORA and PRA SS1/21 audit, and CAF-aligned reporting for Objectives A to D.
Principle 5 - Backups should be monitored, but monitoring must not create an attack path. OSS telemetry is one-way. Health and capacity signals leave the bunker; nothing writeable enters it from the corporate network.
The paper also covers the 3-2-1-1-0 rule, the difference between immutable cloud backups and a physical air gap, procurement notes for G-Cloud and DPS frameworks, and a readiness checklist you can take to your next board or audit committee. Request access below to receive the full PDF.
Download this whitepaper
Free access with registration
GDPR compliantNo spam
Where Firevault fits
A recovery copy an attacker cannot reach
Offline Secure Storage® keeps a clean copy of your data on hardware that is physically disconnected, so backup and recovery do not depend on systems an intruder can touch.
- 1Hardware Your copy sits on dedicated encrypted hardware
- 2Disconnect Offline by default, connected only when you say so
- 3Recovery A known-clean copy to rebuild from, on your timetable
- 4Location Held in a secure Firevault Bunker
More research
Other whitepapers
playbook
Motorsport: 2026 Playbook
Protect competitive data and control race-weekend, supplier and factory network access.
playbookA Control Blueprint for Aerospace & Aviation
An engineering blueprint for communication pathways, operational states, remote access, rapid isolation and assured recovery across aerospace and aviation.




