Connected backup storageIP controlled
- Reachable all day, defended by credentials and software controls
- Exposed to the same stolen administrator account as production
- Can be encrypted or deleted along with everything else
StorageScalable offline secure storage™
Your backups are only as safe as the route to them.
Backups and archives usually sit on the same network as the systems they protect. If an attacker reaches production, they can often reach the copy you would recover from. Storage keeps that copy physically offline.
20TB to 300TB, in fixed 20TB blocks. Priced in a written proposal.
One administrator accountTuesday, 02:14
- Production serversLive systemsReachable
- Backup serverManaged by the same teamReachable
- Snapshots and replicasSame credentialsReachable
- Cloud backupSynced from siteReachable
- StoragePhysically disconnectedOffline
The recovery copy is a target too. Storage was not on the path.
What happens when
Attackers go for the backups first. Then they encrypt everything else.
A ransomware attack is planned so that you cannot recover without paying. That means reaching the copies you would restore from.
- An admin account is taken.
The attacker signs in as someone who manages both the servers and the backups.
- The backups go first.
Snapshots are deleted and backup jobs are switched off, so there is nothing to restore.
- Then the encryption.
Production stops. The team turns to the backups and finds they went first.
The question is not whether you have backups. It is whether they can be reached.
See recent breaches- Sound familiar?Backups on the same network as production
- One admin account that manages both
- Archives nobody has opened in years
What Storage is
The offline copy of what your organisation could not rebuild.
Think of it as a Vault for the whole organisation: dedicated physical storage that is disconnected by default and connected only when a job needs it.
Storage is dedicated, physically disconnected storage for your backups and archives, connected only for an authorised window.
- Offline by default
Outside its windows Storage is physically disconnected, so there is nothing to reach.
- Connected by decision
A schedule, an approved workflow or an authorised request opens a window. When the job ends, the path is removed.
- Sized to your estate
From 20TB to 300TB, added in fixed 20TB blocks as your data grows.
StorageNon-IP controlled
- Physically disconnected outside authorised windows
- Connected by an out-of-band decision, not a rule on the data path
- Holds the offline copy you restore from, alongside your existing backups
What it changes
Restore from a copy that was not on the network.
The attack still happened. The difference is that the copy you recover from was never part of it.
Recovery, Tuesday07:40
- Production serversEncrypted
- Backup serverWiped
- StorageClean copy
- RestoreUnder way
Window loggedCopy verifiedPath removed
Recover on your terms.
- The copy you restore from was physically disconnected when the attack happened
- Your existing backups keep running exactly as they do now
- Every window, write and retrieval is logged, so you can show auditors and insurers what happened
- It can help support GDPR, NIS2, ISO 27001 and NIST CSF
Could that be you?
Different organisations. The same 7am phone call.
A logistics group, an accountancy practice and a manufacturer. Each one had backups. Each one needed a copy that could not be reached.
Switch between the two endings.
ExposedMonday, 07:00DavidCEO, regional logistics group
The moment
The live database has gone.
An attacker has taken data and deleted it. Connected recovery systems are part of the incident.
There is nothing clean to restore.
Every connected copy went with the live system.
A clean copy to recover from.
The recovery copy was not on that path. The business still has a copy to work from.
How Storage is pricedExposedFriday, 17:45
An accountancy practicePractice manager, 60 people
The moment
The file server is encrypted at month end.
Ten years of client archives and working papers sit on the server, and on the backup appliance next to it.
The archive goes with the server.
The backup appliance was on the same network, so it was encrypted too.
A clean archive to restore from.
The offline copy was not on the server’s network, so the practice restores from it.
Request a storage designExposedMonday, 06:10
A manufacturerHead of IT, design and production
The moment
The design archive will not open.
Twenty years of CAD files, test data and certificates live on storage the whole engineering network can reach.
Years of design work are locked.
Re-certifying products means rebuilding evidence that took years to gather.
The gold copy was offline.
The archive is restored from Storage, held in a Firevault Bunker.
Where Storage livesDavid and these situations are illustrative. Our customer story is real.
Who Storage is for
Disclosure bundles, client archives and completed matters.
Retention sets you must keep, and prove you kept.
Design archives and the copies operations recover from.
Full backup estates and large working archives.
Holding one person’s records? Vault is 2TB to 8TB Holding more than 300TB? See Enterprise
Available today
Designed with you. Priced in a written proposal.
Our solutions team designs Storage around your data, access and deployment. Start with a size: it is a working input, not a quote.
Offline by default
5 blocks of 20TB. A working design input, not a quote. Final usable capacity is confirmed in engineering design.
Request a storage design
Want to work it out yourself? Use the OSS Concierge
How it is priced
OSAPOffline Secure Access Profile
- One named person, with their own identity-locked route into the offline capacity
- More people means more profiles, never a shared login
OSSCOffline Secure Storage Capacity
- The physically disconnected capacity itself, on dedicated, mirrored hardware
- Added in fixed 20TB blocks as your data grows
Where it lives: our Bunker, your site, or both
Firevault handles the facility, power and disconnection, in a Tier 3 data centre with controlled entry, physically separated from your network.
The same hardware and the same physical disconnection, inside your building and under your custody.
A working set on your site, with the gold copy held in a Firevault Bunker.
From a customer
“I had full autonomy over the way the Vault was managed. They facilitated the requests I had and adapted to what our business needed.”
- Cyber Essentials PlusConfirm current certificate status, scope and validity with Firevault.
- Firevault BunkersProfessionally managed Firevault Bunkers: Europe live, US and Middle East next, with three independent entry checks and 24/7 monitoring.
- Framework supportStorage can help support GDPR, NIS2, ISO 27001 and NIST CSF. NCSC CAF mapping on request.
- Commissioning and supportSetup, commissioning and ongoing support with every deployment.
How it works
Written in a window. Disconnected when the job ends.
Choose how your systems write to Storage. Methods can be combined, and each one connects only for as long as the job needs.
Write method
Scheduled sync
Data is copied during set windows. The connection opens for the window, the job runs, and the physical path is removed when it ends.
Initial ingestOften much larger than the ongoing change, so it is planned on its own.
Change rateHow much new or changed data arrives in each cycle.
FrequencyHourly, daily, weekly or triggered by an event.
ConcurrencyHow many sources write at the same time.
Illustration. The write pattern is designed with you, from these four inputs.
Four decisions behind every window
A schedule, an approved workflow through the API, or an authorised request.
Long enough for the job, and no longer.
The signal that the write or retrieval has finished.
The physical path is removed and Storage returns to its offline state.
Designed with you in four steps
-
Step 1Discovery
What you hold, what must be offline, and who needs access to it.
-
Step 2Sizing and retention
Volume, growth and retention, with expansion planned in fixed 20TB blocks.
-
Step 3Access and integration
How data is written, the window pattern, and the named access profiles.
-
Step 4Deployment and proposal
Where it lives, commissioning and pricing, set out in a written proposal.
Works with what you already run
Standard SFTP clients, and a scheduling API for windows, audit events and emergency offline.
Storage becomes the offline gold copy behind the backups you already run.
Every connection, exportable for your SIEM, auditors and insurers.
Named people get defined rights over defined data sets, never a shared login.
For your technical teamThe full specification
- Capacity
- 20TB to 300TB, in fixed 20TB blocks
- Default state
- Physically disconnected at the hardware level (Layer 1) outside authorised windows
- Control
- Windows opened by an out-of-band decision, not a rule on the data path
- Write methods
- Scheduled sync, SFTP, REST API, backup workflows, or a mixed design
- Windows
- Scheduled, on demand or event-triggered, each closed when the job completes
- Deployment
- Firevault Bunker, your premises, or hybrid
- Access
- Named people, each with an Offline Secure Access Profile (OSAP) and defined rights over defined data sets
- Audit
- Every connection logged, exportable for your SIEM, auditors and insurers
- Pricing
- OSAP and OSSC, quoted in a written proposal
- Frameworks
- Can help support GDPR, NIS2, ISO 27001 and NIST CSF. NCSC CAF mapping on request
- Bunkers
- Professionally managed Firevault Bunkers: Europe live, US and Middle East next, three independent entry checks including biometrics, 24/7 monitoring
- Beyond 300TB
- Enterprise
- Sessions
- Up to 120 minutes within the agreed access policy. Larger transfers are planned across authorised sessions.
Questions
Before you design your Storage.
Want your IT team in the conversation from the start? Book a demo and we will take them through the design.
Can we buy Storage online?
No. Storage is designed with our solutions team around your data, access and deployment, and priced in a written proposal. Vault and LUV can be bought online.
Will it change how our team works?
No. Your live systems and backups stay as they are. Storage connects only for authorised windows, and named people use their own access profiles.
How does data get into Storage?
By scheduled sync, SFTP, the REST API or your existing backup workflows, alone or combined. Each method connects only for the window the job needs.
Will it work with our backup software?
Storage is designed to sit behind your primary and backup tiers as the offline gold copy. We map the integration with your IT team during design.
Where is it held?
In a Firevault Bunker, on your premises or as a hybrid. The physical protection is the same in each.
Who can access it?
Named people, each with their own identity-locked access profile and defined rights over defined data sets.
What happens beyond 300TB?
Capacity continues in 20TB blocks. For estates of 300TB and above, Enterprise adds installation in your own facilities, multi-site architecture and a named account team.
Your next step
Size your offline copy.
Tell us how much you protect, how it changes and where it should live. We will design Storage around it.