What does Fracture do?
When an incident requires a physical response, Fracture disconnects the registered network crossing at Layer 1. It acts on the link selected in advance, rather than changing a filtering rule while leaving that physical connection available.
What problem does it address?
A live attack can exploit an existing connection between environments. Emergency software-policy changes may not be the right final action when responders need that crossing to be physically unavailable.
How is the physical control arranged?
A physical circuit-breaker arrangement at the assessed crossing, alongside existing security controls. An approved incident decision initiates the connection-state change; release is a separate authorised action.
What does it not claim?
Fracture cannot remove an attacker already inside a zone, stop every alternative network route or guarantee unaffected services continue unless their independence has been proven.
How does Fracture 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. Fracture is used in CP-01 Ransomware Containment and CP-02 Live Incident Response.
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.