--- title: "CP-09 Protect Maritime and Commercial Shipping… | Firevault" url: https://fire-vault.com/control-blueprints/cp-09 description: "Keep vessel, port and terminal operations separated, with remote access that exists only for an approved voyage or maintenance window." lang: en-GB --- Control Blueprints: https://fire-vault.com/control-blueprints Control Blueprint **CP-09** # Protect Maritime and Commercial Shipping At sea or alongside, supplier access should not become permanent reach into vessel and terminal operations. Discuss this Blueprint: https://fire-vault.com/contact Run the sequence Blueprint **CP-09** Primary modules - Firebreak - Isolate - Validate - Relay - Execute Supporting - Lock - Archive - Transfer Where it fits Commercial vessels, ports and terminals with local control of operational and supplier paths CP-09 Protect Maritime and Commercial Shipping, as drawn _Illustration_ Zone 0 **Shore and remote services**Suppliers, fleet management, satellite, private 5G and port services Boundary 1 - Firebreak - Validate - Relay _Window only_ Closed by default. Opens only for an approved, time-bound request. Zone 1 **Controlled exchange**The only place approved maintenance, updates or cargo data cross Boundary 2 - Isolate - Execute - Lock _Severed_ Operational reach is separated and can be severed locally on signal. Zone 2 **Vessel and terminal operations**Bridge support, vessel OT, cargo handling, cranes, gates and terminal systems Held offline **Crown jewels**Held offline, with the record of each approved window and of what crossed the boundary. _Offline_ **Out-of-band command path**Management Ethernet, cellular SMS or an authenticated API, off the production network. **The sequence**Step through how the modules work together, as the Blueprint sets them out. 1. **1**FirebreakFirebreak holds the routes between shore, vessel and terminal operations closed by default. 2. **2**Validate and RelayValidate checks remote supplier, update and data-exchange requests before Relay opens a time-bound path. 3. **3**Execute, Lock, Archive and TransferExecute can close that path locally, while Lock, Archive and Transfer control authority, preserve the record and govern what crosses the boundary. The pattern ## Separate shore support from operational authority. What it does CP-09 governs the crossings between shore services, controlled exchange and vessel or terminal systems. Support, updates and cargo-data exchange are approved windows. They do not automatically give fleet, satellite or port services continuing access to operational environments. Where it fits For commercial vessels, ports and terminals using remote suppliers, fleet systems, satellite communications or private 5G. The design should reflect who owns the crossing during a voyage, a port call or a maintenance engagement. Who uses it - Maritime - Commercial shipping - Ports and terminals - Logistics - Offshore operations Zone by zone ## How CP-09 protects maritime and commercial shipping. Follow shore and supplier reach through the controlled exchange point to the vessel or terminal operation it is permitted to support. 1. Zone 0 ### Shore and remote services Remote suppliers, fleet services and communications links request a specific support or exchange task; their connectivity is not operational authority. 2. Boundary 1 Window only Validate the request before opening the approved shore-to-operations window. - **Firebreak**Physical sever. Primary in CP-09 - **Validate**Integrity check. Primary in CP-09 - **Relay**Time-bound path. Primary in CP-09 3. Zone 1 ### Controlled exchange Maintenance, updates and cargo information cross here under an explicit engagement, not through unrestricted shore reach. 4. Boundary 2 Severed Keep onward reach to vessel or terminal operations bounded and close the selected route when the local response requires it. - **Isolate**Zone boundary. Primary in CP-09 - **Execute**Trigger, act, terminate. Primary in CP-09 - **Lock**Named access. Supporting in CP-09 5. Zone 2 ### Vessel and terminal operations Bridge-support services, vessel OT, cargo handling, cranes and gates have distinct dependencies that must guide the boundary plan. 6. Offline ### Crown jewels Protect selected operational records and recovery assets separately offline, away from the live shore and supplier paths. Offline Secure Storage® (https://fire-vault.com/offline-secure-storage) Bill of modules ## Firebreak, Isolate, Validate, Relay and Execute lead. Lock, Archive and Transfer support. Primary modules govern the maritime crossing and local response. Supporting modules control authority, retained records and exchanged material. | Module | Layer | In CP-09 | Where it sits | What it does here | | --- | --- | --- | --- | --- | | Firebreak: https://fire-vault.com/control/modules/firebreak | Control the path | Primary | Boundary 1 | Disconnects the selected shore, supplier or communications crossing to vessel and terminal operations. | | Isolate: https://fire-vault.com/control/modules/isolate | Control the path | Primary | Boundary 2 | Separates remote-service reach from the operational maritime environment. | | Validate: https://fire-vault.com/control/modules/validate | Protect the asset | Primary | Boundary 1 | Checks the authority and purpose of a voyage, port-call or maintenance access request. | | Relay: https://fire-vault.com/control/modules/relay | Control the path | Primary | Boundary 1 | Opens a defined maritime support or data-exchange window for the approved task. | | Execute: https://fire-vault.com/control/modules/execute | Control the path | Primary | Boundary 2 | Carries out the local boundary response authorised for the vessel or terminal. | | Lock: https://fire-vault.com/control/modules/lock | Protect the asset | Supporting | Boundary 2 | Restricts the maritime engagement to the permitted operator and role. | | Archive: https://fire-vault.com/control/modules/archive | Protect the asset | Supporting | Across the Blueprint | Retains the designated access and control records for voyage or maintenance review. | | Transfer: https://fire-vault.com/control/modules/transfer | Protect the asset | Supporting | Across the Blueprint | Governs the updates and cargo or operational artefacts allowed across the exchange boundary. | Firebreak® is supplied by Firevault within Control at the selected maritime crossing. Its physical action must follow the vessel or terminal’s approved operational response. Explore Firebreak® (https://fire-vault.com/firebreak) All nine modules: https://fire-vault.com/control Versus the alternatives ## Shore connectivity is not a reason for standing access. Compare the support engagement and local response rather than treating communications availability as permission to reach operational systems. | Question | Detect and respond | Manual shutdown | CP-09 | | --- | --- | --- | --- | | Remote authority | Access policy governs the connected shore account | Local staff decide when to connect the support link | Validate checks the named maritime task and authority | | Voyage or maintenance window | Expiry depends on remote-access arrangements | Staff disconnect at the end of the task | Relay defines the approved operational window | | Operational separation | Network rules govern shore-to-OT reach | One removed link may leave other routes | Isolate bounds the vessel or terminal environment | | Loss of central connectivity | Response depends on the deployed orchestration | Local intervention remains possible | Execute applies the pre-agreed local boundary action | | Exchange material | Updates and cargo data need separate controls | A cable does not distinguish approved artefacts | Transfer governs the permitted exchange | | Operational impact | Monitoring does not determine safe disconnection | Manual removal also needs a dependency assessment | The maritime owner validates which crossing may close | Composes with ## Compose maritime control around the voyage and port. CP-03 governs suppliers, CP-04 defines physical separation and CP-05 adds the process constraints relevant to cargo handling and terminal equipment. - **CP-01** **Stop Kill-Chain Ransomware**Stop ransomware moving, spreading or reaching the crown jewels. _Open CP-01_: https://fire-vault.com/control-blueprints/cp-01 - **CP-02** **Contain Active Breaches**When prevention fails, containment must be physical, immediate and provable. _Open CP-02_: https://fire-vault.com/control-blueprints/cp-02 - **CP-04** **Enforce Physical Segmentation**Segmentation should not just be logical. It should be physically enforceable. _Open CP-04_: https://fire-vault.com/control-blueprints/cp-04 All ten Blueprints: https://fire-vault.com/control-blueprints Questions ## Questions from vessel and terminal teams. The pattern supports pre-agreed local enforcement. Establish the command arrangements and authority available on the vessel or terminal when central orchestration cannot be relied on. Supplier maintenance, fleet management, satellite, private 5G and port-service connections that reach operational environments. Map their actual onward reach rather than treating all communications links as equivalent. Yes, through the controlled exchange appropriate to the task. Validate the authority and govern the material and duration instead of providing unrestricted access to cargo-handling systems. No general assurance is made. The responsible maritime operator must assess dependencies and approve the permitted boundary action. A support link and a safety-critical operational connection are not interchangeable. The named authority in the vessel’s agreed access model. Define how shore suppliers request permission and who can end or extend an engagement locally. The engagement authority, relevant control records and approved exchanged artefacts. Archive supports review, while separately protected recovery assets remain a distinct part of the operational recovery plan. All questions: https://fire-vault.com/learn/faq Disconnect to Protect® ## Keep shore support within its purpose. Tell us which remote services reach your vessels or terminals. We will discuss local authority, exchange windows and the operational boundaries. Discuss this Blueprint: https://fire-vault.com/contact All Blueprints: https://fire-vault.com/control-blueprints Discuss this Blueprint: https://fire-vault.com/contact The sequence 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-blueprints/cp-09#webpage", "url": "https://fire-vault.com/control-blueprints/cp-09", "name": "CP-09 Protect Maritime and Commercial Shipping…", "description": "Keep vessel, port and terminal operations separated, with remote access that exists only for an approved voyage or maintenance window.", "isPartOf": { "@id": "https://fire-vault.com/#website" }, "about": { "@id": "https://fire-vault.com/#organization" }, "primaryImageOfPage": { "@type": "ImageObject", "url": "https://fire-vault.com/assets/og-blueprint-cp-09-Y5UAUzk1.webp" }, "inLanguage": "en-GB", "breadcrumb": { "@id": "https://fire-vault.com/control-blueprints/cp-09#breadcrumb" } }, { "@context": "https://schema.org", "@type": "BreadcrumbList", "@id": "https://fire-vault.com/control-blueprints/cp-09#breadcrumb", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://fire-vault.com" }, { "@type": "ListItem", "position": 2, "name": "Control Blueprints", "item": "https://fire-vault.com/control-blueprints" }, { "@type": "ListItem", "position": 3, "name": "CP-09 Protect Maritime and Commercial Shipping…", "item": "https://fire-vault.com/control-blueprints/cp-09" } ] }, { "@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": "CP-09 Protect Maritime and Commercial Shipping", "url": "https://fire-vault.com/control-blueprints/cp-09", "description": "Keep vessel, port and terminal operations separated, with remote access that exists only for an approved voyage or maintenance window.", "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": "CP-09", "item": "https://fire-vault.com/control-blueprints/cp-09" } ] }, { "@type": "FAQPage", "mainEntity": [ { "@type": "Question", "name": "Does CP-09 require continuous contact with shore security?", "acceptedAnswer": { "@type": "Answer", "text": "The pattern supports pre-agreed local enforcement. Establish the command arrangements and authority available on the vessel or terminal when central orchestration cannot be relied on." } }, { "@type": "Question", "name": "Which remote paths should be reviewed first?", "acceptedAnswer": { "@type": "Answer", "text": "Supplier maintenance, fleet management, satellite, private 5G and port-service connections that reach operational environments. Map their actual onward reach rather than treating all communications links as equivalent." } }, { "@type": "Question", "name": "Can cargo-data exchange remain available?", "acceptedAnswer": { "@type": "Answer", "text": "Yes, through the controlled exchange appropriate to the task. Validate the authority and govern the material and duration instead of providing unrestricted access to cargo-handling systems." } }, { "@type": "Question", "name": "Is it safe to disconnect navigation-related equipment?", "acceptedAnswer": { "@type": "Answer", "text": "No general assurance is made. The responsible maritime operator must assess dependencies and approve the permitted boundary action. A support link and a safety-critical operational connection are not interchangeable." } }, { "@type": "Question", "name": "Who authorises access during a voyage?", "acceptedAnswer": { "@type": "Answer", "text": "The named authority in the vessel’s agreed access model. Define how shore suppliers request permission and who can end or extend an engagement locally." } }, { "@type": "Question", "name": "What should be retained after remote maintenance?", "acceptedAnswer": { "@type": "Answer", "text": "The engagement authority, relevant control records and approved exchanged artefacts. Archive supports review, while separately protected recovery assets remain a distinct part of the operational recovery plan." } } ] } ] } ] ```