---
title: "CP-08 AI Connectivity Control | Control by Firevault"
url: https://fire-vault.com/control-plan/control-ai-systems
description: "CP-08 lets an authorised operator withdraw selected network connections used by an AI system, such as tool access, production data paths or external provider…"
lang: en-GB
---

Control Plan **CP-08**AI Connectivity Control

# When an AI system behaves unexpectedly, can you disconnect its reach?

Image: CP-08 AI Connectivity Control Control Plan icon (https://fire-vault.com/__l5e/assets-v1/46daa836-10e3-4e3e-a517-da2778479709/CP-08_ai-connectivity-control.png)

CP-08 lets an authorised operator withdraw selected network connections used by an AI system, such as tool access, production data paths or external provider links.

Book a briefing: https://fire-vault.com/demo
See Control in Action

Plan

CP-08

Purpose

AI Connectivity Control

Selected connections

4

Modules

Validate · Execute · Fracture · Isolate · Relay

Scope

Selected AI tool, data, provider and administration connections recorded in the register.

What is at stake

## Why ai connectivity control matters.

AI systems increasingly connect to tools, data and other services. If one behaves unexpectedly, teams need a clear way to reduce what it can reach without assuming that every function will stop.

**Unexpected tool use**An AI system may call tools or services in ways the owner did not expect.

**Excessive data reach**Standing connections can give an AI service access to more data than its task requires.

**Unclear intervention authority**Teams need to know who can stop selected connections and when.

**Local processing continues**Withdrawing network routes does not necessarily stop a model running locally.

The problem today

## Where you are IP connected today.

CP-08 reviews four 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.

**4**IP-connected paths reviewed

**4**Risks to agree with owners

**5**Control modules applied

1. _Risk 1_**AI tool access path**
   The connection used by the AI system to reach approved tools or services.
   Whenever this path is open over IP, it is a route that can be reached, misused or exploited.
   **Agreed state:** Connected for approved service
2. _Risk 2_**Production data path**
   The route between the AI service and selected production data.
   Whenever this path is open over IP, it is a route that can be reached, misused or exploited.
   **Agreed state:** Connected only where required
3. _Risk 3_**External model provider link**
   The route used to reach an external AI provider.
   Whenever this path is open over IP, it is a route that can be reached, misused or exploited.
   **Agreed state:** Connected for approved use
4. _Risk 4_**Model administration path**
   The route used to administer the AI runtime.
   Whenever this path is open over IP, it is a route that can be reached, misused or exploited.
   **Agreed state:** Disconnected outside approved windows

Matching industry Blueprints

What Firevault changes

## What changes with this Plan.

Withdraw selected AI network connections on an authorised intervention, while recognising that local processing may continue.

| Connection | Agreed normal state | Control action |
| --- | --- | --- |
| AI tool access path | Connected for approved service | Validate checks authority. Execute initiates the action. Fracture withdraws the tool path. |
| Production data path | Connected only where required | Validate checks authority. Execute initiates the action. Fracture withdraws the data path. |
| External model provider link | Connected for approved use | Validate checks authority. Execute initiates the action. Fracture withdraws the provider link. |
| Model administration path | Disconnected outside approved windows | Validate checks the request. Relay opens the path. Fracture withdraws it afterwards. |

CP-08 does not stop local model processing, guarantee safe outputs or control routes outside the approved register. It is not a complete AI shutdown.

Control in Action

## AI Connectivity Control: see the selected path change.

Control in Action

Stage

Before agreed physical control

AI systems increasingly connect to tools, data and other services. If one behaves unexpectedly, teams need a clear way to reduce what it can reach without assuming that every function will stop.**Connected routes require review. Discovery checks your real dependencies.**

**0**reached by the attack

**10**still running

Physical crossings

- AI tool access path _Always connected_
- Production data path _Always connected_
- External model provider link _Always connected_
- Model administration path _Always connected_
- Recovery access (OSS) _Not in place_
1. _VA_**Validate** · 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.

Checks the operator, authority and reason for intervention. Initiates the approved action on the designated AI connection. Physically withdraws the selected connection. Groups agreed runtime uplinks when they must be withdrawn together. Opens approved administration or dataset connections for a limited time.

### CP-08AI Connectivity Control

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 AI network connections on an authorised intervention, while recognising that local processing may continue.

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-08

**CP-07****Security Airlock**A two-stage gateway with independently controlled connections. _Open CP-07_: https://fire-vault.com/control-plan/security-airlock
**CP-09****Controlled Data Transfer**A controlled exchange path between two separate environments. _Open CP-09_: https://fire-vault.com/control-plan/controlled-data-transfer
**CP-06****Controlled 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_: https://fire-vault.com/control-plan/prove-compliance-through-control

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.

AI tool access pathThe connection used by the AI system to reach approved tools or services._Connected for approved service_

Normal state

Connected for approved service

Authorisation

Authorised intervention or an agreed response rule

Module action

Validate checks authority. Execute initiates the action. Fracture withdraws the tool path.

Business effect

Network tool calls on this path stop. Local processing can continue.

Failure behaviour

Behaviour agreed and tested for loss of power or command route.

Production data pathThe route between the AI service and selected production data._Connected only where required_

Normal state

Connected only where required

Authorisation

Authorised intervention

Module action

Validate checks authority. Execute initiates the action. Fracture withdraws the data path.

Business effect

Access to that data source stops through this route.

Failure behaviour

Behaviour agreed with the service owner.

External model provider linkThe route used to reach an external AI provider._Connected for approved use_

Normal state

Connected for approved use

Authorisation

Authorised intervention

Module action

Validate checks authority. Execute initiates the action. Fracture withdraws the provider link.

Business effect

Requests to that provider stop through this route.

Failure behaviour

Model administration pathThe route used to administer the AI runtime._Disconnected outside approved windows_

Normal state

Disconnected outside approved windows

Authorisation

Approved administration request

Module action

Validate checks the request. Relay opens the path. Fracture withdraws it afterwards.

Business effect

Administration uses approved windows.

Failure behaviour

Remains disconnected unless an approved recovery procedure is followed.

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 AI network connections on an authorised intervention, while recognising that local processing may continue. 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**

Validate checks authority. Execute initiates the action. Fracture withdraws the tool path.Validate Relay

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 AI network connections on an authorised intervention, while recognising that local processing may continue.Fracture Isolate

Automatic only for the crossings you agreed. Anything else needs the incident owner.

Each action, timestamped.

_5_Reconnection **Check before reopening**

Review the intervention reason, confirm dependent services and approve reconnection one route at a time.

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 AI network connections on an authorised intervention, while recognising that local processing may continue.

**What it does not replace**CP-08 does not stop local model processing, guarantee safe outputs or control routes outside the approved register. It is not a complete AI shutdown.

**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.

List the tools, data sources and providers your AI system can reach, then choose the first connection an operator should be able to withdraw.

Questions worth asking

## Before you rely on CP-08.

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 ai connectivity control.

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/control-ai-systems#webpage",
    "url": "https://fire-vault.com/control-plan/control-ai-systems",
    "name": "CP-08 AI Connectivity Control",
    "description": "CP-08 lets an authorised operator withdraw selected network connections used by an AI system, such as tool access, production data paths or external provider…",
    "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/control-ai-systems#breadcrumb"
    }
  },
  {
    "@context": "https://schema.org",
    "@type": "BreadcrumbList",
    "@id": "https://fire-vault.com/control-plan/control-ai-systems#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-08 AI Connectivity Control",
        "item": "https://fire-vault.com/control-plan/control-ai-systems"
      }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "WebPage",
    "name": "CP-08 AI Connectivity Control",
    "description": "CP-08 lets an authorised operator withdraw selected network connections used by an AI system, such as tool access, production data paths or external provider links.",
    "url": "https://fire-vault.com/control-plan/control-ai-systems"
  }
]
```