--- title: "CP-19 Autonomous System Intervention | Control by Firevault" url: https://fire-vault.com/control-plan/autonomous-system-intervention description: "Disconnect the communications of an autonomous system." lang: en-GB --- Control Plan **CP-19**Autonomous System Intervention Proposed Control Plan. Subject to technical and publication approval. # An autonomous system acts beyond its remit. Which network connections can you withdraw? Image: CP-19 Autonomous System Intervention Control Plan icon (https://fire-vault.com/__l5e/assets-v1/815349be-891b-4b1f-98e7-dfdbb0601086/CP-19_autonomous-system-intervention.png) Disconnect the communications of an autonomous system. Book a briefing: https://fire-vault.com/demo See Control in Action Plan CP-19 Purpose Autonomous System Intervention Selected connections 8 Modules Fracture · Isolate · Execute · Validate · Anchor · Lock Scope Registered external communications and authorised management crossings. What is at stake ## Why autonomous system intervention matters. The operating risk includes both continued access and the consequences of losing it. **Persistent autonomous connectivity**The autonomous system network connections can remain available beyond the approved need. **Continued local execution**Network disconnection does not stop local execution. Independent safety controls remain necessary. **Autonomous system ownership**Name the autonomous system owner and the conditions for a connection change. **Autonomous connection checks**Check the observed state of the autonomous system network connections, including parallel routes. The problem today ## Where you are IP connected today. CP-19 reviews eight IP-connected paths in your business. While a path stays connected over IP, it is a route that can be reached, misused or exploited. Each path below carries its own risk to agree with its owner. **8**IP-connected paths reviewed **8**Risks to agree with owners **6**Control modules applied 1. _Risk 1_**Autonomous external crossing · All physical members and parallel paths to be mapped.** Whenever this path is open over IP, it is a route that can be reached, misused or exploited. **Agreed state:** Connected within approved operating scope 2. _Risk 2_**Remote instruction route · All physical members and parallel paths to be mapped.** Whenever this path is open over IP, it is a route that can be reached, misused or exploited. **Agreed state:** Connected within approved operating scope 3. _Risk 3_**Engineering management path · All physical members and parallel paths to be mapped.** Whenever this path is open over IP, it is a route that can be reached, misused or exploited. **Agreed state:** Disconnected by default 4. _Risk 4_**External service boundary · All physical members and parallel paths to be mapped.** Whenever this path is open over IP, it is a route that can be reached, misused or exploited. **Agreed state:** Connected within approved operating scope 5. _Risk 5_**Review workspace crossing · All physical members and parallel paths to be mapped.** Whenever this path is open over IP, it is a route that can be reached, misused or exploited. **Agreed state:** Disconnected by default 6. _Risk 6_**Secondary site route · All physical members and parallel paths to be mapped.** Whenever this path is open over IP, it is a route that can be reached, misused or exploited. **Agreed state:** Connected within approved operating scope 7. _Risk 7_**Equipment integration conduit · All physical members and parallel paths to be mapped.** Whenever this path is open over IP, it is a route that can be reached, misused or exploited. **Agreed state:** Connected within approved operating scope 8. _Risk 8_**Internet service crossing · All physical members and parallel paths to be mapped.** Whenever this path is open over IP, it is a route that can be reached, misused or exploited. **Agreed state:** Connected within approved operating scope Matching industry Blueprints What Firevault changes ## What changes with this Plan. Withdraw selected autonomous network connections while assessing local behaviour separately. | Connection | Agreed normal state | Control action | | --- | --- | --- | | Autonomous external crossing · All physical members and parallel paths to be mapped. | Connected within approved operating scope | Isolate groups registered conduits; Fracture withdraws each authorised connection; Execute applies the action. | | Remote instruction route · All physical members and parallel paths to be mapped. | Connected within approved operating scope | Fracture withdraws this authorised connection. Validate checks authority before action. | | Engineering management path · All physical members and parallel paths to be mapped. | Disconnected by default | Fracture withdraws this authorised connection. Validate checks authority before action. | | External service boundary · All physical members and parallel paths to be mapped. | Connected within approved operating scope | Fracture withdraws this authorised connection. Validate checks authority before action. | | Review workspace crossing · All physical members and parallel paths to be mapped. | Disconnected by default | Fracture withdraws this authorised connection. Validate checks authority before action. | | Secondary site route · All physical members and parallel paths to be mapped. | Connected within approved operating scope | Fracture withdraws this authorised connection. Validate checks authority before action. | | Equipment integration conduit · All physical members and parallel paths to be mapped. | Connected within approved operating scope | Fracture withdraws this authorised connection. Validate checks authority before action. | | Internet service crossing · All physical members and parallel paths to be mapped. | Connected within approved operating scope | Fracture withdraws this authorised connection. Validate checks authority before action. | Local execution, model shutdown, physical stopping and unregistered communication channels. Control in Action ## Autonomous System Intervention: see the selected path change. Control in Action Stage Before agreed physical control The operating risk includes both continued access and the consequences of losing it.**Connected routes require review. Discovery checks your real dependencies.** **0**reached by the attack **10**still running Physical crossings - Autonomous external crossing · All physical members and parallel paths to be mapped. _Always connected_ - Remote instruction route · All physical members and parallel paths to be mapped. _Always connected_ - Engineering management path · All physical members and parallel paths to be mapped. _Always connected_ - External service boundary · All physical members and parallel paths to be mapped. _Always connected_ - Recovery access (OSS) _Not in place_ 1. _FB_**Fracture** · Review the purpose and ownership of each selected connection. Illustrative selected connections, not an approved deployment. Agree service dependencies and authorised actions before implementation. This illustration does not predict attack reach or service availability. Offline Secure Storage® remains separate. The modules involved ## The Control modules behind this Plan. In CP-19: withdraws the scoped external path. In CP-19: groups every registered autonomous-zone conduit. In CP-19: applies the authorised communications intervention. ### CP-19Autonomous System Intervention Z0 Requesting environment Z1 Protected systems Z2 Related operations Held in Offline Secure Storage® Selected recovery material, held separately Out-of-band command path This Control Plan #### Withdraw selected autonomous network connections while assessing local behaviour separately. Primary modules: Fracture, Isolate, Execute, Validate, Anchor and Lock. Read the operational detail Module in this plan Image: Fracture module icon (https://fire-vault.com/__l5e/assets-v1/f709a192-16d2-4206-86f3-842a3200db9d/firebreak-icon.png) #### Fracture Controls the path Physically disconnects network paths to prevent unauthorised access, contain threats and stop an attack from progressing. Explore the Fracture module (https://fire-vault.com/control/modules/fracture) Concept illustration. Select any module to see what it does. Placement is drawn from your own network in discovery. Control Plans that work alongside CP-19 **CP-18 · Proposed****Data Exfiltration Interruption**Interrupt outbound paths at a physical boundary. _Open CP-18_: https://fire-vault.com/control-plan/data-exfiltration-interruption **CP-20 · Proposed****Multi-Party Authorisation**Two independent approvals required before a connection opens. _Open CP-20_: https://fire-vault.com/control-plan/multi-party-authorisation **CP-17 · Proposed****Change Window Enforcement**Approved changes made through a timed physical connection. _Open CP-17_: https://fire-vault.com/control-plan/change-window-enforcement See all Control Plans: https://fire-vault.com/control#blueprints How Control works: https://fire-vault.com/control As featured in - Read about Firevault on TechRadar Pro: https://www.techradar.com/pro/uk-startup-put-physical-disconnect-switch-in-its-cloud-storage-offering-to-mitigate-ransomware-attacks-but-will-that-be-enough - Read about Firevault on Yahoo Finance: https://uk.finance.yahoo.com/news/firevault-launches-help-businesses-directors-074500961.html - Read about Firevault on Channel Insider: https://www.channelinsider.com/security/tools-and-platforms/firevault-security-offline-platform-offering/ - Read about Firevault on Security Buyer: https://securitybuyer.com/uk-cybersecurity-startup-launches-firevault/ - Read about Firevault on SecurityBrief: https://securitybrief.com.au/story/firevault-unveils-offline-digital-vault-to-combat-rising-cyber-risks The Control Plan specification ## Each selected connection, written down. Autonomous external crossing · All physical members and parallel paths to be mapped._Connected within approved operating scope_ Normal state Connected within approved operating scope Authorisation Authorised intervention after scope and operational-impact review Module action Isolate groups registered conduits; Fracture withdraws each authorised connection; Execute applies the action. Business effect Connectivity across this crossing is lost. Assess affected supervision, tools and local dependencies. Failure behaviour Specify, justify and test power-loss and fault behaviour before approval. Remote instruction route · All physical members and parallel paths to be mapped._Connected within approved operating scope_ Normal state Authorisation Module action Fracture withdraws this authorised connection. Validate checks authority before action. Business effect Failure behaviour Engineering management path · All physical members and parallel paths to be mapped._Disconnected by default_ Normal state Disconnected by default Authorisation Module action Business effect Failure behaviour External service boundary · All physical members and parallel paths to be mapped._Connected within approved operating scope_ Normal state Authorisation Module action Business effect Failure behaviour Review workspace crossing · All physical members and parallel paths to be mapped._Disconnected by default_ Normal state Disconnected by default Authorisation Module action Business effect Failure behaviour Secondary site route · All physical members and parallel paths to be mapped._Connected within approved operating scope_ Normal state Authorisation Module action Business effect Failure behaviour Equipment integration conduit · All physical members and parallel paths to be mapped._Connected within approved operating scope_ Normal state Authorisation Module action Business effect Failure behaviour Internet service crossing · All physical members and parallel paths to be mapped._Connected within approved operating scope_ Normal state Authorisation Module action Business effect Failure behaviour Operational runbook ## Who does what, and when. What happens under normal conditions, during approved work, when an incident is detected and when connections are restored. Stage What happens Who decides On record _1_Normal operation **Agreed states held** Withdraw selected autonomous network connections while assessing local behaviour separately. Each selected connection sits at its agreed normal state.Anchor Set in the Plan, signed off by your operational, security and continuity leads. Connection states, continuously. _2_Approved work **Booked, bounded access** Isolate groups registered conduits; Fracture withdraws each authorised connection; Execute applies the action.Validate Lock The named owner approves each opening in advance. Request, approval, opening and closure. _3_Incident detected **Act on the alert** Your security tools raise an alert. The agreed action starts out of band, without depending on the network under attack.Execute Pre-authorised in the Plan. The incident owner is told at once. The alert and the action taken. _4_Controlled response **Change the agreed crossings** Withdraw selected autonomous network connections while assessing local behaviour separately.Fracture Isolate Automatic only for the crossings you agreed. Anything else needs the incident owner. Each action, timestamped. _5_Reconnection **Check before reopening** Restoring a physical path is a new operating decision. Review the current system state, outstanding risks and authority before reconnecting. The operational owner authorises each reconnection. Each check and each reconnection. Engineering and integration ## Fit the control around your existing environment. **Map the complete boundary**Confirm cabling, redundant links and alternate routes. A selected physical cut does not remove paths outside its scope. **Agree an independent command route**Confirm the available command methods for the selected hardware. Command delivery can be affected by coverage, roaming and handshakes. **Test the effect, not just the command**Verify the observed link state, service dependencies and failure behaviour in an agreed test window. Testing and evidence ## Prove the selected connection before relying on it. Agree acceptance criteria with the service owner, then retain the observed results. **Normal service**Check the agreed service state and alternate paths. **Controlled change**Verify approved opening, closure and the operational impact. **Recovery and failure**Test reconnection checks, loss of power and loss of the command route. Resilience and recovery ## Offline Secure Storage® OSS protects stored business data, recovery copies and retained evidence through physical disconnection. It is a separate storage service, not a Control module or a network containment function. Control by Firevault governs selected physical connections. Existing detection tools and authorised operators decide when to act. OSS does not detect incidents, command Control or replace operational safety procedures. Explore Offline Secure Storage (https://fire-vault.com/offline-secure-storage) Frameworks and limitations ## Support your obligations. Keep the boundaries clear. **What this addresses**Withdraw selected autonomous network connections while assessing local behaviour separately. **What it does not replace**Local execution, model shutdown, physical stopping and unregistered communication channels. **Evidence agreed for the deployment**Specify the requests, approvals, commands, observed states and test results to retain. Logging capability and retention depend on the selected design. Build your Control Plan ## Start with the connections you would cut first. Use this draft register to discuss connection scope and unresolved operating decisions. It is a discovery aid, not an approved deployment configuration. Questions worth asking ## Before you rely on CP-19. Practical questions for the people who own these connections. Not by assumption. Map dependencies and agree the acceptable service impact with the operational owner before selecting a path. Your next step ## Take the next step with autonomous system intervention. Book a briefing (https://fire-vault.com/demo) Prefer to talk first? Speak to the team: https://fire-vault.com/contact Book a briefing: https://fire-vault.com/demo Speak to the team: https://fire-vault.com/contact ## Structured data ```json [ { "@context": "https://schema.org", "@type": "Organization", "@id": "https://fire-vault.com/#organization", "name": "Firevault", "legalName": "Firevault Limited", "url": "https://fire-vault.com", "logo": { "@type": "ImageObject", "url": "https://fire-vault.com/logo.png", "width": 200, "height": 60 }, "foundingDate": "2025-03", "description": "Firevault is a UK cyber resilience company. Data protection and storage through Offline Secure Storage. Network evolution and rapid protection through Control.", "address": { "@type": "PostalAddress", "addressCountry": "GB", "addressLocality": "United Kingdom" }, "contactPoint": [ { "@type": "ContactPoint", "contactType": "customer service", "email": "hello@fire-vault.com", "availableLanguage": "English", "areaServed": [ "GB", "EU", "US", "AE" ] }, { "@type": "ContactPoint", "contactType": "sales", "email": "sales@fire-vault.com", "availableLanguage": "English", "areaServed": [ "GB", "EU", "US", "AE" ] } ], "founder": [ { "@type": "Person", "name": "Mark Fermor", "jobTitle": "Founder, CTO and CMO" }, { "@type": "Person", "name": "David Bailey", "jobTitle": "Founder and CEO" } ], "areaServed": [ "United Kingdom", "Europe", "United States", "Middle East" ], "sameAs": [ "https://www.linkedin.com/company/firevault", "https://x.com/firevaultuk" ], "slogan": "Disconnect to Protect", "brand": [ { "@type": "Brand", "name": "Offline Secure Storage" }, { "@type": "Brand", "name": "Control by Firevault" }, { "@type": "Brand", "name": "Firebreak" } ], "knowsAbout": [ "Offline Secure Storage", "Physically disconnected data storage", "Physical Air Gap Data Protection", "Ransomware Protection", "Ransomware recovery", "3-2-1-1-0 backup rule", "AI kill switch", "Operational technology security", "Critical national infrastructure resilience", "Data Sovereignty", "GDPR Compliance", "NIS2 Compliance", "DORA Compliance", "NCSC Cyber Assessment Framework" ] }, { "@context": "https://schema.org", "@type": "WebSite", "@id": "https://fire-vault.com/#website", "name": "Firevault", "alternateName": [ "Firevault", "Firevault UK", "Firevault Limited" ], "url": "https://fire-vault.com", "publisher": { "@id": "https://fire-vault.com/#organization" }, "inLanguage": "en-GB", "description": "Firevault is a UK cyber resilience company. Data protection and storage through Offline Secure Storage. Network evolution and rapid protection through Control.", "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://fire-vault.com/learn?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@context": "https://schema.org", "@type": "WebPage", "@id": "https://fire-vault.com/control-plan/autonomous-system-intervention#webpage", "url": "https://fire-vault.com/control-plan/autonomous-system-intervention", "name": "CP-19 Autonomous System Intervention", "description": "Disconnect the communications of an autonomous system.", "isPartOf": { "@id": "https://fire-vault.com/#website" }, "about": { "@id": "https://fire-vault.com/#organization" }, "primaryImageOfPage": { "@type": "ImageObject", "url": "https://fire-vault.com/images/og/og-base-platform.jpg" }, "inLanguage": "en-GB", "breadcrumb": { "@id": "https://fire-vault.com/control-plan/autonomous-system-intervention#breadcrumb" } }, { "@context": "https://schema.org", "@type": "BreadcrumbList", "@id": "https://fire-vault.com/control-plan/autonomous-system-intervention#breadcrumb", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://fire-vault.com" }, { "@type": "ListItem", "position": 2, "name": "Control Plan", "item": "https://fire-vault.com/control-plan" }, { "@type": "ListItem", "position": 3, "name": "CP-19 Autonomous System Intervention", "item": "https://fire-vault.com/control-plan/autonomous-system-intervention" } ] }, { "@context": "https://schema.org", "@type": "WebPage", "name": "CP-19 Autonomous System Intervention", "description": "Disconnect the communications of an autonomous system.", "url": "https://fire-vault.com/control-plan/autonomous-system-intervention" } ] ```