--- title: "BP-16 Public Sector | Control by Firevault" url: https://fire-vault.com/control-blueprint/public-sector description: "Public sector organisations connect citizen-facing services with sensitive records, shared platforms and, where applicable, classified environments. Control…" lang: en-GB --- BP-16 · Industry Blueprint · Public Sector # Public services depend on connections. Not all need to stay open. Image: BP-16 Public Sector Control Blueprint icon (https://fire-vault.com/__l5e/assets-v1/1ea99bfd-9c30-44f7-992b-645d9f86e46d/BP-16_public-sector.png) Public sector organisations connect citizen-facing services with sensitive records, shared platforms and, where applicable, classified environments. Control introduces physical control at selected boundaries, designed around service continuity and information handling requirements. Book a briefing: https://fire-vault.com/demo Explore the Control Plans - A supplier needs a scoped support session for a citizen service without standing access to unrelated statutory records. Review the named support and cross-zone boundaries; operationally required links are not assumed disconnectable. - Reference design for adaptation with the service owner, not a validated deployment. Confirm complete boundary coverage, operational dependencies and the consequences of opening or closing each selected path. - 3 matching Control Plans. Offline Secure Storage® is separate. - Control does not replace information classification, identity and access management, service continuity planning, monitoring or statutory responsibilities. Changing connectivity does not establish a safe process state, stop local execution or guarantee service restoration. The industry reality ## Public Sector: the connections your operation relies on. Local and central government environments may combine legacy systems, shared services and information with different access requirements. Carefully mapped boundaries can inform where physical control may be appropriate. **Citizen access**Disruption to digital services may affect residents and public-facing operations. **Sensitive records**Citizen and case records require access consistent with institutional duties. **Interdependency**Shared services and supplier links may connect otherwise distinct organisations. **Service restoration**Teams need defined procedures for response and restoration of key services. What needs protecting ## The service, systems and people behind the connections. A supplier needs a scoped support session for a citizen service without standing access to unrelated statutory records. Review the named support and cross-zone boundaries; operationally required links are not assumed disconnectable. **Supplier pathways**Which supplier routes remain open beyond authorised support activity? **Shared services**Could a connection create unintended dependencies between departments or authorities? **Service continuity**Which paths must remain available for statutory or essential public services? Threats and failure scenarios ## Situations to plan for, before the next incident. A supplier needs a scoped support session for a citizen service without standing access to unrelated statutory records. Control acts on selected physical connections, not every connection in the environment. **Scoped support for Public Sector**A supplier needs a scoped support session for a citizen service without standing access to unrelated statutory records. The owner authorises the selected route and its closing conditions. **Review an affected boundary**Review an affected administrative route during a ransomware incident; essential services and records access need agreed continuity arrangements. **CP-01: agree the connection and authority**Review an affected administrative route during a ransomware incident; essential services and records access need agreed continuity arrangements. Use CP-01 only where its scope and approval requirements fit this connection. Industry architecture ## Illustrative sector connections. Illustrative sector connection Stage Without Control: the selected routes remain open. Modules in this Blueprint Validate: https://fire-vault.com/control-module/validate Relay: https://fire-vault.com/control-module/relay Lock: https://fire-vault.com/control-module/lock Execute: https://fire-vault.com/control-module/execute Fracture: https://fire-vault.com/control-module/fracture Isolate: https://fire-vault.com/control-module/isolate Unlink: https://fire-vault.com/control-module/unlink Shown when the agreed Control response is selected. An illustrative ransomware event starts in a connected system and follows the open routes shown here. This is a connection model, not a prediction of a real attack.**The open connections allow movement in this simplified model. Actual exposure depends on your environment and existing defences.** Selected connection states - Supplier support to citizen-service administration _Always connected_ - Public-facing services to records administration _Always connected_ - Essential public service to required core systems _Always connected_ - Department support to shared-services management _Always connected_ - Recovery access (OSS) _Disconnected_ 1. _!_**Illustrative threat starts at** · Public services 2. _+_**Modelled movement to** · Suppliers, Identity 3. _+_**Modelled movement to** · Approved access, Corporate IT 4. _+_**Modelled movement to** · Supporting service, Staff services, Citizen data 5. _+_**Modelled movement to** · Protected service, Shared platforms This model only shows the selected routes. An interrupted route does not remove an existing compromise or protect unmodelled paths. Your security tools detect the event; the agreed Control design governs the response. Offline Secure Storage® holds copies separately; it is not a Control module. Recommended industry Blueprint ## Our recommended Blueprint for Public Sector. Start with these connections Supplier support to citizen-service administration; Public-facing services to records administration Agree how access works Open only for the authorised support task; close under agreed completion conditions Plan the response Change only the selected boundary after the service owner approves the impact Refine this recommendation with public-service owners, shared-service engineering and security leads. Offline Secure Storage® can hold recovery copies separately; it is not a Control module. 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 Operational scenarios ## Who decides, what changes, and what is checked. Agree responsibility and service dependencies before relying on a controlled connection. 1. **Normal operation** Public sector organisations connect citizen-facing services with sensitive records, shared platforms and, where applicable, classified environments. Control introduces physical control at selected boundaries, designed around service continuity and information handling requirements. 2. **Approved work** A supplier needs a scoped support session for a citizen service without standing access to unrelated statutory records. The owner authorises the selected route and its closing conditions. 3. **Incident response** A supplier needs a scoped support session for a citizen service without standing access to unrelated statutory records. Control acts on selected physical connections, not every connection in the environment. 4. **Reconnection** The owner reviews service dependencies and security checks, authorises reconnection and verifies the observed result. Evidence is retained only through the specified supporting systems. Control does not replace information classification, identity and access management, service continuity planning, monitoring or statutory responsibilities. Changing connectivity does not establish a safe process state, stop local execution or guarantee service restoration. 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. Offline Secure Storage (OSS) is separate from Control. If selected, it can hold retained copies of configurations, records or recovery material. Collection, completeness and recovery readiness depend on the supporting tools, retention design and tested recovery procedures. Explore Offline Secure Storage (https://fire-vault.com/offline-secure-storage) Standards and governance ## Support your obligations. Keep the boundaries clear. Alignment may be assessed against the NCSC Cyber Assessment Framework (CAF) and GovAssure where applicable; no certification or compliance outcome is implied. Any assessment needs deployment-specific scope and evidence; this Blueprint provides no certification, complete audit trail or guaranteed response time. **What this addresses**A supplier needs a scoped support session for a citizen service without standing access to unrelated statutory records. Control acts on selected physical connections, not every connection in the environment. **What it does not replace**Control does not replace information classification, identity and access management, service continuity planning, monitoring or statutory responsibilities. Changing connectivity does not establish a safe process state, stop local execution or guarantee service restoration. **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. Detection and the decision to act belong to the operational owner and supporting security systems. Identity, approval workflow, session expiry and evidence collection require specified integrations. Execute initiates an approved action; Fracture physically disconnects the selected path through Firebreak hardware. Confirm the observed connection state separately. Anchor keeps critical assets within defined physical connection boundaries; it does not collect or retain records. Transfer governs a designated exchange path, not content inspection or de-identification. Deployment and proof of concept ## Start with one boundary. Test it. Then expand. Review the first selected connection with public-service owners, shared-service engineering and security leads, agree who can authorise a change and test the service impact. 1. **Map the complete boundary** Confirm cabling, redundant links and alternate routes. A selected physical cut does not remove paths outside its scope. 2. **Agree an independent command route** Confirm the available command methods for the selected hardware. Command delivery can be affected by coverage, roaming and handshakes. 3. **Test the effect, not just the command** Verify the observed link state, service dependencies and failure behaviour in an agreed test window. Plan your first route ## Start with the route you would close first. Outcomes ## What changes, and how you will verify it. Judge the Blueprint on agreed, observed outcomes. **Supplier support to citizen-service administration**Open only for the authorised support task; close under agreed completion conditions. Agree identity checks, approval, session closure and observed-state checks **Public-facing services to records administration**Change only the selected boundary after the service owner approves the impact. Map alternate routes and preserve services outside the selected scope **Essential public service to required core systems**Not assumed disconnectable. Safety and continuity owners must assess this dependency separately Questions worth asking ## Before you rely on BP-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 public sector. 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-blueprint/public-sector#webpage", "url": "https://fire-vault.com/control-blueprint/public-sector", "name": "BP-16 Public Sector", "description": "Public sector organisations connect citizen-facing services with sensitive records, shared platforms and, where applicable, classified environments. Control…", "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-blueprint/public-sector#breadcrumb" } }, { "@context": "https://schema.org", "@type": "BreadcrumbList", "@id": "https://fire-vault.com/control-blueprint/public-sector#breadcrumb", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://fire-vault.com" }, { "@type": "ListItem", "position": 2, "name": "Control Blueprint", "item": "https://fire-vault.com/control-blueprint" }, { "@type": "ListItem", "position": 3, "name": "BP-16 Public Sector", "item": "https://fire-vault.com/control-blueprint/public-sector" } ] }, { "@context": "https://schema.org", "@type": "WebPage", "name": "BP-16 Public Sector", "description": "Public sector organisations connect citizen-facing services with sensitive records, shared platforms and, where applicable, classified environments. Control introduces physical control at selected boundaries, designed around service continuity and information handling requirements.", "url": "https://fire-vault.com/control-blueprint/public-sector" } ] ```