Hands-on tutorial

Tutorials · Security Operations

How to Give Vendors and Contractors Secure Remote Access

Let vendors support your systems without leaving permanent backdoors: individual accounts, MFA, approval, time limits, jump hosts and recorded sessions.

Intermediate9 min7 steps

Before you start

  • A VPN or zero-trust access platform
  • A jump host or remote support tool that records sessions
  • A list of vendors and the systems they support

Step by step

  1. Ban shared and permanent accounts

    Every vendor engineer gets a named account. Remove generic logins such as 'vendor' or 'support'.

  2. Require MFA

    Enforce multi-factor authentication for all external access, ideally phishing-resistant methods.

  3. Grant access only when needed

    Accounts are disabled by default and enabled for a ticket and time window, with approval from the system owner.

  4. Use a jump host

    Vendors connect to a jump host or support portal, not directly to servers, controllers or network devices. Only the jump host can reach the target systems.

  5. Limit what they can reach

    Firewall rules allow the jump host to reach only the systems in the ticket.

  6. Record and review

    Record sessions and keep logs. Review them after sensitive work and spot-check regularly.

  7. Remove access afterwards

    Disable the account when the window ends and rotate any passwords the vendor saw.

Pro tips

  • Include remote access rules in vendor contracts.
  • Never allow remote desktop or vendor tools exposed directly to the internet.
  • Review the vendor account list every quarter.