
All Posts
9 min
read
A VPN opens a whole network where only one system should be reachable. The downsides of VPN for remote maintenance and why remote PAM is the secure alternative.
Published
09 Oct 2024
Aktualisiert
17 Nov 2026
When external service providers, manufacturers or your own administrators need remote access to servers, controllers and applications, most organisations reach for the familiar answer: a VPN. For employees reaching office applications, that is still a reasonable choice. For remote maintenance of critical systems, however, a VPN is the wrong tool. It opens a network where only a single system should be reachable, and it proves that someone was connected, not what they did.
This article sets out the concrete downsides of VPN for remote maintenance, what a secure VPN alternative has to deliver, and how to move to remote privileged access management (remote PAM) step by step without disrupting operations.
Key Takeaways
The pattern is almost always the same. A service provider needs access to a server, a database or a machine controller. They receive a VPN client, credentials and a firewall rule. Inside the tunnel they connect via RDP, SSH, VNC or the manufacturer's own tool. The access is set up for one project and often stays in place afterwards, because nobody owns switching it off.
Over the years this produces dozens of VPN accounts whose owners nobody can name with certainty. Each one is a path into the network that bypasses the firewall. How quickly open protocol access gets exploited is covered in our article on securing RDP.
A VPN authenticates the tunnel, not the individual task. Once connected, a user typically reaches an entire network segment. The technician who should maintain one database can also see neighbouring servers, file shares and, in the worst case, production equipment. For attackers this is ideal: one compromised VPN account is the starting point for lateral movement.
Service providers work with changing technicians. In practice several people share one VPN account or one admin password on the target system. Actions can then no longer be attributed to a single person. And because access rarely expires, rights remain long after the project has ended.
The VPN log shows login time, IP address and data volume. It does not show what the technician did on the target system. When an outage or incident occurs, exactly the evidence that auditors and insurers ask for is missing.
The VPN client runs on the service provider's laptop, a device whose patch level, antivirus and configuration you do not control. If that device is compromised, the tunnel connects it straight to your network.
VPN gateways sit on the internet by design, which is exactly why attackers favour them. In 2024, CVE-2024-3400, a vulnerability of the highest severity (CVSS 10.0) in Palo Alto Networks' GlobalProtect gateway, was actively exploited. Early 2025 brought an authentication bypass at Fortinet via CVE-2024-55591. We summarised these incidents in IT security independent of the US.
Every new service provider means an account, a client installation, a firewall rule and documentation, and every project end means the reverse. In reality the setup is done carefully and the removal is forgotten. The result is a growing list of access paths that nobody fully oversees.

An alternative is only better if it fixes these weaknesses directly. For privileged remote access that means:
These requirements follow the zero trust approach: no access is trusted by default, and every session is checked, limited and recorded on its own.
Remote privileged access management places a central access gateway between the user and the target system. The service provider signs in to the gateway in the browser, not to the network. The gateway checks identity and approval, connects to the one approved system in the background and records the session. RDP, SSH and VNC keep working, but encapsulated behind the gateway instead of exposed on the network. How this replaces scattered protocol access is explained in replace RDP, SSH and VNC with one gateway.
Internal administrators and external partners then use the same controlled path; only the approvals differ. Our guide to third-party access shows how to connect external partners. VISULOX implements exactly this flow: agentless, operated on-premises and usually ready in under two days. See external access with VISULOX for details.
Germany's NIS2 implementation act has applied since 6 December 2025. Section 30 of the BSI Act (BSIG) requires in-scope organisations to implement, among other things, access control, multi-factor authentication and supply chain security, which includes service providers with remote access. For industrial environments, the BSI module IND.3.2 additionally requires personal accounts, time windows, supervision with the option to abort, and detailed logging.
A VPN alone does not meet these requirements, because it neither approves individual systems nor proves what was done. Our NIS2 checklist for mid-sized companies lists the points auditors check, and remote maintenance in OT under BSI IND.3.2 covers the OT side.
The switch does not have to be a large project. A step-by-step approach works well in practice:
Our six-phase PAM roadmap shows how to plan the wider project.
The VPN does not disappear entirely. For site-to-site connections or employees reaching office applications it remains a proven tool. The difference is privileged access: as soon as someone exercises admin rights on critical systems, a tunnel is no longer enough. Each session then needs approval, limits and evidence.
Contact
Speak directly with a cybersecurity expert.
Remote maintenance over VPN was the standard for a long time, but it no longer fits today's requirements. A VPN opens a network instead of a system, relies on permanent and often shared access, and does not show what happens in a session. Remote PAM fixes exactly these weaknesses: access to one approved system, personal identity with MFA, just-in-time approvals and complete session recording. Start with an inventory of VPN accounts, move the most critical service providers first, and you can replace the VPN for remote maintenance without disrupting operations. (This article does not constitute legal advice.)
A current VPN encrypts the connection, so it protects against eavesdropping. For maintaining critical systems that is not enough: the VPN opens a whole network segment, usually relies on permanent accounts and does not prove what happens in the session. VPN gateways are also a frequent target themselves.
For privileged remote access, remote privileged access management (remote PAM) is the right alternative. It approves exactly one target system per task, verifies personal identity with MFA, limits access in time and records the session. ZTNA tools also restrict network access, but usually offer no session recording and no approval workflows.
Not with VISULOX. Access runs through the browser, without a VPN client at the service provider and without agents on target systems. That reduces effort on both sides and keeps third-party devices out of your network.
Usually not on its own. Section 30 BSIG requires access control, multi-factor authentication and supply chain security, among other things. A VPN can be part of the setup, but it neither approves individual systems nor proves what was done. Remote PAM closes that gap.
Table Of Content:
Talk to Our Experts
Speak directly with a VISULOX security expert and find out how to protect your infrastructure.
Share:
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.
Expert knowledge, practical tips, and the latest trends in PAM, compliance, and secure remote work — straight from the amitego team.