OSS® (#OSS) for ransomware resilienceData protection and storage
Off the network the attack runs on.
Ransomware finds backups because backups are connected. Hold your gold copies on dedicated hardware that is physically disconnected, so the recovery path does not share the fate of the estate it is meant to restore.
Offline Secure Storage®OSS® (#OSS) for ransomware resilience- Protects
- The records you could not recreate
- Hardware
- Dedicated, except LUV
- When closed
- No standing network path
- Access
- Authorised, out of band, time-bound
- Hosted in
- Firevault Bunkers: Europe live, US and Middle East next
A simple recovery question
If the estate were encrypted tonight, is there a copy the attacker could not reach?
Backups that are visible to the network are part of the attack surface. Physical disconnection changes that. The problem is not just ransomware. It is what ransomware can reach.
- A path that does not exist cannot be used
When the drive is disconnected there is no route, no share, no credential and no console for an intruder to abuse.
- Software controls still run on software
Immutability, retention locks and access policies are enforced inside the same connected platform an attacker is already inside.
- Selection matters more than volume
Only the copies you would genuinely rebuild from need to sit outside the estate. Everyday backups keep doing their everyday job.
- Recovery becomes independent
Your restore does not share the fate of the network being restored, so a full rebuild is possible without negotiating.
- The backup is encrypted too.
Scenario 1
- The snapshot is already infected.
Scenario 2
- Recovery takes weeks.
Scenario 3
- You pay to get moving.
Scenario 4
See the difference
The same stolen login. Two places to keep your records.
Choose a state to see what an intruder can reach.
Contracts, accounts and recovery copies share one connected estate. One stolen login, one supplier or one mistake reaches all of it.
The records you could not recreate sit on dedicated hardware with no standing network path. Access begins outside the normal network, on an authorised out-of-band request, for a time-bound session.
The principle
Select. Secure. Disconnect. Access when required.
Ransomware does not need to defeat your recovery copies if it can simply follow a network path to them. Changing the connection state of the data changes what an attacker can reach at all.
- Your important data
- Your network
- Security tools
- Still reachable
- Stolen, locked or changed
What recovery depends on
The copies you would actually rebuild from.
First-pass inventory
- Gold copies
- Build material
- Runbooks
- Credential material
- Regulated evidence
- Incident evidence
First-pass inventory
Protect the things recovery actually depends on.
It is the clean data plus the configurations, instructions and evidence needed to rebuild with confidence.
- Gold copies
- Build material
- Runbooks
- Credential material
- Regulated evidence
- Incident evidence
- Last known good data
- Critical databases
- Regulated records
What belongs offline
Online backup is not the same as offline protection.
Everyday and connected
- Daily snapshots
- Replication between sites
- Short-term retention
- Live failover copies
- Everyday restore points
- Clean gold copies
- Golden images and configurations
- Recovery runbooks
- Regulated retained records
Who can reach it
The recovery path should be deliberate.
Access to a gold copy should require a person, an authority and a window rather than a credential that already exists on the network. Disconnection is the control. Access is the exception.
- Verified owner
- Recovery lead
- Auditor or insurer
- Succession route
- Data is reachable during the access window you nominate rather than continuously.
Windowed connection
- Retrieval is tied to a verified individual rather than an infrastructure account.
Authority before access
- Access records support insurer, regulator and board reporting after an incident.
Evidence of restoration
The products
Offline Secure Storage®, then the product that fits the volume.
One physical principle at every size. What changes is capacity and how access opens.
- Physically offline between sessions.
Vault
- Ask from your registered phone and confirm it is you.
Open a session
- Work with your files for up to 120 minutes.
File Manager
- Opens on a day you choose each week, for 12 hours.
LUV
- From 20TB, growing in 20TB steps.
Storage
Why Firevault
Physics, not promises.
Every Offline Secure Storage® instance is built on the same four physical principles.
- Physical storage
Offline Secure Storage instances are held on dedicated physical hard drives, not in S3 cloud buckets, shared storage pools or multi-tenant infrastructure. Your selected data is assigned to real hardware, with dedicated RAID 1 drives providing resilience.
- Physical ownership
Each Offline Secure Storage instance is allocated to a specific customer, with dedicated physical capacity and clearly defined ownership. Your data is not pooled, commingled or held within a shared storage estate.
- Physical control
Access begins outside the normal network path. An authorised out-of-band command, such as SMS, controls the physical Layer 1 connection to your #OSS instance. When access is not required, that network path is physically disconnected.
- Physical security
Your #OSS hardware is housed in carefully selected, professionally managed data centres with layered physical security, resilient power and environmental controls. Access is tightly controlled using three-factor authentication, including biometric identification, supported by 24/7 monitoring, restricted access zones and a complete audit trail.
Guidance
Offline copies are the guidance, not a Firevault invention.
A recovery copy that can be reached from the compromised network is a recovery copy at risk.
- Offline backups in an online world
NCSC
- Data integrity: recovering from ransomware
NIST SP 1800-11
- #StopRansomware Guide
CISA
Your next step
Protect the records that matter most.
Start with the records you could not recreate. Keep everything else where it works best.