What it does
Isolate adds physical connection control to both sides of an assessed intermediate zone. The design reduces reliance on a single logical boundary between public-facing and protected environments.
Control Module FV-02
Isolate adds physical connection control to both sides of an assessed intermediate zone. The design reduces reliance on a single logical boundary between public-facing and protected environments.
Separate the zones. Control both crossings.
Incident
Path exposed
Outcome
Control taken
The problem
A network zone can be exposed through more than one side. A DMZ or intermediate environment needs its inbound and outbound crossings considered together, with clear rules for which connections may exist.
What it does
Isolate adds physical connection control to both sides of an assessed intermediate zone. The design reduces reliance on a single logical boundary between public-facing and protected environments.
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 double-protection arrangement with independently controlled physical connection points on both sides of a defined intermediate zone.
Map the outer and inner crossings of the intermediate zone.
Assign normal states and the permitted combinations of the two crossings.
Authorise any change through the agreed decision-maker.
Apply the selected physical state at the correct boundary.
Verify the resulting zone reachability and the restoration path.
What it does
What it does not claim
See it work
Three labelled zones with a separately controlled boundary on each side of the intermediate zone. The states of the two crossings are agreed together, not as a single switch.
Public-facing
Intermediate zone
Protected
Stage
The outer crossing serves the public service. The inner crossing rests disconnected, so the intermediate zone does not reach the protected environment.
Normal states agreed by the service and security owners.
Selected boundary
Concept illustration. Two controlled crossings do not prove complete segmentation if redundant, cellular, wireless or shared-service paths bypass the design.
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-11 Control Plan
Control the crossings between business IT and operational technology, without treating the process like office IT.
CP-12 Control Plan
Reduce the number of connections that can reach essential systems, so fewer routes stay open by default.
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.
Isolate adds physical connection control to both sides of an assessed intermediate zone. The design reduces reliance on a single logical boundary between public-facing and protected environments.
A network zone can be exposed through more than one side. A DMZ or intermediate environment needs its inbound and outbound crossings considered together, with clear rules for which connections may exist.
A double-protection arrangement with independently controlled physical connection points on both sides of a defined intermediate zone.
Two controlled crossings do not prove complete segmentation if redundant, cellular, wireless or shared-service paths bypass the design.
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. Isolate is used in CP-11 IT/OT Boundary Protection and CP-12 Critical System Exposure Reduction.
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