Security teams should treat remote access as a high-risk entry point and reduce reliance on reusable credentials. Stronger options include phishing-resistant authentication, conditional access, least privilege, and tighter monitoring of unusual login patterns. The goal is to make stolen passwords insufficient on their own and to limit how far an intruder can move if one account is compromised.
Why username-and-password VPN access stays a weak point
When remote access still depends on reusable usernames and passwords, the weakest part is usually the credential itself, not the VPN protocol. Passwords are phishable, replayable after theft, and often reused elsewhere. That means a single successful capture can turn a remote access portal into a reliable entry point for initial access, even when the rest of the network is well defended.
Reducing that risk starts with assuming the login can be abused. The practical shift is to make one stolen password insufficient on its own, then narrow what that account can reach if it is used from the wrong device, location, or time window.
Strong remote access design also means treating the VPN as one control in a broader access path, not as the control. If the user, device, session, and destination are all trusted equally after password entry, the attacker inherits the same trust as the legitimate user.
How to reduce exposure without waiting for a full VPN replacement
Use phishing-resistant authentication wherever possible, then layer conditional access so the login decision depends on more than a password. A password may still be present for compatibility, but it should not be enough to satisfy the full access decision on its own.
Limit standing access as much as possible. Separate remote access entitlements by role, environment, and device posture, and avoid granting broad internal reach just because the user has authenticated successfully. Least privilege matters here because VPN compromise is often valuable precisely because it can flatten network boundaries.
Monitoring should focus on patterns that suggest abuse rather than on ordinary success events. Watch for impossible travel, unfamiliar devices, abnormal login times, repeated failures followed by success, and access to destinations the account does not normally use. Those signals are often more useful than raw VPN connection counts.
For practitioners who need a migration path, Secure Remote Access Beyond VPN Guide is the natural next step because it shows how to shrink the VPN with identity-aware alternatives instead of treating remote connectivity as a single gateway.
What to do when usernames and passwords cannot be retired yet
If the organisation must keep password-based remote access for now, the priority is to reduce blast radius, not to pretend the risk is solved. Put step-up authentication on higher-risk paths, require stronger checks for privileged users, and remove dormant or rarely used remote access accounts before they become a hidden entry point.
Build the control set around the specific access path. A VPN account that can reach sensitive admin systems, production support tools, or remote management interfaces needs tighter restrictions than an account used only for low-risk user access. Where possible, pair remote access policy with device trust, approved endpoints, and session logging.
Operationally, this is also where remote access governance needs a policy backbone. Remote Access Policy Template is useful because it covers the policy decisions that usually fail first: MFA, dormant accounts, vendor access, logging, and approved access methods.
If you want a threat-informed view of how stolen credentials are actually used against VPNs and similar entry points, T1133 External Remote Services Defensive Guide helps connect the access control decision to the attack path an intruder follows after the first login.
Risk and Threat Considerations
VPN-based compromise becomes serious when authentication is the only meaningful gate. If an attacker gets valid credentials, the VPN can provide trusted network reach, a stable foothold, and a low-noise path to internal systems that were never meant to be internet-adjacent. That makes password theft especially valuable for intrusion, persistence, and lateral movement.
Failure mechanism: Stolen or replayed credentials authenticate successfully because the control still treats password knowledge as sufficient proof of trust, and the resulting session is allowed too much network reach.
Impact: An attacker can enter through a legitimate remote access channel, blend in with normal traffic, and expand access from one account into additional systems, services, or administrative workflows.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5, CIS Controls v8 and NIST Zero Trust (SP 800-207) set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | IA-2 — Identification and Authentication (Organizational Users) | Remote VPN logins depend on user authentication strength. |
| AC-6 — Least Privilege | Limits what a compromised VPN user can reach after login. | |
| AU-6 — Audit Review, Analysis, and Reporting | Unusual VPN logins need monitoring and review for compromise signals. | |
| Recommendation — Require stronger user authentication for remote access entry points. Restrict remote access paths to the minimum needed resources. Review remote access logs for anomalous login and session patterns. | ||
| CIS Controls v8 | CIS-5 — Account Management | Dormant and over-permissive remote access accounts increase compromise risk. |
| CIS-6 — Access Control Management | Remote access should be constrained by policy and least privilege. | |
| CIS-8 — Audit Log Management | VPN compromise is often detected through log anomalies and session review. | |
| Recommendation — Remove dormant accounts and tighten remote access account lifecycle. Enforce remote access policy and narrow internal reach for VPN users. Centralise and review remote access logs for suspicious activity. | ||
| NIST Zero Trust (SP 800-207) | PA-1 — Policy Engine | Conditional access decisions are central to replacing password-only trust. |
| PA-2 — Policy Administrator | Remote access control needs enforcement of access decisions at the gateway. | |
| PA-3 — Policy Enforcement Point | The VPN or access gateway must enforce the resulting trust decision. | |
| Recommendation — Use policy decisions that combine identity, device and context signals. Enforce access decisions consistently at the remote access boundary. Place enforcement at the remote access point, not only in policy. | ||
Practitioner Guidance
What to prioritise: Put the highest assurance on the login step that opens the widest internal reach. If the remote access path can reach production, admin tooling, or sensitive data stores, it deserves stronger authentication and tighter session controls than ordinary user login.
What to verify: Check whether remote access is still usable with only a password, whether dormant accounts still exist, and whether successful VPN logins are being correlated with device trust, destination restrictions, and unusual session behaviour. If those checks are missing, the control is weaker than it appears.
Practitioner takeaway: The safest way to keep legacy VPN access is to make the password only one signal in the decision, then constrain the session so a compromised login cannot freely behave like a trusted insider.
Related resources from NHI Mgmt Group
- Guide: Remote Access Identity Guide
- How should security teams reduce breach risk when remote access still depends on passwords and weak MFA factors?
- Why do VPN-based remote access models still create privilege risk?
- Why does browser-based zero trust reduce risk compared with broad VPN access for remote users?
- Why does identity-based access reduce risk in SSH environments that still depend on passwords or shared keys?
Deepen Your Knowledge
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.
Reviewed and updated by the NHIMG editorial team on November 4, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org