Firevault, offline secure storage, physically disconnected from the internet
Pricing

Control PlanCP-08AI Connectivity Control

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

CP-08 AI Connectivity Control Control Plan icon

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.

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 useAn AI system may call tools or services in ways the owner did not expect.
Excessive data reachStanding connections can give an AI service access to more data than its task requires.
Unclear intervention authorityTeams need to know who can stop selected connections and when.
Local processing continuesWithdrawing 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.

4IP-connected paths reviewed
4Risks to agree with owners
5Control modules applied
  1. Risk 1AI 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 2Production 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 3External 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 4Model 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.

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

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.

0reached by the attack
10still running

Physical crossings

  • AI tool access pathAlways connected
  • Production data pathAlways connected
  • External model provider linkAlways connected
  • Model administration pathAlways connected
  • Recovery access (OSS)Not in place
  1. VAValidate · 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

Z0Requesting environment
Z1Protected systems
Z2Related 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

Fracture module icon

Fracture

Controls the path

Physically disconnects network paths to prevent unauthorised access, contain threats and stop an attack from progressing.

Physically disconnects network paths to prevent unauthorised access, contain threats and stop an attack from progressing.

Explore the Fracture module

Concept illustration. Select any module to see what it does. Placement is drawn from your own network in discovery.

As featured in

  • TechRadar Pro logo
  • Yahoo Finance logo
  • Channel Insider logo
  • Security Buyer logo
  • SecurityBrief logo

The Control Plan specification

Each selected connection, written down.

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

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
Behaviour agreed with the service owner.
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.

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.

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.

StageWhat happensWho decidesOn record
1Normal operationAgreed 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.

2Approved workBooked, bounded access

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

The named owner approves each opening in advance.

Request, approval, opening and closure.

3Incident detectedAct 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.

4Controlled responseChange the agreed crossings

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

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

Each action, timestamped.

5ReconnectionCheck 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.

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.

Engineering and integration

Fit the control around your existing environment.

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

Map the complete boundaryConfirm cabling, redundant links and alternate routes. A selected physical cut does not remove paths outside its scope.
Agree an independent command routeConfirm the available command methods for the selected hardware. Command delivery can be affected by coverage, roaming and handshakes.
Test the effect, not just the commandVerify 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 serviceCheck the agreed service state and alternate paths.
Controlled changeVerify approved opening, closure and the operational impact.
Recovery and failureTest 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.

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

Explore Offline Secure Storage

Frameworks and limitations

Support your obligations. Keep the boundaries clear.

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.

What this addressesWithdraw selected AI network connections on an authorised intervention, while recognising that local processing may continue.
What it does not replaceCP-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 deploymentSpecify 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.

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

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

Not by assumption. Map dependencies and agree the acceptable service impact with the operational owner before selecting a path.

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

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

Your next step

Take the next step with ai connectivity control.

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

Book a briefing

Prefer to talk first? Speak to the team