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

Control Module FV-04

Execute Authorised supervisory physical intervention

Execute gives a nominated supervisory authority a defined way to change the physical state of a registered network connection when the ordinary operating process must be overridden.

Put an approved intervention above routine connection control.

Incident

Path exposed

Outcome

Control taken

The problem

The problem Execute addresses.

During an exceptional incident or operational escalation, the people accountable for the service may need an approved intervention path that is independent of routine access arrangements.

What it does

Execute gives a nominated supervisory authority a defined way to change the physical state of a registered network connection when the ordinary operating process must be overridden.

Before a connection 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.

The physical-control arrangement

A supervisory hierarchy above routine control. Agreed before it is needed.

A supervisory control hierarchy governing a selected physical connection, with documented priority, escalation, conflict resolution and restoration rules.

  1. Register the authority

    Register the condition and the supervisory authority.

  2. Confirm it is permitted

    Confirm the requested action is permitted.

  3. Apply the instruction

    Apply the defined higher-priority instruction.

  4. Record command and state

    Record the command and the reported state separately.

  5. Return to normal authority

    Return to normal authority only through the agreed release process.

What it does

  • Give designated decision-makers a defined higher-priority way to change a selected connection state.
  • Acts only on the registered crossings in the agreed design.
  • Records the command, the reported state and any independent verification separately.

What it does not claim

  • Execute does not detect incidents on its own, override plant safety systems or stop local AI computation. A delivered command is not automatically proof of the expected physical state.
  • Act on routes outside the registered design.

See it work

Two paths of authority. One enforcement point.

Routine management and a supervisory decision path both act on the same selected enforcement point. The decision and the observed physical result are recorded as different things.

Authority

Enforcement point

Connected system

Routine managementScheduled operational changes
Supervisory authorityNominated decision-makers
Business networkWhere the selected connection starts
AI platformOr another registered system

Stage

Routine management in authority

Routine management keeps C1 connected on its normal schedule.

Routine management has authority.

Commanded
No change.
Reported by the control point
Connected.
Independently verified
Matches the state confirmed at the last test.

Selected boundary

Execute module emblem: magenta and slate folded arrow, for authorised supervisory physical interventionExecute · FV-04 Selected enforcement pointBusiness network to AI platform · AI, IT, Cyber
Normal state
Connected under routine management.
What changes it
Routine management, or a higher-priority supervisory instruction.
What Execute does
Execute applies the supervisory instruction above routine control, with documented priority and restoration rules.

Concept illustration. Execute does not detect incidents on its own, override plant safety systems or stop local AI computation.

Operational boundaries and tests

Agreed in advance. Tested before it counts.

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.

Before you rely on it

What has to be true first.

  • The design names each boundary, its normal state and who can change it.
  • Dependencies are mapped, including what must keep running.
  • In OT and CNI, the process reaches a safe state before a route is withdrawn.
  • Failure behaviour and the restoration method are agreed and tested.
  • Wireless, cellular and other routes outside the design need their own controls.

Acceptance tests

Prove the operating conditions, not just the command.

  • Command, device-reported state and independent verification are recorded as separate observations.
  • Safe disconnection and restoration are tested in a planned window.
  • Priority and conflict rules are tested against routine changes, and release returns authority as agreed.
  • Alternative physical, wireless and cellular paths remain in scope for architecture review.

No guaranteed timing or universal fail-closed state is implied. Observed timings belong to the tested installation.

Related Control Plans

Adopt Execute through a Control Plan.

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

CP-17 Control Plan

CP-17 Emergency Authority Intervention Control Plan iconEmergency Authority Intervention

Give designated decision-makers a defined way to change selected connections when circumstances demand.

Open CP-17

CP-18 Control Plan

CP-18 AI Connectivity Control Control Plan iconAI Connectivity Control

Withdraw the connections an AI system uses to reach data and operations, on an authorised decision.

Open CP-18

Industry Blueprints adapt the Plans to each sector's systems, suppliers, continuity requirements and safety constraints. Explore the Blueprints.

Questions

Straight answers.

For security, network and operations owners.

What does Execute do?

Execute gives a nominated supervisory authority a defined way to change the physical state of a registered network connection when the ordinary operating process must be overridden.

What problem does it address?

During an exceptional incident or operational escalation, the people accountable for the service may need an approved intervention path that is independent of routine access arrangements.

How is the physical control arranged?

A supervisory control hierarchy governing a selected physical connection, with documented priority, escalation, conflict resolution and restoration rules.

What does it not claim?

Execute does not detect incidents on its own, override plant safety systems or stop local AI computation. A delivered command is not automatically proof of the expected physical state.

How does Execute relate to Control Plans?

Modules are the physical control capabilities. Control Plans apply the appropriate Modules to a defined security or operational problem; the design for your own connections is produced with Firevault in Control Studio. Execute is used in CP-17 Emergency Authority Intervention and CP-18 AI Connectivity Control.

Is this a validated installation?

No. It is a reference arrangement. Deployment drawings, interlock behaviour, approvals, link-state verification and failure modes are confirmed for your estate in discovery and acceptance testing.

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.

Discuss a critical connectionOr see all nine Modules