--- title: "Control Transfer Module: controlled data | Firevault" url: https://fire-vault.com/control-module/transfer description: "Transfer hands custody across network boundaries with dual approval and full chain of custody, so movement happens only through authorised paths." lang: en-GB --- **FV-09 Transfer**Control 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: https://fire-vault.com/demo See it in action Image: Transfer module icon (https://fire-vault.com/__l5e/assets-v1/74c9558c-a9c7-46db-934d-2ee953d77f45/transfer-icon.png) **Transfer**Protect 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. 1. Nightly**Backups copy across.** A share between production and recovery is open so the job can run. 2. One night**Production is encrypted.** Ransomware finds the same share. 3. Next morning**The 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. 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 1. Step 1**Approve** Agree what may move, from where, to where. 2. Step 2**Open** The path opens in one direction, for a defined window. 3. Step 3**Move and verify** The data moves and the transfer is checked. 4. Step 4**Close 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. ### 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. - CP-18**Data Exfiltration Interruption**_Interrupt outbound paths at a physical boundary._: https://fire-vault.com/control-plan/data-exfiltration-interruption - 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._: https://fire-vault.com/control-plan/prove-compliance-through-control - CP-03**Third-Party Access Control**_Supplier and vendor paths that exist only for approved work, in a defined window._: https://fire-vault.com/control-plan/control-third-party-access - **Control Plans**Twenty Plans, each solving one problem. All Control Plans (https://fire-vault.com/control-plans) - **Control Blueprints**Industry solutions that combine Plans. All Control Blueprints (https://fire-vault.com/control-blueprints) - **Fracture**Physically disconnect a connection. See Fracture (https://fire-vault.com/control-module/fracture) - **Isolate**Hold zones apart by design. See Isolate (https://fire-vault.com/control-module/isolate) Questions ## What network and security teams ask. Want to see it on real hardware? We will show you. Book a Control demo: https://fire-vault.com/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. Firevault home (https://fire-vault.com/) Offline Secure Storage® and Control. A UK cyber resilience company. Data protection and storage through Offline Secure Storage®. Network evolution and rapid protection through Control. Firevault on LinkedIn: https://www.linkedin.com/company/firevault-limited Firevault on Facebook: https://www.facebook.com/Firevaultltd/ Firevault on YouTube: https://www.youtube.com/@Firevault-ltd Verify Firevault Cyber Essentials and Cyber Essentials Plus certification on the NCSC register: https://registry.blockmarktech.com/certificates/ © 2026 Firevault Limited Company No. 16320803 VAT No. 490 8551 64 Registered in England and Wales ## 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-module/transfer#webpage", "url": "https://fire-vault.com/control-module/transfer", "name": "Control Transfer Module: controlled data", "description": "Transfer hands custody across network boundaries with dual approval and full chain of custody, so movement happens only through authorised paths.", "isPartOf": { "@id": "https://fire-vault.com/#website" }, "about": { "@id": "https://fire-vault.com/#organization" }, "primaryImageOfPage": { "@type": "ImageObject", "url": "https://fire-vault.com/__l5e/assets-v1/ac3f61c1-0ea6-4e48-b896-1514702fb207/og-control-transfer.webp" }, "inLanguage": "en-GB", "breadcrumb": { "@id": "https://fire-vault.com/control-module/transfer#breadcrumb" } }, { "@context": "https://schema.org", "@type": "BreadcrumbList", "@id": "https://fire-vault.com/control-module/transfer#breadcrumb", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://fire-vault.com" }, { "@type": "ListItem", "position": 2, "name": "Control Module", "item": "https://fire-vault.com/control-module" }, { "@type": "ListItem", "position": 3, "name": "Control Transfer Module: controlled data", "item": "https://fire-vault.com/control-module/transfer" } ] }, { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://fire-vault.com/#org", "name": "Firevault", "legalName": "Firevault Limited", "url": "https://fire-vault.com/", "identifier": "16320803", "sameAs": [ "https://www.linkedin.com/company/firevault-limited", "https://www.facebook.com/Firevaultltd/", "https://www.youtube.com/@Firevault-ltd" ] }, { "@type": "WebPage", "name": "FV-Transfer: Movement only along paths that were approved", "url": "https://fire-vault.com/control-module/transfer", "description": "Transfer governs how sensitive assets move into, out of or between protected environments. The path is approved before the movement, the movement is recorded as it happens, and the destination is one that was always intended.", "publisher": { "@id": "https://fire-vault.com/#org" } }, { "@type": "BreadcrumbList", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://fire-vault.com/" }, { "@type": "ListItem", "position": 2, "name": "FV-Transfer", "item": "https://fire-vault.com/control-module/transfer" } ] }, { "@type": "FAQPage", "mainEntity": [ { "@type": "Question", "name": "Is Transfer a data loss prevention tool?", "acceptedAnswer": { "@type": "Answer", "text": "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." } }, { "@type": "Question", "name": "What if a destination is not approved?", "acceptedAnswer": { "@type": "Answer", "text": "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." } }, { "@type": "Question", "name": "Can Transfer be used for one-off, ad-hoc movements?", "acceptedAnswer": { "@type": "Answer", "text": "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." } }, { "@type": "Question", "name": "How does Transfer relate to Anchor?", "acceptedAnswer": { "@type": "Answer", "text": "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." } } ] } ] } ] ```