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.
Control Module FV-08
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
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 applied to one or more designated connections, with schedule, authorisation, exception handling and expiry behaviour defined before deployment.
Agree the allowed connection calendar.
Identify any separate approval required.
Open the assessed path for the permitted window.
Close it at the designated end condition.
Log exceptions and test clock, communications and power-loss behaviour.
What it does
What it does not claim
See it work
A timeline linked to a single connection-state indicator: closed outside the window, authorised open during it, closed after expiry.
Supplier
Maintained system
Stage
The connection is closed. The calendar allows Tuesday 09:00 to 11:00 for supplier maintenance.
Calendar agreed with the system owner.
Selected boundary
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
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
Acceptance tests
No guaranteed timing or universal fail-closed state is implied. Observed timings belong to the tested installation.
Related Control Plans
The solutions. CP-01 to CP-17 apply the appropriate Modules to defined security and operational problems.
CP-09 Control Plan
Connections for planned maintenance that open for the agreed window and close when it ends.
CP-10 Control Plan
High-risk changes to production made through a connection that exists only for the approved change.
Industry Blueprints adapt the Plans to each sector's systems, suppliers, continuity requirements and safety constraints. Explore the Blueprints.
Questions
For security, network and operations owners.
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.
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.
An access time-lock applied to one or more designated connections, with schedule, authorisation, exception handling and expiry behaviour defined before deployment.
Lock does not promise native inactivity-based disconnection or guaranteed closure after command-path loss unless the tested implementation explicitly provides it.
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.
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
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