CP-01Ransomware Containment
Cut the paths ransomware uses to spread before encryption reaches critical systems.
Open CP-01
Control PlansCP-01 to CP-20The method library
One problem. One plan.A physical answer to each.
A Control Plan describes a repeatable method for one security problem: which connections to remove, control, isolate or open only when they are needed, who decides, and how it is checked. Find the plan that matches the problem you are trying to solve.
- Control Plans
- 20 in the library
- Control modules
- 9
- Every plan includes
- Register, runbook and acceptance tests
- Applies to
- Any organisation, any sector
- Applied by industry
- Industry Blueprints
Find your Control Plan
Start with the problem. Find the plan.
Every plan is built for one problem. Filter by the problem you are facing, or search by module or keyword.
Showing 20 Control Plans
No plan matches that yet. Tell us the problem and we will show you how Control would approach it.
CP-01
CP-02Live Incident Containment
Physically disconnect the affected path during a live incident while the rest of the operation keeps running.
Open CP-02
CP-03Third-Party Access Control
Supplier and vendor paths that exist only for approved work, in a defined window.
Open CP-03
CP-04Physical Network Segmentation
Zones separated at Layer 1, so a boundary holds even when software controls are compromised.
Open CP-04
CP-05Critical Asset Protection
Separate business access from essential systems, with planned isolation boundaries.
Open CP-05
CP-06Controlled Access & Assurance
Connect approvals and observed control states to agreed record sources, with collection and retention defined for the actions in scope.
Open CP-06
CP-07Security Airlock
A two-stage gateway with independently controlled connections.
Open CP-07
CP-08AI Connectivity Control
Disconnect an AI system from your data and networks when it behaves unexpectedly.
Open CP-08
CP-09Controlled Data Transfer
A controlled exchange path between two separate environments.
Open CP-09
CP-10Executive Override
Authorised senior intervention that withdraws predefined connections.
Open CP-10
CP-11ProposedSupply Chain Isolation
Keep supplier networks separate from your own environment.
Open CP-11
CP-12ProposedPrivileged Access Control
Administrator access through a controlled network entry point.
Open CP-12
CP-13ProposedMaintenance Window Control
Connections that exist only for a scheduled maintenance window.
Open CP-13
CP-14ProposedCompromised Device Isolation
Physically isolate one affected device from the network.
Open CP-14
CP-15ProposedOperational Technology Protection
Industrial controllers behind a physical network boundary.
Open CP-15
CP-16ProposedRemote Site Isolation
Disconnect the communications link to a remote facility.
Open CP-16
CP-17ProposedChange Window Enforcement
Approved changes made through a timed physical connection.
Open CP-17
CP-18ProposedData Exfiltration Interruption
Interrupt outbound paths at a physical boundary.
Open CP-18
CP-19ProposedAutonomous System Intervention
Disconnect the communications of an autonomous system.
Open CP-19
CP-20ProposedMulti-Party Authorisation
Two independent approvals required before a connection opens.
Open CP-20All twenty Control Plans have their own page.
What every plan includes
Written the same way, so you can compare them.
Every Control Plan is commercially clear at the top and technically credible further down. Your board, your CISO and your engineers each get what they need.
01The outcome and the stakes
What the plan achieves, who needs it, and what is at risk without it.
02Control in Action
An interactive view of the crossings before control, in normal use, under attack and in recovery.
03The connection register
Every protected route: normal state, authorisation, enforcement, response and evidence.
04The operational runbook
Who does what in normal conditions, maintenance, an incident and restoration.
05Engineering and testing
How it fits your firewalls, SIEM and EDR, and the acceptance criteria it must pass.
06Limits and frameworks
What it does not protect against, and the standards it can help support.
Modules in each plan
The modules behind each Plan.
The primary modules each plan relies on. Supporting modules are set out in each plan’s specification.
CP-01 Ransomware Containment
Fracture · Isolate · Execute · Validate
CP-02 Live Incident Containment
Fracture · Isolate · Execute · Validate
CP-03 Third-Party Access Control
Fracture · Relay · Execute · Validate
CP-04 Physical Network Segmentation
Fracture · Isolate · Relay · Unlink · Lock
CP-05 Critical Asset Protection
Fracture · Isolate · Relay · Execute · Validate · Anchor · Lock · Transfer
CP-06 Controlled Access & Assurance
Fracture · Relay · Execute · Validate · Anchor · Lock · Transfer
CP-07 Security Airlock
CP-08 AI Connectivity Control
Fracture · Isolate · Relay · Execute · Validate
CP-09 Controlled Data Transfer
CP-10 Executive Override
CP-11 Supply Chain Isolation
Fracture · Isolate · Relay · Execute · Validate · Lock
CP-12 Privileged Access Control
Fracture · Relay · Execute · Validate · Anchor · Lock
CP-13 Maintenance Window Control
Relay · Execute · Validate · Anchor · Lock · Transfer
CP-14 Compromised Device Isolation
Fracture · Isolate · Execute · Validate · Unlink · Lock
CP-15 Operational Technology Protection
Fracture · Isolate · Relay · Execute · Validate · Anchor
CP-16 Remote Site Isolation
Fracture · Isolate · Relay · Execute · Validate
CP-17 Change Window Enforcement
Relay · Validate · Transfer
CP-18 Data Exfiltration Interruption
Fracture · Isolate · Execute
CP-19 Autonomous System Intervention
Fracture · Isolate · Execute · Validate · Anchor · Lock
CP-20 Multi-Party Authorisation
Fracture · Relay · Execute · Validate · Anchor · Lock
Plans and Blueprints
The plan is the method. The Blueprint is the application.
A ransomware containment plan applies to many organisations. An industry Blueprint shows how it combines with supplier access, IT and OT separation, recovery and safety in a real sector.
Control modulesThe capabilities
Fracture, Isolate, Relay, Execute, Validate, Anchor, Unlink, Lock and Transfer. Each does one physical job.
Example: Firebreak® cuts a selected crossing at Layer 1.How Control worksControl PlansThe method
How modules combine to solve one problem, written so it can be repeated in any organisation.
Example: CP-01 cuts the routes out of an infected zone on a high-confidence alert.Browse the plansIndustry BlueprintsThe application
How the relevant plans adapt to a sector’s infrastructure, suppliers, safety requirements and regulators.
Example: Control for Water combines five plans, with Offline Secure Storage® kept separate.Explore Industry BlueprintsHow a plan becomes yours
From the library to your network.
No plan is installed as-is. Each one is mapped to your own connections, decision makers and constraints, then tested before you rely on it.
- 1Discovery
Map the connections in scope, what must keep running and who decides.
- 2Draft the plan
Write the connection register, decision rules and runbook for your network.
- 3Pilot
Put the first crossing under control in a planned window.
- 4Test and evidence
Run the acceptance criteria and keep the evidence.
- 5Operate and expand
Add crossings and plans, using the same method.
→Build your Control Plan
Tell us the problem. We will show you the plan.
Tick what sounds familiar. You’ll see which Control Plans your discovery session would start with.
?Questions worth asking
Before you choose a plan.
The practical answers your board, your CISO and your engineers will want.
A Control Plan is a repeatable method for one problem, such as ransomware spreading or supplier access. An industry Blueprint combines the relevant plans and adapts them to a sector’s real infrastructure, suppliers, safety requirements and regulators.
Yes. Most organisations start with one plan where the risk is greatest and add others. Plans share the same modules, so they work together.
No. Each plan uses only the modules it needs. CP-01, for example, relies on Execute, Firebreak® and Isolate.
No. Firewalls, detection and endpoint tools stay. A plan adds a physical layer they can act through, and that an attacker cannot switch off from inside the network.
Separately. Control decides which connections exist. Offline Secure Storage® keeps recovery copies, configurations and evidence physically disconnected, with its own access.
With a discovery session. We agree the problem, the first crossing to control and who decides, then pilot and test it before you rely on it.
→Your next step
Pick the problem. We will build the plan.
A working session on your network: the problem, the plan that fits, and the first crossing to control.
Build your Control Plan