--- title: "CP-16 Remote Site Isolation | Control by Firevault" url: https://fire-vault.com/control-plan/remote-site-isolation description: "Disconnect the communications link to a remote facility." lang: en-GB --- Control Plan **CP-16**Remote Site Isolation Proposed Control Plan. Subject to technical and publication approval. # One remote site is affected. Which connections should you withdraw? Image: CP-16 Remote Site Isolation Control Plan icon (https://fire-vault.com/__l5e/assets-v1/53528939-c0c1-4a94-b7bf-db0f96a490e9/CP-16_remote-site-isolation.png) Disconnect the communications link to a remote facility. Book a briefing: https://fire-vault.com/demo See Control in Action Plan CP-16 Purpose Remote Site Isolation Selected connections 8 Modules Fracture · Isolate · Relay · Execute · Validate Scope The assessed remote facility communications boundary, support, management and alternate conduits. What is at stake ## Why remote site isolation matters. Assess the remote facility communications boundary with the remote site operations owner. Record dependencies, approval conditions and verification evidence before a physical connection is changed. **Unnecessary exposure**The remote site communications links can remain available beyond the approved need. **Service impact**Central services may become unavailable. Local operation must be assessed rather than assumed. **Unclear authority**Name the remote site operations owner and the conditions for a connection change. **Unverified closure**Check the observed state of the remote site communications links, including parallel routes. The problem today ## Where you are IP connected today. CP-16 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 **5**Control modules applied 1. _Risk 1_**Primary WAN** Physical hand-off between the remote facility and central network. Whenever this path is open over IP, it is a route that can be reached, misused or exploited. **Agreed state:** Connected 2. _Risk 2_**Supplier support** Support gateway into the facility. Whenever this path is open over IP, it is a route that can be reached, misused or exploited. **Agreed state:** Disconnected by default 3. _Risk 3_**Site management** Dedicated facility management connection. 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_**Central service path** Central network to shared facility services. Whenever this path is open over IP, it is a route that can be reached, misused or exploited. **Agreed state:** Connected 5. _Risk 5_**Exchange connection** Approved site data exchange route. 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 WAN** Backup carrier hand-off and SD-WAN underlay. Whenever this path is open over IP, it is a route that can be reached, misused or exploited. **Agreed state:** Connected 7. _Risk 7_**Cellular gateway** Independent mobile router or wireless bridge. Whenever this path is open over IP, it is a route that can be reached, misused or exploited. **Agreed state:** To assess 8. _Risk 8_**Local internet edge** Facility internet gateway independent of central WAN. Whenever this path is open over IP, it is a route that can be reached, misused or exploited. **Agreed state:** Connected Matching industry Blueprints BP-01 · utilities water (https://fire-vault.com/control-blueprint/utilities-water)BP-06 · telecommunications (https://fire-vault.com/control-blueprint/telecommunications)BP-13 · construction (https://fire-vault.com/control-blueprint/construction)BP-14 · critical infrastructure (https://fire-vault.com/control-blueprint/critical-infrastructure)BP-17 · retail (https://fire-vault.com/control-blueprint/retail)BP-18 · utilities (https://fire-vault.com/control-blueprint/utilities)BP-20 · utilities renewables (https://fire-vault.com/control-blueprint/utilities-renewables) What Firevault changes ## What changes with this Plan. Keep local facility services within the defined physical boundary. | Connection | Agreed normal state | Control action | | --- | --- | --- | | Primary WAN | Connected | Fracture withdraws the authorised connection. | | Supplier support | Disconnected by default | Relay opens a time-bound window; Validate checks approval. | | Site management | Disconnected by default | Relay governs approved access; Fracture withdraws it. | | Central service path | Connected | Fracture withdraws the selected path. | | Exchange connection | Disconnected by default | Transfer governs what moves; Relay limits the window. | | Secondary WAN | Connected | Isolate operates both site conduits as a group. | | Cellular gateway | To assess | Unlink removes persistent dependencies that bypass the control. | | Local internet edge | Connected | Fracture withdraws the selected edge connection. | Detection, malware removal, device radios and safety-system design. Stored data protection is scoped separately. Control in Action ## Remote Site Isolation: see the selected path change. Control in Action Stage Before agreed physical control Assess the remote facility communications boundary with the remote site operations owner. Record dependencies, approval conditions and verification evidence before a physical connection is changed.**Connected routes require review. Discovery checks your real dependencies.** **0**reached by the attack **10**still running Physical crossings - Primary WAN _Always connected_ - Supplier support _Always connected_ - Site management _Always connected_ - Central service path _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-16: group C1 and C6, and any other assessed bypass. In CP-16: withdraw the selected facility hand-off. In CP-16: apply only the operationally approved boundary action. ### CP-16Remote Site Isolation 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 #### Keep local facility services within the defined physical boundary. Primary modules: Fracture, Isolate, Relay, Execute and Validate. 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-16 **CP-15 · Proposed****Operational Technology Protection**Industrial controllers behind a physical network boundary. _Open CP-15_: https://fire-vault.com/control-plan/operational-technology-protection **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 **CP-14 · Proposed****Compromised Device Isolation**Physically isolate one affected device from the network. _Open CP-14_: https://fire-vault.com/control-plan/compromised-device-isolation 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. Primary WANPhysical hand-off between the remote facility and central network._Connected_ Normal state Connected Authorisation Tier 2Site and incident owner approval Module action Fracture withdraws the authorised connection. Business effect Central applications become unreachable from the site. Failure behaviour Assessed and tested with operations Supplier supportSupport gateway into the facility._Disconnected by default_ Normal state Disconnected by default Authorisation Tier 2Approved support request Module action Relay opens a time-bound window; Validate checks approval. Business effect Remote supplier sessions are unavailable outside the window. Failure behaviour Assessed and tested with operations Site managementDedicated facility management connection._Disconnected by default_ Normal state Disconnected by default Authorisation Tier 2Named engineering work Module action Relay governs approved access; Fracture withdraws it. Business effect Remote administration pauses. Failure behaviour Assessed and tested with operations Central service pathCentral network to shared facility services._Connected_ Normal state Connected Authorisation Tier 2Joint service impact decision Module action Fracture withdraws the selected path. Business effect Shared services are lost; local fallback needs testing. Failure behaviour Assessed and tested with operations Exchange connectionApproved site data exchange route._Disconnected by default_ Normal state Disconnected by default Authorisation Tier 2Approved exchange purpose Module action Transfer governs what moves; Relay limits the window. Business effect Data queues and reconciliation require local procedures. Failure behaviour Assessed and tested with operations Secondary WANBackup carrier hand-off and SD-WAN underlay._Connected_ Normal state Connected Authorisation Tier 2Same approval as C1 Module action Isolate operates both site conduits as a group. Business effect Automatic carrier failover cannot bypass the grouped action. Failure behaviour Assessed and tested with operations Cellular gatewayIndependent mobile router or wireless bridge._To assess_ Normal state To assess Authorisation Tier 2Site survey and authority review Module action Unlink removes persistent dependencies that bypass the control. Business effect Device-level cellular radios require separate controls. Failure behaviour Assessed and tested with operations Local internet edgeFacility internet gateway independent of central WAN._Connected_ Normal state Connected Authorisation Tier 2Site and service owner approval Module action Fracture withdraws the selected edge connection. Business effect Cloud access may fail even when local applications continue. Failure behaviour Assessed and tested with operations 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** Keep local facility services within the defined physical boundary. Each selected connection sits at its agreed normal state. Set in the Plan, signed off by your operational, security and continuity leads. Connection states, continuously. _2_Approved work **Booked, bounded access** Fracture withdraws the authorised connection.Relay Validate 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** Keep local facility services within the defined physical boundary.Fracture Isolate Automatic only for the crossings you agreed. Anything else needs the incident owner. Each action, timestamped. _5_Reconnection **Check before reopening** 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**Keep local facility services within the defined physical boundary. **What it does not replace**Detection, malware removal, device radios and safety-system design. Stored data protection is scoped separately. **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. Which routes cross the remote facility communications boundary? Which dependencies fail when they are withdrawn? Who can approve the local operating state? Use the draft register to prepare a review, not as deployment approval. Questions worth asking ## Before you rely on CP-16. 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 remote site isolation. 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/remote-site-isolation#webpage", "url": "https://fire-vault.com/control-plan/remote-site-isolation", "name": "CP-16 Remote Site Isolation", "description": "Disconnect the communications link to a remote facility.", "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/remote-site-isolation#breadcrumb" } }, { "@context": "https://schema.org", "@type": "BreadcrumbList", "@id": "https://fire-vault.com/control-plan/remote-site-isolation#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-16 Remote Site Isolation", "item": "https://fire-vault.com/control-plan/remote-site-isolation" } ] }, { "@context": "https://schema.org", "@type": "WebPage", "name": "CP-16 Remote Site Isolation", "description": "Disconnect the communications link to a remote facility.", "url": "https://fire-vault.com/control-plan/remote-site-isolation" } ] ```