Is Transfer a data loss prevention tool?

It governs sanctioned movement rather than watching for unsanctioned movement. Sensitive assets move only along approved paths, to explicit destinations, with each movement validated first and recorded through Anchor.

What if a destination is not approved?

The movement does not happen along that route. Destinations are agreed in advance for each movement category, and Validate checks the request before the asset moves.

Can Transfer be used for one-off, ad-hoc movements?

Yes, as a request along an approved path. The point is to retire improvised routes, so even a one-off movement is named, validated and recorded.

How does Transfer relate to Anchor?

Anchor is the preserved store. Transfer is the governed path into and out of it: scheduled, validated movement into the offline vault, and restoration as a Transfer event with quorum approval and a full restore manifest.

FV-09 TransferControl module · Protect the asset

Move sensitive data on a path that closes afterwards.

Transfer controls how sensitive data and digital assets move between environments: through an authorised path, in one agreed direction, for a defined window, with each move verified and recorded. When the move is done, the path closes.

Book a Control demo See it in action

TransferProtect the asset

Module: FV-09 Transfer
Family: Protect the asset
The question it answers: How may this data move, and when?
Path: Authorised, one direction, time-bound
Records: Every transfer, verified

What happens when

The share was there for backups. It carried the ransomware too.

Data has to move between environments. The paths that carry it are often open all the time, in both directions.

NightlyBackups copy across.
A share between production and recovery is open so the job can run.
One nightProduction is encrypted.
Ransomware finds the same share.
Next morningThe recovery copy is affected.
The path that was meant to protect you carried the damage.

An open share moves anything, at any time. Transfer moves what you approved, then closes.

See it in action

One move, two ways. Switch between an always-open share and Transfer.

The same nightly copy from production to recovery.

Always-open shareWith Transfer

An always-open share connects production and recovery, in both directions, all day.

An approved path opens from 02:00 to 03:00 in one direction. The move is verified, then the path closes.

Step by step

Step 1Approve
Agree what may move, from where, to where.
Step 2Open
The path opens in one direction, for a defined window.
Step 3Move and verify
The data moves and the transfer is checked.
Step 4Close and record
The path closes. The transfer is on record.

What Transfer is

Data moves on purpose, not because a path is open.

Transfer treats every movement of sensitive data as an approved event, not a standing connection.

Authorised paths
Only agreed routes, in agreed directions.
Defined windows
The path exists only while the move runs.
Verified and recorded
Each transfer is checked and kept on record.

What it changes

Recovery copies that stay recovery copies.

Transfer does not change what you back up. It changes how long the path for it exists, and in which direction.

Transfer record

Transfer · Production to recoveryVerified, 02:00 to 02:41Closed
Request · Records exportSecond approval requiredPending
Transfer · Supplier deliveryInbound only, verifiedClosed
Review · Transfer routesQuarterlyLogged

Approved moves. Closed paths.

Sensitive data moves only on approved paths
Paths are one direction and time-bound
Each transfer is verified and recorded
No standing share between environments

Where it fits

Fracture, Isolate and Transfer answer different questions.

Fracture and Isolate decide whether connections exist. Transfer does a different job, and most Plans use more than one module.

Module	Fracture	Isolate	Transfer
The question it answers	Must this connection be physically disconnected now?	Which zones should never share a path?	How may this data move, in which direction, and when?
Normal state	Connected, with a crossing ready to be disconnected	Zones held apart, crossings closed by default	Closed, opened only for an approved transfer
When it acts	When a connection becomes dangerous	By design, before anything goes wrong	For each approved move or scheduled copy
What it ends	An incident travelling along a live path	Trust that exists only because systems share a network	Always-open shares between environments
Typical Plans	CP-01, CP-02	CP-04, CP-05, CP-14	CP-18, CP-06, CP-03

Control Plans and Blueprints

Where Transfer does the work.

Transfer governs movement in exfiltration, assurance and third-party Plans. Plans marked Proposed are awaiting technical approval.

Control PlansTwenty Plans, each solving one problem.All Control Plans
Control BlueprintsIndustry solutions that combine Plans.All Control Blueprints
FracturePhysically disconnect a connection.See Fracture
IsolateHold zones apart by design.See Isolate

Questions

What network and security teams ask.

Want to see it on real hardware? We will show you.

Book a Control demo

How is Transfer different from Relay?

Relay opens a path for work, such as maintenance. Transfer governs the movement of data itself, including direction and verification.

How is Transfer different from Fracture and Isolate?

Fracture and Isolate decide whether connections exist. Transfer decides how data may cross the ones that open.

Does Transfer work with our backup tools?

Integration is agreed during scoping. Transfer governs the path; your backup tools still run the copy.

Where are recovery copies held?

In your chosen environment. Offline Secure Storage® is a separate Firevault service for physically offline copies.

Your next step

See a controlled transfer in front of you.

We will take one of your data moves and show it open, verify and close.

Book a Control demo