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

Control module · Vault layer

FV-Unlink. Remove the relationships that expose the asset.

Unlink removes persistent connections, live dependencies and inherited trust relationships that quietly keep sensitive assets reachable. Where the relationship is not needed, it should not exist.

As featured in

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

The problem

Most exposure is paid for by relationships nobody chose to keep.

An asset is as exposed as its weakest relationship. Remove the relationship and you remove the exposure with it.

  1. Persistent connections that no longer serve a purpose are removed rather than catalogued.

  2. Live dependencies are replaced with mediated patterns, so the sensitive asset does not inherit the posture of its dependants.

  3. Inherited trust relationships are reviewed and removed where the inheritance is no longer warranted.

Problem 1

Persistent connections.

Always-on connections between systems remain long after the reason for them has passed, available to anyone who later finds them.

Answered byConnection removal

Problem 2

Live dependencies.

Direct, live dependencies between sensitive systems and convenience services drag the security posture of one onto the other.

Answered byDependency decoupling

Problem 3

Inherited trust.

Trust that exists because two systems share a domain, a directory or a network neighbourhood is trust nobody chose to grant.

Answered byTrust pruning

The scenario

Scenario:
Cutting a quiet path that no longer earns its keep.

Unlink is the audit of relationships you forgot you had. Step through it, or play it through.

Step 1 of 4

Review

A review of a sensitive records system shows a long-standing integration with a reporting service that has not been used in over a year.

Illustration.

Severed
Persistent connections removed where they are not required
Decoupled
Live dependencies replaced with mediated patterns
No inheritance
Trust does not carry over from one context to another
Reviewable
Every removal is recorded with its reason

Placement

Where Unlink revokes the trust.

Unlink is the deliberate revocation of a trust relationship. It removes the inherited reach a credential, certificate or federation gave away in the first place. Grounded in NIST CSF PR.AC-6 and PR.AC-7, ISO 27001 A.5.16 Identity Management and IEC 62443-3-3 SR 1.3.

Relies on

  • An accurate inventory of standing trusts in the first place
  • An authoritative revocation path that downstream systems honour
  • Evidence that the revocation actually took effect

Pairs with

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

ISO 27001 A.5.16

Departing-staff trust revocation

Identity and certificate trust is revoked at the boundary, not just disabled in a directory.

NIST CSF PR.AC-6

Compromised vendor relationship

Severs the standing trust to a compromised vendor’s infrastructure. Restoring it is a deliberate act.

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

NIST CSF PR.IP-6

Decommissioned system trust

Removes the inherited reach a retired system had into adjacent zones, even after it is unplugged.

IEC 62443 SR 1.3

Federation and SSO trust review

Periodic Unlink reviews surface unused federations before they become an attack surface.

Capabilities

What you get with every deployment.

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

FV-Unlink

Connection removal

Persistent connections that no longer serve a purpose are removed rather than catalogued.

FV-Unlink

Dependency decoupling

Live dependencies are replaced with mediated patterns, so the sensitive asset does not inherit the posture of its dependants.

FV-Unlink

Trust pruning

Inherited trust relationships are reviewed and removed where the inheritance is no longer warranted.

FV-Unlink

Sensitive-asset focus

Effort is concentrated on the relationships that touch the assets that matter, rather than spread thinly across the estate.

FV-Unlink

Authorised removals

Removals require the right authority and are scoped to the relationship under review.

FV-Unlink

Evidential record

Each removal is recorded with the rationale, the approver and the outcome through Archive.

Adoption guide

From first workflow to routine operation.

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

  1. 1

    Inventory the relationships

    Catalogue persistent connections, live dependencies and inherited trust touching the sensitive assets.

  2. 2

    Review with the owners

    Work through the inventory with the relevant owners to identify what is no longer warranted.

  3. 3

    Pilot the removals

    Remove a defined batch and confirm operational continuity before broadening the work.

  4. 4

    Operate and review

    Run Unlink as an ongoing discipline, with reviews recorded through Archive.

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.

Closing a matter means removing live dependencies and inherited access that keep the record exposed.

Read the playbook

The Leaders’ Playbook

Explains why permanently connected data is the exposure boards most often overlook.

Read the playbook

A Control Blueprint for AI: 2026 Playbook

Covers open weights and model assets that should not remain reachable from a production estate.

Read the playbook

All playbooks

Questions

Frequently asked about Unlink

Isolate draws the zones and holds their boundaries. Unlink removes the individual relationships that keep a sensitive asset reachable: persistent connections, live dependencies and inherited trust.

By reviewing an inventory of the relationships touching the sensitive assets with their owners, and removing what is no longer warranted. Each removal needs the right authority and is scoped to the relationship under review.

Restoring it is a deliberate act, approved and recorded like the removal, rather than something that quietly returns.

Adoption is designed around continuity: removals are piloted in a defined batch, and operational continuity is confirmed before the work is broadened.

All questions

Decide what stays connected.

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