Fracture
Break a selected network path when an authorised incident response calls for physical separation.
Explore FV-01
Cyber security tools can identify a threat, approve access or alert your team. But the network connection often remains physically available. Control by Firevault introduces a deliberate physical control point at selected network boundaries, so connections can be withdrawn, permitted or time-limited according to an agreed operating design.
ModulesPhysical control patterns
Control PlansSolutions to defined problems
BlueprintsSector applications
Before a changeBoundary, state, authority, restoration
The nine Modules
Each of the nine Modules addresses a different connection-control problem, from incident containment and network separation to authorised access, protected critical assets and diode-protected data paths.
9 Modules
Break a selected network path when an authorised incident response calls for physical separation.
Explore FV-01Control both sides of a protected intermediate zone, rather than relying on a single network crossing.
Explore FV-02Stage approved connectivity between public, intermediate and private zones, without leaving an open end-to-end route.
Explore FV-03Give designated decision-makers a defined higher-priority way to change a selected connection state.
Explore FV-04Require two independent approvals for the same proposed connection change before it is released.
Explore FV-05Protect a named critical asset through multiple assessed, diode-protected connection boundaries.
Explore FV-06Physically withdraw selected access paths so critical systems are not continuously reachable through them.
Explore FV-07Allow selected connections only during approved time windows, with defined expiry and closure behaviour.
Explore FV-08Control when a designated connection around a separately enforced one-way data path is available.
Explore FV-09How it fits together
Control is not another firewall, identity platform or content-inspection tool. It operates on assessed physical paths, using connection states that are authorised, tested and documented. Existing security and operational tools continue to decide what is safe; the selected physical boundary enforces the connection decision.
The physical control patterns. Each Module is a distinct reference arrangement with its own connection states and deployment requirements.
The solutions. CP-01 to CP-20 apply the appropriate Modules to defined security and operational problems.
The application. The Plans are adapted to the sector's real systems, suppliers, continuity requirements and safety constraints.
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.
Your next step
We will help you identify the boundary, assess its dependencies and select the right Modules and Control Plans.