Control Blueprints
FIRE controls the path. VAULT protects the asset.
Six buyer-led Blueprints. Each one names its lead layer, the primary modules that deliver it, and the supporting modules that round it out.
- 6
- Blueprints
- 9
- Modules
- 3
- Lead types
What a Blueprint is
A pattern. A lead layer. A defined set of modules.
Controls the path. Disconnects, isolates and severs the route the attack would take.
Protects the asset. Holds the data, identity and evidence behind verifiable controls.
Path and asset together. Used where access must be controlled and what it touches must be locked.
Blueprints in play
See the modules compose a Blueprint.
Deal nine modules into a path. Firebreak lands on the gate and the route severs. Click any card to pause.
RW·Break the attack path, contain systems, preserve clean recovery.
The six Blueprints
Pick a Blueprint to see the modules in detail.
Filter by lead layer, module or sector to narrow the patterns that fit your environment.
Stop Kill-Chain Ransomware
Stop ransomware moving, spreading or reaching the crown jewels.
Contain Active Breaches
When prevention fails, containment must be physical, immediate and provable.
Control Third-Party Access
Give third parties access without giving them a permanent doorway.
Enforce Physical Segmentation
Segmentation should not just be logical. It should be physically enforceable.
Protect Critical Infrastructure
Keep critical systems available, controlled and disconnected from unnecessary exposure.
Prove Compliance Through Control
Compliance becomes stronger when control can be demonstrated, not just documented.
The nine modules
Every Blueprint is built from these.
Physically opens or closes connection paths to prevent unauthorised access and stop attack progression.
Separates systems and networks into controlled zones to reduce lateral movement and enforce trust boundaries.
Allows connectivity only when needed, for a defined purpose, under controlled conditions and for a limited time.
Initiates control actions when a policy, approval, schedule, incident state or supervisory override requires action.
Checks whether a request, command or approval should proceed before access, action or transfer is allowed.
Preserves critical files and records for recovery, retention, compliance, continuity and evidential integrity.
Removes persistent connections, live dependencies and inherited trust relationships that keep sensitive assets exposed.
Restricts access through identity, authority, policy, permission and operational controls.
Controls how sensitive assets move into, out of or between protected environments through approved paths.



Compose Control for your environment
Talk to our team about combining these Blueprints around your estate.
Takes about 2 minutes. No account needed.