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.
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
Ban shared and permanent accounts
Every vendor engineer gets a named account. Remove generic logins such as 'vendor' or 'support'.
Require MFA
Enforce multi-factor authentication for all external access, ideally phishing-resistant methods.
Grant access only when needed
Accounts are disabled by default and enabled for a ticket and time window, with approval from the system owner.
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.
Limit what they can reach
Firewall rules allow the jump host to reach only the systems in the ticket.
Record and review
Record sessions and keep logs. Review them after sensitive work and spot-check regularly.
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.
FAQ
Frequently asked questions
Is a VPN enough?
A VPN alone gives too broad access. Combine it with a jump host, MFA and firewall rules, or use zero-trust access to single applications.
What about vendor 'cloud' remote support tools?
Use them only with your approval for each session, and make sure they can be disabled when not in use.
Keep learning
Related guides
SSH jump host (bastion)
Read more →ZTNA vs VPN vs SASE
Read more →Phishing-resistant MFA
Read more →How to Set Up a WireGuard VPN Server for Remote Access
WireGuard is a fast, modern VPN with a small, auditable code base. Build a WireGuard server on Linux, add users with their own keys and route them only to the networks they need.
Read more →How to Scan Your Network for Vulnerabilities With Nmap and OpenVAS
Find open ports, outdated services and known vulnerabilities before attackers do. Discover hosts with Nmap, then run authenticated vulnerability scans with Greenbone OpenVAS and fix what matters first.
Read more →How to Build a Free SIEM With Wazuh for Network and Server Logs
A SIEM collects logs from servers, firewalls and switches in one place and alerts on attacks. Install Wazuh, add agents and syslog sources, and tune the first alerts.
Read more →Stuck on a step?
Ask Navijin technical support or an authorised partner for help with your configuration.