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

Control module · Fire layer

FV-Relay. A path that exists only for the work.

Relay turns access from a permanent state into a temporary, purposeful event. A connection exists for the work that needs it, under the conditions that suit it, for the window it requires, and then it does not.

As featured in

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

The problem

Paths opened for a moment tend to stay open for years.

The safest connection is the one that did not need to exist five minutes ago and will not exist five minutes from now.

  1. When the window ends, the path closes. There is no manual cleanup to remember and nothing left for someone to discover later.

  2. Sessions are tied to a named purpose, owner and scope rather than to a generic always-on tunnel.

  3. Every Relay session has an explicit start time and end time, with the end enforced automatically.

Problem 1

Persistent jump paths.

Paths opened for a one-off task tend to stay open. They become part of the environment, available to anyone who later finds them, attacker or otherwise.

Answered bySelf-closing

Problem 2

Implicit privilege.

Always-on connectivity quietly becomes always-on privilege. The original purpose is forgotten long before the route is closed.

Answered byPurpose-bound

Problem 3

Manual cleanup fails.

Cleanup that depends on someone remembering to close a path is cleanup that does not happen reliably.

Answered byDefined windows

The scenario

Scenario:
Vendor maintenance, on the clock.

Relay made vendor access a calendar entry rather than a standing arrangement. Step through it, or play it through.

Step 1 of 4

Request

A maintenance partner needs access to an operations system for a scheduled patching window.

Illustration.

Time-bound
Every connection has a defined start and end
Purposeful
Each path is opened for a specific, recorded reason
Conditional
Opening depends on identity, approval and state
Self-closing
Windows end automatically, no manual cleanup

Placement

Where Relay creates a time-bound path.

Relay is the controlled opening of a normally severed conduit. It exists for the time the work needs, no longer, and closes on its own. Grounded in IEC 62443-3-3 SR 1.13 Access via Untrusted Networks, NIST CSF PR.AC-3 and ISO 27001 A.5.15.

Relies on

  • A trustworthy time source the relay cannot be tricked about
  • Hard automatic close, not a reminder
  • Independent record of who opened it, why and for how long

Pairs with

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

IEC 62443 SR 1.13

Vendor maintenance window

Opens a vendor path with a fixed start time, fixed duration and fixed scope. Closes automatically.

NIST CSF PR.AC-3

Operator emergency access

Provides time-bound break-glass access for incident response, with multi-party approval and full audit.

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

NIST CSF PR.IP-4

Backup and replication windows

Brings the recovery vault online for the replication window only. The conduit is severed before the window expires.

ISO 27001 A.5.15

Audit and assessment sessions

External auditors get a scoped, time-bound path into the evidence set, never to live production.

Capabilities

What you get with every deployment.

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

FV-Relay

Defined windows

Every Relay session has an explicit start time and end time, with the end enforced automatically.

FV-Relay

Purpose-bound

Sessions are tied to a named purpose, owner and scope rather than to a generic always-on tunnel.

FV-Relay

Approval-gated

Opening a path requires the right approval pattern for that path, not just the requester’s intent.

FV-Relay

Scoped reach

Sessions reach only the systems the work requires, not the wider zone they happen to traverse.

FV-Relay

Self-closing

When the window ends, the path closes. There is no manual cleanup to remember and nothing left for someone to discover later.

FV-Relay

Evidential record

Each session is recorded through Archive, including who requested it, who approved it and what occurred.

Adoption guide

From first workflow to routine operation.

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

  1. 1

    Identify standing paths

    Inventory the connections that are currently always-on and categorise them by who they serve and why.

  2. 2

    Design the sessions

    Define the purposes, owners, approval patterns and acceptable windows for each category.

  3. 3

    Pilot with one workflow

    Move a single standing path to a Relay session pattern, including the calendar, approval and evidential pieces.

  4. 4

    Decommission the rest

    Migrate remaining standing access onto Relay sessions and close the persistent paths.

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.

Control for Water: Deployment Playbook

Covers third-party support and engineering access as purposeful, time-bound connections rather than standing links.

Read the playbook

A Control Blueprint for Aerospace and Aviation

Documents supplier and maintenance access windows across a distributed aviation supply chain.

Read the playbook

All playbooks

Questions

Frequently asked about Relay

For standing access, it can be. Instead of a persistent VPN, the owner approves a Relay session bound to a named partner, a named system and a defined window, and the path closes automatically when the window expires.

The end of every session is enforced automatically, so the path closes when the window expires. Continuing the work means a new, approved window, recorded like the first.

Yes. Operator emergency access is one of Relay’s conduits: time-bound break-glass access for incident response, with multi-party approval and full audit.

Firebreak severs the path. Relay is the controlled opening of a normally severed conduit, for the time the work needs, no longer, and it closes on its own.

All questions

Decide what stays connected.

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