Firevault, offline secure storage, physically disconnected from the internet
Pricing
City buildings and business infrastructure at night

Nine modules.Nine ways to take physical control.

Cyber security tools can identify a threat, approve access or alert your team. But the network connection often remains physically available. Control by Firevault introduces a deliberate physical control point at selected network boundaries, so connections can be withdrawn, permitted or time-limited according to an agreed operating design.

ModulesPhysical control patterns

Control PlansSolutions to defined problems

BlueprintsSector applications

Before a changeBoundary, state, authority, restoration

The nine Modules

Find the control that fits the problem.

Each of the nine Modules addresses a different connection-control problem, from incident containment and network separation to authorised access, protected critical assets and diode-protected data paths.

9 Modules

FV-01 · Rapid physical disconnection and incident containment
Fracture module emblem: magenta hexagon with a slate blade split away

Fracture

Break a selected network path when an authorised incident response calls for physical separation.

Explore FV-01
FV-02 · Double-boundary network separation
Isolate module emblem: two magenta and slate forward chevrons, for double-boundary network separation

Isolate

Control both sides of a protected intermediate zone, rather than relying on a single network crossing.

Explore FV-02
FV-03 · Controlled access through a security airlock
Relay module emblem: magenta ring around a slate three-part airlock, for controlled access through a security airlock

Relay

Stage approved connectivity between public, intermediate and private zones, without leaving an open end-to-end route.

Explore FV-03
FV-04 · Authorised supervisory physical intervention
Execute module emblem: magenta and slate folded arrow, for authorised supervisory physical intervention

Execute

Give designated decision-makers a defined higher-priority way to change a selected connection state.

Explore FV-04
FV-05 · Independent two-person connection approval
Validate module emblem: magenta and slate pair of panels, for independent two-person connection approval

Validate

Require two independent approvals for the same proposed connection change before it is released.

Explore FV-05
FV-06 · Multi-boundary critical asset protection
Array module emblem: nested magenta and slate diamonds around a white centre, for multi-boundary critical asset protection

Array

Protect a named critical asset through multiple assessed, diode-protected connection boundaries.

Explore FV-06
FV-07 · Remove standing access to critical systems
Unlink module emblem: magenta and slate X split apart, for removing standing access to critical systems

Unlink

Physically withdraw selected access paths so critical systems are not continuously reachable through them.

Explore FV-07
FV-08 · Time-controlled physical connectivity
Lock module emblem: magenta and slate interlocking hook, for time-controlled physical connectivity

Lock

Allow selected connections only during approved time windows, with defined expiry and closure behaviour.

Explore FV-08
FV-09 · Controlled diode-protected data paths
Transfer module emblem: magenta and slate sphere with white one-way flow lines, for controlled diode-protected data paths

Transfer

Control when a designated connection around a separately enforced one-way data path is available.

Explore FV-09

How it fits together

Not another firewall.

Control is not another firewall, identity platform or content-inspection tool. It operates on assessed physical paths, using connection states that are authorised, tested and documented. Existing security and operational tools continue to decide what is safe; the selected physical boundary enforces the connection decision.

Modules

The physical control patterns. Each Module is a distinct reference arrangement with its own connection states and deployment requirements.

Control Plans

The solutions. CP-01 to CP-20 apply the appropriate Modules to defined security and operational problems.

Industry Blueprints

The application. The Plans are adapted to the sector's real systems, suppliers, continuity requirements and safety constraints.

Before a connection changes

Agreed before anything changes.

Every deployment starts with a named physical boundary, a defined normal state, mapped dependencies, an agreed decision-maker, failure behaviour and a tested restoration method. Disconnecting one controlled link does not remove alternative routes outside the design.

Your next step

Start with one critical connection.

We will help you identify the boundary, assess its dependencies and select the right Modules and Control Plans.