PodcastOT & ICS · Third-Party Access

The Integrator Is Part of the OT Trust Boundary

New CISA/FBI guidance shows why third-party ICS access is not merely a VPN problem. Supplier identity, privilege, customer data and operational recovery all become part of the security case.

Cybersecurity Under Pressure podcast artworkPodcast episode
Listen here

Listen to the full episode.

Episode guide

Navigate the reasoning, not just the runtime.

Four editorial phases and the conclusions worth carrying into a technical or risk discussion.

Chapters

01
The Technical Breakdown

How ICS integrators can inherit engineering, data and operational authority that extends well beyond a secure VPN tunnel.

02
The Operational Decisions

How named identity, approved devices, time-bounded privilege, monitoring and contractual controls can bound integrator authority.

03
The Pressure Test

What happens when the integrator itself is compromised, unavailable or becomes an untrusted dependency during an incident.

04
The Key Takeaways

Why third-party OT access should be governed as privileged operational authority with a defined recovery path.

Key takeaways

  1. A secure tunnel does not constrain what an authenticated third party can change.
  2. Integrator identities should be named, time-bounded, least-privileged and reconstructable after an incident.
  3. Customer engineering data held by suppliers is part of the downstream attack surface.
  4. Offline backups and manual operation reduce dependence on a compromised or unavailable integrator.

Editorial chapter map. Timecodes appear only when validated against the published audio; none are inferred from duration or section names.

What this episode examines

This episode examines what happens when an integrator inherits engineering or operational authority inside an industrial environment.

The Technical Breakdown

ICS integrators may program SCADA, maintain devices, handle engineering files or support daily operations. A secure tunnel protects transport but does not limit what an authorised session can change.

The Operational Decisions

Use named identities, approved devices, time-bounded access, least privilege, session monitoring, explicit contractual controls and rapid revocation. Preserve offline backups and manual operating capability.

The Pressure Test

If the integrator itself is compromised or unavailable, can the operator identify exposed data, revoke authority and continue operating safely without depending on that supplier?

The Key Takeaways

Third-party OT access should be treated as privileged operational authority that is bounded, observable and recoverable.

Read the technical analysis

Related analysisThird-Party ICS Access Is an Operational Trust Boundary, Not a VPN ProblemRead analysis →