A Guide to Controlling Third-Party Access with a Control Blueprint

Share

About this guide

This guide is written for security, infrastructure and risk leaders who need to give third parties access without giving them a permanent doorway. It explains one Control Blueprint, CP-03, in plain terms: the failure it addresses, the Control Modules it uses, how those modules work together, and how a deployment is scoped.

Control by Firevault is a suite of nine purpose-built modules: a set of tools and techniques that give you physical control over the paths into and across your estate. A Control Blueprint is a proven combination of those modules assembled for a specific outcome. This guide covers one blueprint. The Control overview covers the nine modules and the full set of blueprints.

The problem this blueprint addresses

Most supplier access starts as a temporary arrangement and quietly becomes permanent. VPN tunnels, jump hosts and standing accounts remain long after the work finishes, and the organisation inherits the supplier security posture along with its own.

CP-03 at a glance

• Lead layer FIRE+VAULT
• Primary modules Validate, Relay, Lock
• Supporting modules Transfer, Archive, Execute
• Typical sectors Financial services, healthcare, energy and public sector

The primary modules

These modules do the work the blueprint is named for.

• Validate checks the request, command or identity before anything opens.
• Relay opens a controlled, time-bound crossing and closes it again on schedule.
• Lock holds access to the systems that matter behind identity and condition controls.

The supporting modules

These modules round out the pattern and are usually added as the deployment matures.

• Transfer governs what data is allowed to move, in which direction, and when.
• Archive preserves logs, records and evidence beyond the reach of the live estate.
• Execute fires the control action on signal, without waiting for a change window.

What good looks like

• No supplier path exists until a request is validated.
• Access windows close on schedule without human intervention.
• Only the approved role, system and function can be reached.
• Everything the supplier did is preserved for audit.

How the blueprint is deployed

Control Modules are a suite of tools and techniques deployed within your own estate and applied to the paths they govern: at a boundary, inside a zone, or at a third-party edge. Authorisation and evidence remain local, so losing connectivity to Firevault never opens a path.

Most deployments start with a single boundary or zone, prove the control behaviour, then extend the same blueprint across the estate. Modules can be customer-operated or co-managed.

How to scope it

Scoping starts with the paths, not the product. A short discovery exercise identifies the boundaries that matter, who needs to cross them, how often, and what evidence is required. That produces the module count and placement, which in turn produces the price. Blueprints are combined where an estate has more than one problem to solve.

Next steps

• Read the full blueprint detail: CP-03 blueprint
• See all nine modules and the other blueprints: Control by Firevault
• Talk it through with our team: contact Firevault

How Firevault would handle this

Controls an auditor can physically verify

Firevault gives you physical separation, named custody and evidenced access, so compliance claims about isolation and control are things you can show, not just assert.