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

Control Module FV-08

Lock Time-controlled physical connectivity

Lock governs selected physical network connections through a defined schedule. Approved windows permit connectivity; expiry triggers the agreed closing behaviour, subject to safe-state requirements.

The connection exists only when the clock and authority permit.

Incident

Path exposed

Outcome

Control taken

The problem

The problem Lock addresses.

Maintenance links, recurring support routes and temporary management crossings can be left open because no one remembers to close them. A documented connection window reduces that standing exposure.

What it does

Lock governs selected physical network connections through a defined schedule. Approved windows permit connectivity; expiry triggers the agreed closing behaviour, subject to safe-state requirements.

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

An access time-lock on the designated connection. Agreed before it is needed.

An access time-lock applied to one or more designated connections, with schedule, authorisation, exception handling and expiry behaviour defined before deployment.

  1. Agree the calendar

    Agree the allowed connection calendar.

  2. Identify approvals

    Identify any separate approval required.

  3. Open for the window

    Open the assessed path for the permitted window.

  4. Close at the end condition

    Close it at the designated end condition.

  5. Log and test

    Log exceptions and test clock, communications and power-loss behaviour.

What it does

  • Allow selected connections only during approved time windows, with defined expiry and closure behaviour.
  • 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

  • Lock does not promise native inactivity-based disconnection or guaranteed closure after command-path loss unless the tested implementation explicitly provides it.
  • Act on routes outside the registered design.

See it work

The clock and authority decide. One connection, one window.

A timeline linked to a single connection-state indicator: closed outside the window, authorised open during it, closed after expiry.

Supplier

Maintained system

Supplier supportRecurring maintenance route
Maintained systemFor example a building management system

Stage

07:00. Outside the window

The connection is closed. The calendar allows Tuesday 09:00 to 11:00 for supplier maintenance.

Calendar agreed with the system owner.

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

Selected boundary

Lock module emblem: magenta and slate interlocking hook, for time-controlled physical connectivityLock · FV-08 Time-locked connectionSupplier support to maintained system · OT, IT, CNI
Normal state
Closed outside the agreed calendar.
What changes it
The agreed calendar and any separate approval.
What Lock does
Lock opens the connection only for the permitted window and closes it at the designated end condition.

Concept illustration. Times are examples. Lock does not promise inactivity-based disconnection or guaranteed closure after command-path loss unless the tested implementation provides it.

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.
  • Opening, expiry, clock drift, communications loss and power loss are tested for the installed model.
  • 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 Lock through a Control Plan.

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

CP-09 Control Plan

CP-09 Scheduled Critical Maintenance Control Plan iconScheduled Critical Maintenance

Connections for planned maintenance that open for the agreed window and close when it ends.

Open CP-09

CP-10 Control Plan

CP-10 High-Risk Production Changes Control Plan iconHigh-Risk Production Changes

High-risk changes to production made through a connection that exists only for the approved change.

Open CP-10

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 Lock do?

Lock governs selected physical network connections through a defined schedule. Approved windows permit connectivity; expiry triggers the agreed closing behaviour, subject to safe-state requirements.

What problem does it address?

Maintenance links, recurring support routes and temporary management crossings can be left open because no one remembers to close them. A documented connection window reduces that standing exposure.

How is the physical control arranged?

An access time-lock applied to one or more designated connections, with schedule, authorisation, exception handling and expiry behaviour defined before deployment.

What does it not claim?

Lock does not promise native inactivity-based disconnection or guaranteed closure after command-path loss unless the tested implementation explicitly provides it.

How does Lock 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. Lock is used in CP-09 Scheduled Critical Maintenance and CP-10 High-Risk Production Changes.

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