The Vendor Is the Vector: Governing Third-Party Access to OT and IT
A service technician connects remotely to troubleshoot a building controller. The repair succeeds; the ticket closes, and operations continue. But the account remains enabled; the connection stays available, and the technician can still reach systems beyond the equipment serviced. Third-party access has become a standing exposure.
Cybersecurity Operations Infrastructure (CSOI) helps organizations bring access under control. Through Identity-Defined Networking, CSOI ties permitted connections to authenticated identities and specific resources. Network Cloaking and identity-based microsegmentation help keep unrelated systems undiscoverable and inaccessible to unauthorized connections. These capabilities provide a practical foundation for vendor support that stays within an approved operational boundary.
The vendor may be trusted, and the work is legitimate. The risk comes from access that exceeds the assignment or outlives its purpose. If a technician’s credentials or device are compromised, that standing connection can become a path into operational technology (OT) and information technology (IT).
For applicable U.S. electric-sector entities, vendor access also carries a specific compliance obligation. NERC CIP-003-9 became effective April 1, 2026, adding vendor electronic remote access controls for assets containing low-impact Bulk Electric System Cyber Systems.

Why Third-Party Access Remains After the Work Is Done
An onboarding questionnaire assesses a supplier’s practices. It does not enforce which systems a technician can reach on Tuesday afternoon.
A shared virtual private network (VPN) account weakens individual accountability. A remote maintenance computer that stays accessible between service calls may give a technician access to several systems, even when the assignment involves only one. Neither arrangement establishes a maintenance window or a resource boundary unless those restrictions are deliberately enforced.
Consider a contractor troubleshooting one building controller. If the connection also reaches surveillance infrastructure, engineering workstations, or business applications, the authorization exceeds the task.
CSOI’s policy-defined connections help narrow that reach authorized resources. The surrounding workflow should define the technician, approved device, necessary permissions, and start and end time. Together, connection controls and operational procedures make the maintenance assignment the basis for access.
What NERC CIP-003-9 Actually Requires
The North American Electric Reliability Corporation’s (NERC) CIP-003-9 standard addresses security management controls. Attachment 1, Section 6 requires applicable entities to implement methods for determining vendor electronic remote access, disabling that access, and detecting known or suspected inbound and outbound malicious communications associated with it.
These requirements concern qualifying assets containing low-impact Bulk Electric System Cyber Systems. They do not create a universal obligation for every utility, manufacturer, facility, or tribal enterprise.
The operational lesson travels further: access governance needs an observable connection, a usable shutoff method, and detection coverage.
CSOI’s access authorization and revocation capabilities can support the access-control portion of that design. Organizations must also establish detection, evidence, and response procedures appropriate to their environment. Each deployment should be evaluated against the applicable requirements.
Replace Standing Permission with an Approved Access Window
A useful vendor-access policy begins with the maintenance task. Record who needs access, which device they will use, the destination, the permitted activity, and the approving operational owner.
Use individual authentication and multifactor authentication for remote access. Keep application permissions limited as well: permission to connect to a workstation should not automatically confer administrative control.
NIST’s Guide to Operational Technology Security recommends justified remote access limited to business needs. Its Zero Trust guidance also rejects implicit trust based solely on network location.
CSOI applies cryptographic identity and policy-defined connections at the network layer. Administrators can restrict communication to specific devices, helping translate a maintenance authorization into a narrower network path.
The time boundary needs an enforced closure process. Establish who removes access at the deadline, how completion is confirmed, and how extensions are approved. Make closure part of the service workflow.
Limit What an Authorized Connection Can Reach
Identity verification establishes who or what may connect. Segmentation limits the consequences if an approved endpoint is compromised.
CSOI’s identity-based microsegmentation restricts permitted communication between resources. Network Cloaking makes protected resources undiscoverable and inaccessible until identity and policy requirements are satisfied. Together, these controls help reduce unauthorized discovery and lateral movement.
For manufacturing, scope supports the engineering resource needed for one production cell. For facilities, separate building systems maintenance from surveillance and business systems. For tribal enterprises, retain local authority over which contractors reach each operational environment.
Validate each design against the actual maintenance workflow and its dependencies.
A single-resource connection also needs scrutiny if that resource is a broadly connected jump host. Restrict its downstream reach, or the narrow entry point can still provide a wide path into the environment.

Revoke Access Without Rebuilding the Network
Revocation becomes difficult when a contractor’s access is spread across routing changes, firewall exceptions, shared credentials, and undocumented support paths.
CSOI documents point-and-click authorization and revocation between devices without requiring changes to access control lists or firewall rules. Identity-defined connections let teams manage permitted relationships without redesigning the underlying physical network.
That supports a practical response when a contract ends; a technician changes employers, or a service device becomes suspect: withdraw the relevant connection authorization.
Validate what withdrawal does in the deployed environment. Confirm whether an active session ends, whether reconnection is blocked, and whether an alternate remote-support path remains. Application accounts and previously issued credentials also need appropriate closure.
The operational benefit is a repeatable way to remove access while preserving approved production relationships.
Put the Workflow into Operation in Four Steps
1. Map Existing Support Paths
Inventory vendor accounts, remote tools, jump hosts, destinations, owners, and access schedules. Include unattended support connections. Review OT dependencies with operations staff before changing paths.
2. Pilot One Maintenance Workflow
Choose a bounded task with a known owner. Use CSOI to define the approved device connection and resource boundary. Document necessary application privileges, authentication, the access window, and the person responsible for closure.
3. Test Closure and Operational Continuity
Confirm approved work successes and unrelated resources remain unreachable. Revoke access, test an existing session and a fresh connection, and verify essential processes continue. Establish a controlled emergency procedure with named approval and subsequent review.
4. Retain Evidence and Repeat
Associate approvals, connection activity, policy changes, and closure confirmation with the maintenance record. Determine which systems provide each record and who reviews suspicious activity. Expand the workflow after operators confirm it supports safe maintenance.
Keep Support Available and Access Accountable
Effective third-party access governance makes outside expertise available under conditions of your organization’s controls. CSOI’s Identity-Defined Networking, Network Cloaking, and microsegmentation help limit unnecessary reach and make vendor connections easier to authorize and revoke.
Start with a clearer picture of your exposure. Request a complimentary network exposure assessment from CSOI and discuss the next practical steps for strengthening access across your IT and OT environments.







