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

Control need · Third-party and supplier access

Your suppliers need access. They do not need a permanent doorway.

Maintenance contracts, support arrangements and integrations all arrive with a connection attached. Those connections outlive the projects that created them, and they are rarely reviewed with the same care as employee access. Control governs the relationship rather than trusting it.

As featured in

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

What is exposed

Your risk now includes everyone you have ever connected to.

A supplier relationship is a commercial arrangement with a technical consequence. This is what is exposed when that consequence is left ungoverned.

Inherited risk

Their security posture, applied to you

A standing connection means their credential hygiene, patching and staff turnover become part of your risk position.

Orphaned access

Access that outlives the contract

Connections created for an implementation frequently remain live years after the supplier relationship changed or ended.

Excess privilege

Reach beyond the scope of work

Access granted for one system often carries network reach into others, because it was easier to grant broadly than precisely.

Governance gap

The audit answer you cannot give

Asked which suppliers can reach which systems today, most organisations need days to answer, and the answer is rarely complete.

Why the exposure exists

Access was granted to get work done, then nobody closed it.

Supplier access is created under delivery pressure and reviewed under audit pressure, which are two very different moments with two very different levels of scrutiny.

The honest position

Nobody wants to be the person who blocks the engineer at two in the morning.

Permanent access exists because the alternative has historically been friction. If opening a path takes a day of paperwork, teams will keep the path open permanently and tell themselves it is monitored. Control removes that trade-off by making the temporary path easy to open and automatic to close.

Control the path, protect the asset.

  • Temporary access has no expiryAccess granted for a project is almost never diarised for removal when the project ends.
  • Contracts do not describe connectivityCommercial agreements cover liability and service levels, rarely the physical path or its lifetime.
  • Suppliers hold the credentialsWhen the supplier manages its own accounts, your leavers process no longer covers who can reach you.
  • Convenience beats processIf requesting access is slow, teams keep standing access rather than face the delay each time.
  • Support tooling reaches widelyRemote support platforms are built for reach, which is exactly what makes them attractive to attackers.
  • The register is out of dateVendor access lists are compiled for audits and drift as soon as the audit finishes.

Which paths need controlling

Every relationship becomes a path with a lifetime.

Third-party risk becomes manageable the moment each relationship is expressed as a specific path with a specific lifetime. Switch between today and with Control.

  • Vendor remote support

    Who uses itEquipment and software suppliers

    How it behaves todayStanding remote access, often unmonitoredWhat Control governsOpened for an approved request, closed when the window ends

  • Managed service provider administration

    Who uses itOutsourced IT and security providers

    How it behaves todayPersistent administrative reach across zonesWhat Control governsScoped to the systems in the contract, time-bound per engagement

  • Integration and data exchange

    Who uses itPartner platforms and applications

    How it behaves todayAlways-on connection between estatesWhat Control governsDefined route with checks on what moves and when

  • Contractor and project access

    Who uses itTemporary staff and implementation teams

    How it behaves todayGranted at kick-off, removed inconsistentlyWhat Control governsExpires with the engagement without needing a manual step

How each window is requested, approved, brokered and recorded is Blueprint territory. What matters here is agreeing that these relationships should be paths with lifetimes rather than standing trust.

What physical Control changes

Supplier access that closes on its own.

Control does not make supplier access harder to obtain. It makes supplier access hard to leave open by accident.

Today

Standing supplier access

The path exists permanently and is restrained by credentials, agreements and good intentions.

  • Access continues after the project, the contract or the individual
  • Your exposure follows the supplier’s own security posture
  • Reviews happen at audit time rather than continuously
  • Activity records depend on the supplier’s tooling
  • Removing access requires someone to remember to do it

With Control

Time-bound governed access

The path is created for an approved purpose, held open for a defined period and physically removed when that period ends.

  • No standing route from any supplier into the estate
  • Each window tied to a named person and a stated purpose
  • Closure is automatic rather than dependent on memory
  • A clear record of who reached what, and when
  • An answer to the supplier access question that takes minutes, not days

Supply chain risk is not abstract. It is a list of connections you can name.Connected when approved. Disconnected by default.

The Control philosophy

Control the path, protect the asset.

Control is a way of thinking about connectivity before it is a product set.

  1. 1

    Start with the path, not the tool

    Every incident that spreads does so along a connection that was already there. Control begins by naming that connection in plain language, before anyone talks about products.

  2. 2

    Make the default state disconnected

    A path that exists only when it is needed cannot be used at three in the morning by someone who should not have it. Disconnection is the resting state, not the emergency response.

  3. 3

    Open on approval, close on schedule

    When work genuinely needs a connection, Control opens it for a named person, a stated purpose and a fixed period, then closes it again without anyone having to remember.

  4. 4

    Prove it physically, not on paper

    A policy says the path should be closed. Physical control shows that it is. That difference is what auditors, insurers and boards are actually asking about.

  1. NeedSets the direction
  2. ControlSets the rule
  3. BlueprintSets the architecture
  4. Modules and Firebreak®Implement it

Where this goes next

The Blueprint for this need is CP-03 Control Third-Party Access.

The Blueprint turns the agreed relationships into a working access pattern, including how requests are checked, how windows are brokered and what the audit trail contains.

CP-03 Control Third-Party Access

Give third parties access without giving them a permanent doorway. Applied to supplier, vendor and partner access.

What the Blueprint adds

  • How a request is validated before any path is created
  • The brokered route that keeps suppliers away from the wider estate
  • How windows are scheduled, extended and revoked
  • The evidence produced for supplier assurance and regulatory review
  • How the pattern scales across dozens of supplier relationships

Lead module

FV-Validate

Checks whether a request, command or approval should proceed before access, action or transfer is allowed.

Read FV-Validate

Lead module

FV-Relay

Allows connectivity only when needed, for a defined purpose, under controlled conditions and for a limited time.

Read FV-Relay

Lead module

FV-Lock

Restricts access through identity, authority, policy, permission and operational controls.

Read FV-Lock

Questions

What teams ask about third parties

In practice, yes. Suppliers are increasingly uncomfortable holding permanent access to customer estates because it makes them a target. A defined window with a clear record protects both sides.

The window is opened for an approved request, for a named person and a stated purpose, and closes when it ends. Because the temporary path is easy to open, the engineer is not blocked, and the access does not stay open afterwards.

No. Assessments judge the supplier. Control governs the path: each relationship becomes a specific connection with a specific lifetime, and a clear record of who reached what, and when.

It can help support them. The Blueprint produces evidence for supplier assurance and regulatory review, and the question of which suppliers can reach which systems takes minutes to answer, not days.

All questions

Name the relationships. Then design the doorway.

CP-03 Control Third-Party Access sets out the validation, brokering and evidence behind access that exists only when it should.