Firevault, offline secure storage, physically disconnected from the internet
Pricing

Control module · Vault layer

FV-Archive. Preserve what the business must be able to recover.

Archive preserves critical files and records on physically separate storage, so they can be recovered, retained, attested to and relied on. Recovery, retention, compliance, continuity and evidential integrity are treated as a single discipline.

As featured in

  • TechRadar Pro logo
  • Yahoo Finance logo
  • Channel Insider logo
  • Security Buyer logo
  • SecurityBrief logo

The problem

A record you cannot recover is a record you do not have.

A record you cannot recover is a record you do not have. A record anyone can edit is a record nobody will trust.

  1. Archived records sit apart from the live operating environment, so a bad day there does not reach them.

  2. Integrity is established when records are written and confirmed when they are retrieved.

  3. Retention periods are set by policy and enforced by the system rather than maintained by hand.

Problem 2

Backups that cannot be relied on.

Unverified backups, or backups that depend on the same infrastructure to read them, may fail when they are needed.

Answered byVerifiable integrity

Problem 3

Retention as an afterthought.

Retention bolted on afterwards leads to inconsistent periods, incomplete evidence and audits that become projects.

Answered byPolicy-driven retention

The scenario

Scenario:
Recovering what matters after a bad day.

Archive is the difference between recovery as a plan and recovery as a hope. Step through it, or play it through.

Step 1 of 4

Incident

An incident affects the live environment.

Illustration.

Physically separate
Storage held apart from the live operating environment
Verified
Cryptographic integrity confirmed on retrieval
Retained
Held for the period the policy requires, no less
Recoverable
Designed to be brought back, not just stored

Placement

Where Archive holds the disconnected copy.

Archive places critical data in a copy that is not on the live network. The copy is reachable only through an authorised Transfer event into a time-bound Relay window. Grounded in NIST SP 800-209, ISO 27001 A.8.13 Information Backup and NCSC offline backup guidance.

Relies on

  • Storage that is not reachable on the live network at rest
  • Tamper-evident write path
  • Tested restore, not just tested backup

Pairs with

FV-Archive works alongside Transfer, Validate, Lock and Firebreak. Firebreak® hardware is manufactured by Firevault.

ISO 27001 A.8.13

Operational data archive

Periodic copies of operational data are written into the offline vault. The vault is not on the live network.

NIST CSF PR.IP-1

Configuration and golden image archive

Authoritative configurations and golden images are stored offline, so the source of truth survives an incident.

Physically disconnected Offline Secure Storage: server, three drives and a padlock

ISO 27001 A.8.15

Audit and evidence archive

Audit trails and attestations are sealed into the offline vault for the retention period.

ISO 27001 A.5.34

Long-term legal hold

Material under legal hold is stored in a copy protected from in-place edit or deletion.

Capabilities

What you get with every deployment.

Six things FV-Archive gives a security team, from the first decision to the audit afterwards.

FV-Archive

Physically separate storage

Archived records sit apart from the live operating environment, so a bad day there does not reach them.

FV-Archive

Verifiable integrity

Integrity is established when records are written and confirmed when they are retrieved.

FV-Archive

Policy-driven retention

Retention periods are set by policy and enforced by the system rather than maintained by hand.

FV-Archive

Recovery as an operation

Bringing records back is a defined operation with named owners, not an improvised salvage.

FV-Archive

Authorised access

Retrieval, restoration and release require the right authority and the right validation.

FV-Archive

Continuity and evidence as one

The same preserved store supports operational continuity, regulatory evidence and forensic reconstruction.

Adoption guide

From first workflow to routine operation.

Four steps, piloted on one workflow before it extends across the estate.

  1. 1

    Identify the records that matter

    Catalogue the files, datasets and records on which recovery, retention, compliance and evidence depend.

  2. 2

    Set the policy

    Agree retention periods, integrity expectations, retrieval authorities and approved destinations.

  3. 3

    Pilot the preservation

    Move one critical class of records into Archive end-to-end, including a rehearsed recovery.

  4. 4

    Operate and review

    Extend Archive across the remaining critical records and rehearse recovery on a regular cadence.

Playbooks

Which playbook covers this module.

Each playbook shows where this module sits in a real deployment, who authorises it and how a pilot scales into rollout.

Close the File. Protect the Record.

The closed-file chapters cover retained legal records, retention periods and evidential integrity on separate media.

Read the playbook

A Control Blueprint for Aerospace and Aviation

Addresses type records, configuration baselines and continuing airworthiness data that must outlive the live system.

Read the playbook

The Leaders’ Playbook

Frames records and continuity as a board-level custody question rather than a storage cost.

Read the playbook

All playbooks

Questions

Frequently asked about Archive

It treats recovery, retention, compliance, continuity and evidence as one discipline. Archived records sit on physically separate storage, integrity is confirmed on retrieval, and recovery is a defined, rehearsed operation rather than a backup you hope will restore.

Records are written through a tamper-evident path, held in a copy that is not reachable on the live network at rest, and their integrity is confirmed when they are retrieved.

It can help support them. Retention periods are set by policy and enforced by the system, and the same preserved store supports regulatory evidence and forensic reconstruction.

As a defined operation with named owners. The copy is reached only through an authorised Transfer event into a time-bound Relay window, and recovery is rehearsed on a regular cadence.

All questions

Decide what stays connected.

We will walk your architecture, show where FV-Archive sits on each path, and the evidence it leaves behind.