Firevault, offline secure storage, physically disconnected from the internet
Pricing

Control for supply chain risk

Supply chain risk, governed at the path.

Persistent vendor connections, such as VPNs and remote access tools, are a common entry point for attackers. Control keeps vendor paths physically severed except during approved, time-bound sessions.

  • Always-on vendor VPNs
  • Compromised suppliers
  • Vendors inside production

As featured in

  • TechRadar Pro logo
  • Yahoo Finance logo
  • Channel Insider logo
  • Security Buyer logo
  • SecurityBrief logo

The challenge

Every persistent vendor connection is a route in.

Attackers who compromise a supplier inherit the supplier’s access. If that access is always on, so is the route.

  1. Vendor connections activate only during defined maintenance windows.

  2. Every vendor session requires approval from both the vendor team and internal security.

  3. Vendor activity during active windows is captured on physically disconnected storage.

Challenge 1

Always-on vendor VPNs.

Managed service providers and equipment vendors often hold 24/7 connections into the estates they support.

Answered byScheduled access windows

Challenge 2

Compromised suppliers.

An attacker who compromises a supplier’s management platform can use its connections to reach every customer (MITRE ATT&CK T1195).

Answered byMulti-party session approval

Challenge 3

Vendors inside production.

Third-party sessions often land on networks that also reach production, backups and management systems.

Answered bySession recording

The scenario

Scenario: a managed service provider is compromised.

The vendor path was needed for one patch window a week, and open for the other 167 hours. Step through it, or play it through.

Step 1 of 2

The attack path

A manufacturer’s managed service provider holds a 24/7 VPN into its network.

Attackers compromise the MSP’s management platform and use that VPN to deploy ransomware into the manufacturer’s estate.

The path
Always there
What the attacker needs
A foothold and time

An illustrative scenario.

Windowed
Vendor connections
Two-party
Approval for every session
Recorded
Vendor activity, held offline
Severed
All vendor paths on command

Where Control breaks the chain

How Control breaks a supply chain compromise.

Each module removes something a compromised supplier would otherwise inherit: the standing path, the trust, or the reach beyond the vendor zone.

  1. Physical severFirebreakPhysically opens or closes connection paths to prevent unauthorised access and stop attack progression.
  2. Remove trustUnlinkRemoves persistent connections, live dependencies and inherited trust that keep sensitive assets exposed.
  3. Time-bound pathRelayAllows connectivity only when needed, for a defined purpose, under controlled conditions and for a limited time.
  4. Named accessLockRestricts access through identity, authority, policy, permission and operational controls.
  5. Trigger, act, terminateExecuteInitiates control actions when a policy, approval, schedule, incident state or supervisory override requires it.
  6. Integrity checkValidateChecks whether a request, command or approval should proceed before access, action or transfer is allowed.
  7. Zone boundaryIsolateSeparates systems and networks into controlled zones to reduce lateral movement and enforce trust boundaries.

Explore the Control Blueprints

Capabilities

What you get with every deployment.

Six things Control gives the team, from the first boundary to the audit afterwards.

Supply chain

Scheduled access windows

Vendor connections activate only during defined maintenance windows.

Supply chain

Multi-party session approval

Every vendor session requires approval from both the vendor team and internal security.

Supply chain

Session recording

Vendor activity during active windows is captured on physically disconnected storage.

Supply chain

Fast vendor disconnection

When a supply chain compromise is detected, all vendor paths are physically severed on command.

Supply chain

Vendor zone isolation

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

Supply chain

Vendor compliance evidence

Automated logging that can help support ISO 27001 supplier assessments, NIS2 and SLA evidence.

Adoption guide

From first boundary to routine operation.

Four steps, piloted on one site before it extends across the estate.

  1. 1

    Third-party path audit

    Map every vendor, MSP and software supplier connection into your infrastructure.

  2. 2

    Window and zone design

    Define maintenance windows, vendor zones and multi-party authorisation requirements.

  3. 3

    Pilot with your primary MSP

    Deploy Relay-governed access for your primary managed service provider.

  4. 4

    Full vendor governance

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

Questions

What teams ask first

Through an emergency window: the path opens as a named, time-bound session with approval from the vendor team and internal security, and closes again afterwards.

Yes. Control governs the path the tooling uses, not the tooling itself. Sessions land in a separated vendor zone during the approved window.

Validate checks requests and updates for origin and integrity before they cross, and vendor paths are severed outside approved windows.

All questions

Speak to the team to organise a PoC.

Walk through your blueprint with the Firevault team and scope a proof of concept on your estate. 30 minutes, no sales pitch.