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

Control by Firevault

Control access.Cut the affected path.

Supplier access, business networks and connected equipment all need routes into your systems. Control by Firevault governs when those routes exist and physically disconnects selected paths when your response policy requires it. Designed to contain exposure while limiting disruption to unaffected operations.

Controlled access. Rapid isolation. Evidence of every action.

Approximately 120–150 msManagement enable/disable operation

Around 2–3 secondsSMS round-trip operation, good signal

Observed in March 2025 tests on 10Gbps copper hardware. These are command-response observations, not isolated physical switching times or guaranteed deployment timings. SMS delivery can vary with signal, roaming and handshakes; command delivery, authorisation and processing, physical switching and service readiness are separate stages.

Why the path matters

Attackers do not stop at the first system. They follow the path.

A stolen supplier login can expose production systems. A compromised business network can put operational technology at risk. In healthcare, utilities and transport, the consequences reach beyond lost data to interrupted services. Detection matters. So does the ability to stop an incident crossing into systems you cannot afford to lose.

0

nationally significant cyber incidents handled by the NCSC in the year to August 2025, up from 89.

NCSC Annual Review 2025
0min

average time for an attacker to move from a first foothold into other systems. The fastest was 27 seconds.

CrowdStrike 2026 Global Threat Report

How we developed Control

It started with one principle: Disconnect to Protect®.

Control by Firevault applies that principle to the routes into your critical systems. A route exists when approved work needs it, and is physically disconnected when your response plan requires it.

  1. 01Where it began

    Built for networks that cannot afford to fail.

    Physical control of network connections was first developed for military, government, critical national infrastructure and OT environments: connected in normal operation, isolated at Layer 1 when a threat appears.

    Firebreak® hardware has won places on the NATO DIANA and UK MoD DASA accelerator programmes.

  2. 02What we built first

    We turned it around for data.

    Firevault reversed the model. Offline Secure Storage® keeps data physically disconnected as its normal state, and connects only when access is authorised.

    Explore Offline Secure Storage®

  3. 03Why we built Control

    Then we brought it back to the network.

    Operational systems cannot sit offline. Suppliers, business networks and connected equipment all need routes in. Control governs when those routes exist, and disconnects the affected path when your plan requires it.

    See it happen
  4. Nine modules
    Control Plans icon
    Control Plans
    Control Blueprints icon
    Blueprints

    04What Control became

    A platform, not a single device.

    Nine modules, combined into Control Plans for one risk and Control Blueprints for one industry. Every deployment is designed around your estate.

    Network Evolution. Rapid Protection.™

Physics, not promises.

Every Control action ends in a physical state you can verify: a path that exists, or a path that does not. And every action is on record.

How we engineered it

The point of difference

Do not just watch the path. Decide when it exists.

Your security tools detect threats. Your response policy or authorised operator decides what must happen. Control applies that decision to the selected connection.

  • Open for the job, then gone.Approved work gets a defined access window rather than a permanent route into critical systems.
  • Contain the incident, not the business.The affected path is physically disconnected, limiting disruption to unaffected operations.
  • Proof, not screenshots.Every action is signed, timestamped and logged, under a named authority.

See it happen

Situation

A supplier needs two hours on a control system to apply a patch.

No standing path to critical systems

    Control record. Each action is signed, timestamped and sent to SysLog.

What Control does

Concept illustration. Timings and module roles depend on your Blueprint and architecture.

Who it is for

Built for the teams who own the consequences.

Different estates have different consequences. Start with the connection that exposes a critical service, sensitive environment or operational process.

Does this sound familiar?

OT and utilitiesHead of operational technology

“Our supplier needs two hours on a control system to apply a patch.”

Their remote access stays open all year, because closing and reopening it is a job nobody owns. Anyone holding that login has a way in.

See the Third-Party Access Plan

Multi-site businessIT director

“Ransomware is spreading through the office network on a Saturday night.”

The team watches the alerts while someone drives to site to pull cables, unsure which ones are safe to pull.

See the Ransomware Containment Plan

Regulated financeChief information security officer

“The board wants evidence that our critical systems are kept apart.”

Separation lives in a policy document and firewall rules. Evidence is screenshots gathered after the event.

See the Compliance Evidence Plan

Where Control is used

Critical national infrastructureSeparate business access from essential-service systems, with planned isolation boundaries and a record of response actions. OT and SCADALimit access to legacy equipment and open maintenance paths only when needed, with isolation planned around safe process operation. Defence and national securityGovern connections into sensitive enclaves and test environments, with named authorisation and defined access windows. Regulated financeControl access to settlement systems and trading environments, with recorded actions to support investigation and oversight. Enterprise IT under NIS2 and DORATurn access and isolation policies into enforceable controls, with evidence to support risk reviews and regulatory obligations. Healthcare and researchSeparate clinical, research and administrative environments. Plan containment around patient safety and the dependencies services need.

The Control range

Choose where to start. Module, Plan or Blueprint.

Nine Modules are the building blocks. Control Plans combine them to answer one risk. Control Blueprints apply them to the systems of one industry. Every deployment is designed around your estate.

BP codes, twenty industries

Control Blueprints

From aviation and banking to utilities and water. Each Blueprint applies the modules to the systems of one industry.

BP-05 Aviation Blueprint icon
Aviation
BP-11 Maritime Blueprint icon
Maritime
BP-12 Motorsport Blueprint icon
Motorsport
Browse Control Blueprints

Firebreak® hardware, supplied by Firevault within Control

The AI Kill Switch

Physically disconnect an AI system from your data and networks on command.

Control is designed and quoted around your systems. Book a briefing

As featured in

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

Designed and engineered by Firevault

Three weaknesses. One physical answer.

We built Control around three practical problems: isolation that is too broad, response controls that depend on the affected environment, and actions that are difficult to evidence. The platform connects policy decisions to physical enforcement, with the boundaries and approvals designed for each estate.

01Per-zone independence

Once inside, an attacker can move through the network.

What we engineered: Defined isolation boundaries for circuits, tenants and operational segments, with dependencies assessed before deployment.

The result: Selected paths can be disconnected to limit further movement.

Stopping lateral movement

02Out-of-band command path

Take control through an independent command path.

What we engineered: A separately governed command route, rather than depending solely on the production connection being isolated.

The result: Response commands do not depend solely on the affected data path.

Protecting the management plane

03An evidential record

Pulling cables works, but it does not scale.

What we engineered: Authorised physical actions with signed, timestamped records, logged locally and to SysLog.

The result: A record of what changed, when and under whose authority.

Control in a live incident

Detection identifies the threat. Control enforces the response.

Keep detection, firewalls and incident response. Control adds a physical enforcement point where your plan calls for isolation, without relying on someone reaching a rack and pulling cables.

Posture Detect and respond Manual shutdown Control
Time to contain Minutes to hours Minutes, by hand Physical switching on command; response timing varies
Scope of action Alerts, blocks or isolates a host Depends on the cables and connections removed Per zone, per module, per Blueprint
Reversible without a site visit Yes No Yes
How isolation is enforced Configured software controls Manual cable disconnection Physical switching on the selected path
Recorded physical action No Ad hoc Yes, signed

Which services remain available depends on the zones, dependencies and response plan agreed for your estate.

Board-level evidence, not screenshots.

Control can help support these obligations. It does not make you compliant on its own.

NCSC Cyber Security Toolkit for Boards

  1. AGovernanceEach zone’s state is on record.
  2. BCultureNo silent reconnection. Every action is named.
  3. CBaseline controlsPhysical separation of OT, IT and crown jewels.
  4. DSupply chainSupplier access is time-bound and verified.
  5. EIncident responseRehearsed isolation with records for review.

NIS2 director duties

  1. 20Management accountabilityDecisions evidenced at the physical layer.
  2. 21Risk-management measuresSupports Article 21(2)(a), (d), (e) and (i).
  3. 23Incident notificationA record from the moment of isolation for the 24 and 72-hour notices.
Read the NIS2 mapping

The Control platform

Nine modules. Two families, one principle.

FIRE modules act on the path: opening, closing and cutting connections. VAULT modules govern what sits behind them: identity, boundaries and protected assets. Choose a Plan to see the modules it uses, or choose a module to see its role.

Control the path

Fracture, Isolate, Relay and Execute decide which paths exist, and for how long.

Protect the asset

Validate, Anchor, Unlink, Lock and Transfer decide what those paths can touch.

Choose a Control Plan

Control PlanRansomware Containment

Z0Internet and email
Z1Business network
Z2Crown-jewel systems
Kept in Offline Secure Storage®Clean recovery copies
Out-of-band command path

This Control Plan

Stop ransomware moving, spreading or reaching crown-jewel systems, across IT and OT.

FIRE-led

Primary modules: Fracture, Isolate and Execute.

Read the Ransomware Containment Plan

Module in this Plan

Fracture

Control the path

Physically disconnect the path.

Physically disconnects network paths to prevent unauthorised access, contain threats and stop an attack from progressing.

Fracture details

Concept illustration. Select any module to see what it does. Each Control Plan page shows the full topology and every module’s role.

Control the path. Protect the asset.

Containing an incident and protecting a recovery copy are different jobs. Control governs operational paths. Offline Secure Storage® separately keeps valuable data and recovery assets physically disconnected between authorised access sessions.

Questions worth asking

Before you change how paths are controlled.

Your engineers will want detail. Your board will want evidence. Here are the practical answers.

No. Your existing tools detect and investigate threats. Your response policy or authorised operator decides what action is appropriate. Control provides physical enforcement on the selected paths; it does not replace threat detection or your incident response team.

Firevault designs and engineers Control: the modules, Control Plans, Control Blueprints and the separately governed command route. Where a Plan needs a physical cut, Control uses Firebreak® hardware, supplied by Firevault within Control.

Control is designed for IT and OT estates, from field equipment up to enterprise networks (Purdue Levels 0 to 5). Most organisations start with one critical system, supplier connection or boundary and extend from there.

No. Control decides whether a selected path exists; it does not inspect what travels on it. Firebreak® hardware keeps its control and data layers completely separate, so your traffic is not read or changed.

Every deployment is designed around your estate, with zones, dependencies and approvals assessed before anything goes live. Like Offline Secure Storage®, Control can be delivered in a Firevault Bunker, on your premises or as a hybrid.

No single product can. Control can help support your obligations under frameworks such as DORA, IEC 62443, ISO 27001 and the NIST Cybersecurity Framework, and we map it to MITRE ATT&CK.

Yes. Start with the risk or industry that matters most: one Control Plan or one Control Blueprint, scoped to a single system, supplier connection or boundary. You can add more later. A demo is the quickest way to find the right starting point.

See all questions

Your next step

Decide what stays connected.

Start with one critical system, supplier connection or operational boundary. We will discuss the exposure, the Blueprint that fits, and what a scoped deployment needs: safe isolation, authorised access and evidence of the response.

Book a demo

Prefer to talk first? Speak to the team

Protecting business data? Ask us.