Recent Breaches
Breaches
View All →
Threat Response

Eliminate Supply Chain Risk Through Physical Path Governance

Supply chain attacks exploit the persistent connections that organisations maintain with vendors, managed service providers, and software suppliers. When these paths are physically severed between active sessions, the attack vector ceases to exist.

Back to Control
Control

Threat Response

Every vendor connection is a doorway into your organisation. If that doorway remains open when no one is walking through it, you are inviting risk without gaining value.

62%

Of breaches originate through third-party access

Zero

Persistent vendor paths outside maintenance windows

100%

Third-party sessions recorded on tamper-proof storage

4.5x

Faster containment when vendor paths are physically severed

The Threat

Third-party connections are the most exploited entry point.

Persistent Vendor Access

Managed service providers and equipment vendors maintain always-on VPN connections and remote access tools. These paths remain active 24/7, regardless of whether maintenance is being performed.

Trust Chain Exploitation

Attackers compromise a vendor with weaker security and use their legitimate access to pivot into the target organisation. The connection is trusted, the credentials are valid, and the activity appears routine.

Software Supply Chain

Compromised software updates delivered through trusted channels bypass perimeter security entirely. The malicious payload arrives through the same path as legitimate updates.

The Scenario

Scenario: Managed Service Provider Compromise

A mid-size manufacturer uses a managed IT service provider for patch management and monitoring. The MSP maintains a persistent VPN connection to the manufacturer's network for 24/7 support. Attackers compromise the MSP's RMM platform and use the existing VPN connection to deploy ransomware across all of the MSP's clients simultaneously. With Firevault Control, the MSP's access path is physically severed outside scheduled maintenance windows. The Relay module activates the connection for a four-hour patch window each Tuesday, with all activity recorded. When the MSP is compromised on a Thursday evening, there is no path for the attackers to traverse.

"Our MSP had a VPN into our network that was active 168 hours a week. They used it for about 6 hours. That left 162 hours where an attacker had a trusted path into our core infrastructure."

Supply chain attack

How Control contains a trusted-vendor compromise.

Supply chain attacks turn a trusted maintenance route into a breach path. Firevault Control treats vendor access as a temporary, governed event rather than a standing trust, so a compromised supplier cannot ride straight into production.

Mapped to MITRE ATT&CK T1195 Supply Chain Compromise, ENISA Threat Landscape for Supply Chain Attacks and NCSC supply chain guidance.

  1. ST 01

    Vendor Compromise

    T1195

    ◤ Attacker

    Attackers breach a software vendor, MSP or update server that customers already trust.

    ◢ Control breaks it

    Vendor reach into the protected zone is severed by default. There is no permanent trust to ride.

    FirebreakUnlink
    ✕ Break here
  2. ST 02

    Trusted Delivery

    T1078.004

    ◤ Attacker

    Pushes a tainted update or piggy-backs on a legitimate support session into customer environments.

    ◢ Control breaks it

    Maintenance windows open only as time-bound Relay sessions. The connection closes on schedule, every time.

    RelayLock
    ✕ Break here
  3. ST 03

    Execution in Production

    TA0002

    ◤ Attacker

    Runs the malicious payload against production assets, often with privileges granted to the vendor.

    ◢ Control breaks it

    Vendor-initiated changes are routed through Execute with multi-party approval and Validate before they reach the asset.

    ExecuteValidate
    ✕ Break here
  4. ST 04

    Onward Movement

    TA0008

    ◤ Attacker

    Pivots from the vendor-managed system into the wider estate.

    ◢ Control breaks it

    Isolate enforces the zone boundary. The compromised system cannot reach into adjacent zones without a fresh, approved path.

    IsolateFirebreak

Outcome · outcome block

A compromised vendor reaches only what the time-bound session allowed, for only as long as it was open. The wider estate stays out of reach.

Modules & symbols

FirebreakPhysical sever
UnlinkRemove trust
RelayTime-bound path
LockNamed access
ExecuteApproved action
ValidateIntegrity check
IsolateZone boundary
Break hereChain severed by Firevault
Attacker stepMITRE ATT&CK tactic

Featured In

TechRadar ProSecurity BuyerYahoo FinanceSecurityBriefChannel Insider

Key Capabilities

Scheduled Access Windows

Vendor connections activate only during defined maintenance windows. Between windows, the physical path does not exist and cannot be established remotely.

Multi-Party Session Approval

Every vendor session requires approval from both the vendor team and internal security before the physical path is activated.

Complete Session Recording

All vendor activity during active windows is captured on physically disconnected storage that neither the vendor nor an attacker can access or modify.

Instant Vendor Disconnection

When a supply chain compromise is detected, all vendor paths are physically severed within seconds, regardless of which vendor is affected.

Vendor Zone Isolation

Third-party access is confined to a physically separated zone with no path to production systems, backup infrastructure, or management planes.

Vendor Compliance Evidence

Automated logging provides the evidence required for ISO 27001 supplier assessments, NIS2 supply chain requirements, and contractual SLA compliance.

Demo to Live

Adoption Guide

Step 1

Third-Party Path Audit

Map every vendor, MSP, and software supplier connection into your infrastructure, documenting active hours, data flows, and the systems each path can reach.

Step 2

Window and Zone Design

Define maintenance windows, vendor zones, and multi-party authorisation requirements for each third-party relationship based on operational need and risk profile.

Step 3

Pilot with Primary MSP

Deploy Relay-governed access for your primary managed service provider, testing scheduled windows, emergency access procedures, and session recording.

Step 4

Full Vendor Governance

Extend to all third-party connections with automated window management, vendor zone isolation, and continuous compliance evidence generation.

Step 1

Third-Party Path Audit

Map every vendor, MSP, and software supplier connection into your infrastructure, documenting active hours, data flows, and the systems each path can reach.

Step 2

Window and Zone Design

Define maintenance windows, vendor zones, and multi-party authorisation requirements for each third-party relationship based on operational need and risk profile.

Step 3

Pilot with Primary MSP

Deploy Relay-governed access for your primary managed service provider, testing scheduled windows, emergency access procedures, and session recording.

Step 4

Full Vendor Governance

Extend to all third-party connections with automated window management, vendor zone isolation, and continuous compliance evidence generation.

Questions

Frequently Asked

    Your privacy matters

    We use cookies to keep the site running smoothly and to understand how you use it. You are in control. Privacy Charter · Cookie Policy

    Supply Chain

    Disconnect third-party paths when not in active use, so a supplier compromise cannot become an estate-wide breach. Physical supply-chain control.

    © 2026 Firevault Limited. Disconnect to Protect®