Join our Newsletter — 33% off our NHI Course
Home› Guides› Vendor Privileged Access Management (VPAM) Guide
Guide Identity Governance (IGA)

Vendor Privileged Access Management (VPAM) Guide

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 27 October 2026 13 min read
On this page

Vendors, integrators and managed service providers often hold the most powerful remote access into an organisation, through accounts and tools the organisation neither issued nor watches. Vendor privileged access management (VPAM) is the discipline of giving third parties administrative access only through a brokered, approved, time-limited and recorded session, without handing them a VPN account or a standing password. This guide covers the VPAM architecture, how to identify vendor users without owning their identity lifecycle, credential injection, approvals, session monitoring, the remote support tools that sit beside VPAM, and how to roll it out. It goes deeper on the privileged part of the problem than the Third-Party Access Guide, which covers the wider onboarding, governance and offboarding of all third-party identities. It is for PAM, IAM and third-party risk teams, and for the infrastructure owners who sponsor vendors.

Key takeaways

  • Broker, never connect directly. Vendor administrators should reach target systems only through a gateway that authenticates them, checks approval and proxies the protocol, so no network route or credential is handed over.
  • Vendors never see the password. Credential injection from a vault means the shared or privileged account password stays inside the PAM system and can be rotated after every session.
  • Access exists only while work is approved. Tie each session to a ticket or time window; accounts and routes that are always on are the gap attackers use.
  • Record and watch, then review. Session recording, keystroke or command logs and live monitoring for high-risk targets turn vendor activity from invisible to evidential.
  • The vendor's own tooling is part of your attack surface. Remote support platforms, RMM agents and the API keys behind them need the same scrutiny as the vendor's people, as the BeyondTrust Remote Support incident showed.

Why vendor privileged access is different

Employee privileged access is governed by HR-driven joiner, mover and leaver events, managed devices and internal MFA. Vendor access breaks each of those assumptions:

  • Identity is not yours: the vendor hires and dismisses its engineers. You learn about a leaver late or never, so vendor accounts outlive the people using them.
  • Devices are not yours: vendor laptops are outside your endpoint controls. In the Uber Breach, a contractor's password was likely stolen by malware on a personal device, then MFA fatigue completed the takeover.
  • Accounts are shared: support teams often work a rota, so one named login quietly becomes a team login, which destroys attribution.
  • Access is bursty: a vendor may need domain admin rights for four hours once a quarter. Standing access for that pattern is almost entirely unused risk.
  • Trust is transitive: ATT&CK tracks the route as T1199 Trusted Relationship, and the remote access paths themselves as T1133 External Remote Services. A compromised provider reaches every customer it can connect to.

CISA, NSA and MS-ISAC noted in advisory AA23-025A that managed service providers and IT help desks are prime targets precisely because compromising one extends to many customers.

Access models compared

ModelHow the vendor connectsStrengthsWeaknessesUse when
Site-to-site or client VPN accountNetwork-level access, then native protocols with credentials the vendor holdsSimple, cheap, familiarBroad network reach, vendor holds passwords, little session visibility, accounts left enabledAvoid for privileged work; acceptable only for low-risk, segmented access with MFA
Jump host or bastionVPN or published RDP/SSH to a hardened host, then onwardSingle choke point, can record locallyVendor still holds target credentials; jump host becomes a high-value targetTransitional step while VPAM is deployed
VPAM broker (clientless or agent-based)Browser or lightweight client to a broker that injects credentials and proxies RDP, SSH, web consoles or database sessionsNo network route, no password disclosure, approvals, recording, per-target scopeLicensing, onboarding effort per target, protocol coverage gapsDefault for privileged vendor access to servers, network devices, OT and cloud consoles
Vendor-operated remote support or RMM toolAgent on your endpoints connecting to the vendor's cloudVendor productivity, supports end-user devicesControl plane sits with the vendor; its keys and accounts can reach your fleetOnly where contractually required, allowlisted and monitored
Federated cloud access (B2B guest, cross-account role)Vendor signs in with its own IdP into your tenant or accountVendor MFA and lifecycle, conditional access, no passwords to shareYou depend on the vendor's IdP hygiene; guest sprawlSaaS and cloud administration; combine with JIT role activation

Many organisations end up with two lanes: federated identity plus just-in-time role activation for cloud control planes, and a VPAM broker for everything that speaks RDP, SSH, Telnet, VNC or a web admin console. See the Entra ID Cross-Tenant Access and B2B Guest Governance Guide for the federated lane.

Core VPAM controls

Identifying vendor users

  • One person, one identity: each vendor engineer gets a named account in the VPAM system, never a shared company login. Require the vendor to notify you of leavers contractually within an agreed period, and do not rely on that alone.
  • Sponsor-driven enrolment: an internal sponsor invites the vendor user, sets an end date (for example 90 days) and must renew it. No sponsor, no access.
  • Phishing-resistant MFA: enforce FIDO2 or certificate-based authentication at the broker where the vendor can support it, and at least app-based push with number matching otherwise. NIST SP 800-53 IA-2(1) requires MFA for privileged accounts.
  • Federation where mature: large vendors can federate their own IdP so their leaver process disables access at source. Keep the sponsor end date as a second control.

Credential handling

  • Injection, not disclosure: the broker retrieves the target account credential from the vault and injects it into the session. The vendor never sees or types it.
  • Rotate on check-in: rotate privileged account passwords after each vendor session, or at least daily, so a recorded or keylogged secret is worthless.
  • Prefer dedicated target accounts per vendor: a vendor-specific local or domain account with scoped rights makes logs attributable and lets you disable one vendor without affecting others.
  • Remove embedded vendor credentials: default and hard-coded vendor maintenance passwords on appliances and OT equipment must be changed and vaulted.

Approvals and time limits

  • Ticket-bound sessions: require a change or incident ticket reference to start a session, and validate it against the ITSM system where possible.
  • Time windows: grant access for the change window only. PCI DSS v4.0 Requirement 8.2.7 expects third-party remote access accounts to be enabled only for the period needed and monitored when in use.
  • Dual control for crown jewels: domain controllers, PAM itself, backup systems, hypervisors and safety-related OT need an approver who is not the sponsor.
  • Emergency path: a documented, alerting break-glass route for out-of-hours vendor support, reviewed the next working day.

Session control and recording

  • Record everything privileged: video for graphical sessions, command and keystroke logs for SSH and database sessions, with recordings protected from deletion by administrators. NIST SP 800-53 AU-14 Session Audit and MA-4(1) Logging and Review of nonlocal maintenance apply.
  • Live monitoring for high-risk work: allow an internal engineer to shadow and terminate sessions in real time.
  • Command and action restrictions: block or require approval for high-risk commands, file transfer and clipboard where not needed.
  • Idle timeouts: terminate idle sessions (AC-12 Session Termination) and cap session duration.

The Privileged Session Management Guide covers recording architecture and privacy considerations in more depth.

Remote support tools, RMM agents and vendor NHIs

A large share of vendor access does not go through people logging in at all. It goes through software the vendor runs: remote support SaaS, RMM agents, monitoring collectors and API integrations. These are non-human identities with privileged reach, and they are where several major incidents started.

  • The vendor control plane: in the BeyondTrust Breach, a stolen infrastructure API key for the Remote Support SaaS service was used to reset local application account passwords on customer instances, which led to the US Treasury classing the intrusion as a major incident. Ask vendors how such keys are scoped, stored and monitored, and whether you are notified when they are used.
  • Allowlist approved tools: CISA advisory AA23-025A recommends auditing remote access tools to identify the authorised ones, using application control to block unapproved and portable RMM executables, and permitting authorised RMM only from inside the network over approved remote access such as VPN or VDI. ATT&CK tracks misuse of such software as T1219 Remote Access Tools.
  • Vendor service accounts in your estate: monitoring collectors, backup agents and integration accounts often hold domain or cloud admin rights they do not need. Inventory them, scope them, give them an internal owner and rotate their credentials. See the OWASP NHI Top 10 NHI3 Vulnerable Third-Party NHI Guide.
  • Support staff with customer access: the Okta Support System Breach shows the reverse direction: a service account for the vendor's own support system was saved in an employee's personal browser profile, and files customers had uploaded to support, including session tokens, were exposed. Strip session tokens and secrets from anything you send a vendor.

Implementing VPAM: a phased rollout

  1. Discover vendor access paths: list VPN accounts held by third parties, firewall rules for vendor IPs, published RDP and SSH, remote support and RMM agents (search EDR software inventory), guest accounts and cross-account roles, and vendor-held local admin accounts on appliances. Expect to find more than the contract register shows.
  2. Tier vendors and targets: rank by the privilege of the target (tier 0 identity systems, PAM, backup, hypervisors and OT first) and by how often the vendor connects.
  3. Pilot with one or two vendors: choose a cooperative vendor with frequent access to a high-value system. Run sessions through the broker in parallel with the existing route for two to four weeks, confirm protocol support, recording quality and approval workflow.
  4. Cut over and close the old route: disable the vendor's VPN account and firewall rule once the broker path works. Keep the old route disabled, not deleted, for a defined rollback window (for example 30 days), then remove it.
  5. Vault and rotate target credentials: move vendor-used privileged accounts into the vault and turn on rotation after check-in. Test rotation on non-production first; some appliances lock or break when passwords change.
  6. Extend by tier: roll out vendor by vendor, tier 0 targets first. Make VPAM a contractual condition for new suppliers through your security clauses; see the Third-Party Security Contract Clauses Template.
  7. Operate: monthly sponsor recertification, quarterly sample review of recordings, and annual vendor access review tied to contract renewal.

Decision guidance

  • Small organisations: if a full PAM suite is out of reach, use a single hardened jump host with MFA, session recording and per-vendor accounts enabled only on request. That captures most of the value: no standing access, attributable sessions and evidence.
  • Large or regulated organisations: deploy a VPAM broker integrated with the vault, ITSM and SIEM, and federate large strategic vendors. Expect onboarding per target to be the main effort, not licensing.
  • OT and industrial sites: vendor access to control systems needs site-level approval and often physical or operator confirmation before a session can start. See the OT Third-Party and Integrator Access Guide.
  • MSPs with broad standing access: where an MSP runs your infrastructure day to day, ticket-bound sessions may be impractical. Use named accounts, JIT elevation for tier 0, full recording and an independent review of MSP activity instead.
  • VPAM or federation: choose federation where the vendor works in your cloud or SaaS control planes and has a mature IdP; choose a broker where the work is on servers, network devices or OT, or where the vendor cannot federate.

Detection and measurement

Feed broker, vault, VPN, firewall and EDR telemetry into the SIEM and alert on:

  • Vendor sessions outside the approved window or without a ticket reference.
  • Logons to vendor-dedicated target accounts that did not come through the broker (Windows event 4624 from a source other than the broker host).
  • Execution of remote access software not on the allowlist, including portable executables.
  • Vendor VPN or guest accounts authenticating after the sponsor end date.
  • Bulk file transfer, new account creation or privilege changes during vendor sessions.
MetricWhat it showsTarget
Share of privileged vendor sessions through the brokerCoverage of VPAM100 percent for tier 0 and tier 1 targets
Vendor accounts with standing (always-on) accessResidual standing privilegeFalling to zero outside documented MSP exceptions
Vendor identities without a current sponsorLifecycle hygieneZero; auto-disable at end date
Unapproved remote access tools detected per monthShadow access pathsFalling trend, each one investigated
Percentage of recorded sessions sampled and reviewedWhether recordings are usedAgreed sample, for example 5 percent plus all tier 0
Median time from vendor offboarding notice to access removalOffboarding speedSame working day

Framework mapping

Control areaNIST SP 800-53 Rev. 5NIST CSF 2.0ISO/IEC 27001:2022 Annex A
Remote access through managed pointsAC-17, AC-17(1)PR.AA-05A.8.20 Networks security
Vendor maintenance sessions logged and reviewedMA-4, MA-4(1), AU-14DE.CM-06A.8.15 Logging
Privileged access and MFAIA-2(1), AC-2(6)PR.AA-05A.8.2 Privileged access rights
External personnel and servicesPS-7, SA-9GV.SC-05, GV.SC-07A.5.19, A.5.20 Supplier relationships and agreements
Session terminationAC-12PR.AA-05A.8.5 Secure authentication

Common failure patterns

  • The forgotten VPN account: VPAM is deployed but the vendor's old VPN account and firewall rule are never removed, so the attacker simply uses the old route.
  • Brokered session, disclosed password: the session goes through the broker but the vendor is shown the target password "just this once", and it is never rotated.
  • Shared vendor logins: one named account used by a whole support team, so recordings cannot be attributed and leavers keep access.
  • Recordings nobody watches: sessions are recorded for compliance but no one reviews them or alerts on risky actions, so evidence arrives only after the incident.
  • Ignoring the vendor's software: remote support and RMM agents installed by vendors bypass the broker entirely, and their cloud control plane holds keys to your fleet.
  • Lifecycle by trust: relying on the vendor to report leavers, with no sponsor end date or recertification.

Practitioner checklist

  • Inventory every vendor access path: VPN, firewall rules, published RDP/SSH, guest accounts, cross-account roles and remote support or RMM agents.
  • Route all privileged vendor sessions through a broker or hardened jump host with MFA, and close the direct routes.
  • Give each vendor engineer a named identity with an internal sponsor and an end date.
  • Vault target credentials, inject them into sessions and rotate after each session.
  • Bind sessions to tickets and time windows; require dual approval for tier 0 targets.
  • Record all privileged vendor sessions, protect recordings and sample them for review.
  • Allowlist approved remote access tools and block the rest, including portable versions.
  • Inventory vendor service accounts and API keys in your estate and give each an internal owner.
  • Alert on vendor activity outside windows, outside the broker, or after sponsor end dates.
  • Write VPAM requirements and leaver notification into supplier contracts.

Standards and references

Related NHI Mgmt Group resources: Third-Party Access Guide · Privileged Access Management Guide · JIT Access Guide · Vendor Offboarding and Termination Guide · PAM Buyer's Guide

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 27 October 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.