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

Control module · Fire layer

FV-Execute. Act on a decision, not a habit.

Execute initiates control actions in response to policy, approval, schedule, incident state or supervisory override. The decision to act is recorded with the action, so there is no ambiguity about why the environment changed.

As featured in

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

The problem

An action without a reason is a fact you will struggle to defend.

An action without a reason is a fact you will struggle to defend. Execute records both, together, every time.

  1. The reason for the action and the action itself are recorded together through Archive.

  2. Actions begin because a defined condition was met, not because somebody remembered.

  3. An explicit supervisory layer can pause, redirect or stop an action when human judgement needs to take over.

Problem 1

Ad-hoc response.

When a control action is taken by the person who happens to be on shift, the rationale lives only in their memory and the outcome is harder to reason about later.

Answered byDecision and execution paired

Problem 2

Missed conditions.

Actions that should follow a schedule, a state change or an upstream signal often do not, because nothing systematic connects the signal to the action.

Answered byCondition-led initiation

Problem 3

No supervisory layer.

Without an explicit supervisory override, a runaway automation or a faulty trigger has no clean way to be paused, redirected or stopped.

Answered bySupervisory override

The scenario

Scenario:
A scheduled lockdown that does not depend on memory.

Execute is the discipline of treating an action as a decision, not as a habit. Step through it, or play it through.

Step 1 of 4

Schedule

A weekly maintenance pattern requires several systems to be placed into a restricted state outside business hours.

Illustration.

Triggered
Actions follow defined conditions, not informal practice
Approved
Sensitive actions require the right approval pattern
Recorded
Every action is paired with its reason and approver
Reversible
Where appropriate, actions have a defined undo path

Placement

Where Execute requires an approved action.

Execute is the gate around any change that matters. Nothing destructive, privileged or boundary-altering happens without a named approver and a recorded decision. Grounded in IEC 62443-3-3 SR 1.5 Authenticator Management, NIST CSF PR.AC-4 and ISO 27001 A.5.18, A.8.18.

Relies on

  • Independent approver identities that cannot be impersonated from the system being changed
  • Recorded intent for every action, not just an audit log
  • Quorum policy that survives a single compromised admin

Pairs with

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

IEC 62443 SR 5.1

Firebreak open and close events

Every change to the physical conduit state is an approved Execute event, not a console click.

NIST CSF PR.AC-4

Privileged change to OT assets

Engineering changes against PLCs, RTUs and HMIs require multi-party approval before the path is opened.

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

NIST CSF PR.IP-9

Restore from offline vault

Restoration from the offline vault is an explicit, recorded Execute decision with quorum approval.

ISO 27001 A.5.18

Boundary policy changes

Changes to the zone and conduit definitions themselves are governed actions, not silent edits.

Capabilities

What you get with every deployment.

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

FV-Execute

Condition-led initiation

Actions begin because a defined condition was met, not because somebody remembered.

FV-Execute

Approval where it matters

Sensitive actions require the right approval before execution rather than after the fact.

FV-Execute

Incident-aware

Execute responds to incident state so containment, isolation and lockdown actions can be carried out at machine speed within agreed bounds.

FV-Execute

Supervisory override

An explicit supervisory layer can pause, redirect or stop an action when human judgement needs to take over.

FV-Execute

Scoped authority

Each action is constrained to the systems and operations the policy permits.

FV-Execute

Decision and execution paired

The reason for the action and the action itself are recorded together through Archive.

Adoption guide

From first workflow to routine operation.

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

  1. 1

    Catalogue the actions

    List the control actions that matter, including their owners, scopes and current triggers.

  2. 2

    Define conditions and approvals

    For each action, agree the policy, schedule, incident state and approval pattern that should govern it.

  3. 3

    Pilot with one workflow

    Move one action onto Execute end-to-end, including the supervisory override and the evidential record.

  4. 4

    Operate and review

    Run Execute as the initiation layer for control actions and review patterns through Archive 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.

A Control Blueprint for AI: 2026 Playbook

The kill switch doctrine chapter explains who may initiate a control action against an agent or cluster, and on what authority.

Read the playbook

Control for Water: Deployment Playbook

Sets the approval pattern, escalation route and pre-approved conditions for control actions during a supply incident.

Read the playbook

All playbooks

Questions

Frequently asked about Execute

It is the initiation layer for control actions. Actions begin because a defined condition was met, under the approval pattern agreed for them, and the decision and the action are recorded together through Archive.

An explicit supervisory layer can pause, redirect or stop an action when human judgement needs to take over, and each action is constrained to the systems and operations the policy permits.

Sensitive actions require the right approval before execution, not after the fact. Nothing destructive, privileged or boundary-altering happens without a named approver and a recorded decision.

The supervisory override can pause, redirect or stop actions. Where appropriate, actions also have a defined undo path.

All questions

Decide what stays connected.

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