Platform
Solutions
Resources
Company
Platform
Solutions
Resources
Company
Use cases
Remote access and VPN authentication
WWPass removes usernames and passwords from VPN and remote desktop authentication. The same WWPass Key that authenticates employees across web applications and enterprise tools also secures VPN access, Windows logins, and remote desktop sessions — with no separate VPN password, no shared credentials, and no credential database for attackers to target.
Use cases
Remote access and VPN authentication
WWPass removes usernames and passwords from VPN and remote desktop authentication. The same WWPass Key that authenticates employees across web applications and enterprise tools also secures VPN access, Windows logins, and remote desktop sessions — with no separate VPN password, no shared credentials, and no credential database for attackers to target.
Use cases
Remote access and VPN authentication
WWPass removes usernames and passwords from VPN and remote desktop authentication. The same WWPass Key that authenticates employees across web applications and enterprise tools also secures VPN access, Windows logins, and remote desktop sessions — with no separate VPN password, no shared credentials, and no credential database for attackers to target.
The remote access credential problem
VPN credentials and remote desktop passwords are among the highest-value targets in enterprise environments. A stolen VPN password gives an attacker persistent access to the entire network from anywhere in the world. Unlike a compromised web application, a compromised VPN session is indistinguishable from a legitimate one.
Remote and hybrid workforces expanded the attack surface. Employees authenticate from personal devices, home networks, shared workstations, and contractor laptops — environments IT cannot fully control. Every VPN password in that environment is a liability.
VPN authentication without passwords
WWPass integrates with VPN infrastructure to replace username and password authentication with cryptographic key-based access. Confirmed VPN integrations include Fortinet, Cisco, Juniper, and OpenVPN. Integration uses standard protocols including RADIUS and Kerberos alongside SAML and OIDC for broader infrastructure.
The same WWPass Key the employee uses for web applications and SaaS tools authenticates them into the VPN. No separate VPN password to set, remember, reset, or expose. If a key is lost or a device is compromised, the key is revoked immediately through self-service — no waiting for IT, no window of exposure while a ticket is processed.
Remote desktop and Windows authentication
Remote desktop access through Windows and VMware environments is also supported through the same WWPass Key. Computers, thin clients, and virtual desktop environments all authenticate through the same cryptographic key infrastructure.
For Windows computer authentication specifically, Winlogon provides strong authentication for Windows personal accounts, LDAP-connected accounts, and Microsoft Entra ID environments. The same key works across all three Windows authentication contexts without requiring separate credentials for each.
For high-security remote access environments, the hardware WWPass Key — available as a USB token, NFC token, or smartcard — provides Authentication Assurance Level 3 (AAL3) as defined in NIST SP 800-63B. A health insurance company's system administrators access corporate resources through VMware and Windows Remote Desktop using the hardware WWPass Key specifically because of the assurance level it provides in their regulated environment.
One key for all remote access
The same WWPass Key authenticates across every remote access method:
Corporate VPN: Fortinet, Cisco, Juniper, OpenVPN
Remote desktop: Windows Remote Desktop, VMware environments
Windows computer login: personal, LDAP, and Entra ID accounts via Winlogon
Web applications and SaaS tools via SAML, OAuth2, and OIDC
Enterprise applications via SSO
No separate credential per access method. No password sprawl across VPN, remote desktop, and application logins. One key for everything.
Continuous authentication for persistent sessions
Removing the credential from the login event addresses initial access. Persistent remote sessions introduce a second risk: a compromised session that stays active after the login event passes.
WWPass supports continuous authentication for persistent sessions: ongoing monitoring of connection parameters including IP address range, time of day, browser type and version, and behavioral characteristics. Where parameters fall outside defined ranges, the system provides alerts and can automatically revoke access rights without requiring the user to re-authenticate through a credential flow that does not exist.
This is the post-login defence layer that credential-based remote access systems cannot provide — because they have no mechanism to revoke a valid credential mid-session without invalidating it for every future session too.
What changes for IT teams
No VPN passwords to manage. Self-service key management means employees provision, rotate, and revoke their own access without raising helpdesk tickets.
No shared device passwords. Each user authenticates through their own cryptographic key on shared workstations, thin clients, and kiosk terminals.
No credential database to protect. WWPass stores no usernames or passwords. A breach of remote access infrastructure yields no reusable credentials.
Immediate revocation. A lost device or compromised key is revoked in seconds by the user through their Service Key. No window of exposure while IT processes a reset request.
One integration layer. SAML, OAuth2, OIDC, RADIUS, and Kerberos cover the full stack of VPN, remote desktop, and application access from a single authentication layer.
Frequently asked questions
Q: Which VPN platforms does WWPass integrate with?
A: Confirmed VPN integrations include Fortinet, Cisco, Juniper, and OpenVPN. Integration uses RADIUS and Kerberos for VPN authentication alongside SAML and OIDC for broader infrastructure. WWPass engineers are available for customized integration assistance where needed.
Q: Does WWPass work for Windows remote desktop and VMware environments?
A: Yes. WWPass supports remote desktop access through Windows Remote Desktop and VMware environments on computers and thin clients. For Windows computer authentication, Winlogon provides strong authentication for personal accounts, LDAP-connected accounts, and Microsoft Entra ID environments through the same WWPass Key.
Q: What assurance level does WWPass reach for high-security remote access?
A: With a hardware WWPass Key and PIN or biometric, authentication reaches Authentication Assurance Level 3 (AAL3) as defined in NIST SP 800-63B, the highest level defined. This makes the hardware token the appropriate choice for high-security remote access environments including regulated industry and government infrastructure.
Q: What happens if a remote employee loses their WWPass Key?
A: The employee uses their Service Key to revoke the lost key and issue a replacement. VPN and remote desktop access is revoked immediately upon revocation. No IT involvement is required. The WWPass Key App can also be restored using a registered backup email. There is no VPN password to reset because there is no VPN password.
Q: Does WWPass support continuous authentication for persistent VPN sessions?
A: Yes. WWPass supports ongoing monitoring of connection parameters including IP address range, time of day, browser type and version, and behavioral characteristics during active sessions. Where parameters fall outside defined ranges, the system provides alerts and can automatically revoke access rights without requiring re-authentication.
The remote access credential problem
VPN credentials and remote desktop passwords are among the highest-value targets in enterprise environments. A stolen VPN password gives an attacker persistent access to the entire network from anywhere in the world. Unlike a compromised web application, a compromised VPN session is indistinguishable from a legitimate one.
Remote and hybrid workforces expanded the attack surface. Employees authenticate from personal devices, home networks, shared workstations, and contractor laptops — environments IT cannot fully control. Every VPN password in that environment is a liability.
VPN authentication without passwords
WWPass integrates with VPN infrastructure to replace username and password authentication with cryptographic key-based access. Confirmed VPN integrations include Fortinet, Cisco, Juniper, and OpenVPN. Integration uses standard protocols including RADIUS and Kerberos alongside SAML and OIDC for broader infrastructure.
The same WWPass Key the employee uses for web applications and SaaS tools authenticates them into the VPN. No separate VPN password to set, remember, reset, or expose. If a key is lost or a device is compromised, the key is revoked immediately through self-service — no waiting for IT, no window of exposure while a ticket is processed.
Remote desktop and Windows authentication
Remote desktop access through Windows and VMware environments is also supported through the same WWPass Key. Computers, thin clients, and virtual desktop environments all authenticate through the same cryptographic key infrastructure.
For Windows computer authentication specifically, Winlogon provides strong authentication for Windows personal accounts, LDAP-connected accounts, and Microsoft Entra ID environments. The same key works across all three Windows authentication contexts without requiring separate credentials for each.
For high-security remote access environments, the hardware WWPass Key — available as a USB token, NFC token, or smartcard — provides Authentication Assurance Level 3 (AAL3) as defined in NIST SP 800-63B. A health insurance company's system administrators access corporate resources through VMware and Windows Remote Desktop using the hardware WWPass Key specifically because of the assurance level it provides in their regulated environment.
One key for all remote access
The same WWPass Key authenticates across every remote access method:
Corporate VPN: Fortinet, Cisco, Juniper, OpenVPN
Remote desktop: Windows Remote Desktop, VMware environments
Windows computer login: personal, LDAP, and Entra ID accounts via Winlogon
Web applications and SaaS tools via SAML, OAuth2, and OIDC
Enterprise applications via SSO
No separate credential per access method. No password sprawl across VPN, remote desktop, and application logins. One key for everything.
Continuous authentication for persistent sessions
Removing the credential from the login event addresses initial access. Persistent remote sessions introduce a second risk: a compromised session that stays active after the login event passes.
WWPass supports continuous authentication for persistent sessions: ongoing monitoring of connection parameters including IP address range, time of day, browser type and version, and behavioral characteristics. Where parameters fall outside defined ranges, the system provides alerts and can automatically revoke access rights without requiring the user to re-authenticate through a credential flow that does not exist.
This is the post-login defence layer that credential-based remote access systems cannot provide — because they have no mechanism to revoke a valid credential mid-session without invalidating it for every future session too.
What changes for IT teams
No VPN passwords to manage. Self-service key management means employees provision, rotate, and revoke their own access without raising helpdesk tickets.
No shared device passwords. Each user authenticates through their own cryptographic key on shared workstations, thin clients, and kiosk terminals.
No credential database to protect. WWPass stores no usernames or passwords. A breach of remote access infrastructure yields no reusable credentials.
Immediate revocation. A lost device or compromised key is revoked in seconds by the user through their Service Key. No window of exposure while IT processes a reset request.
One integration layer. SAML, OAuth2, OIDC, RADIUS, and Kerberos cover the full stack of VPN, remote desktop, and application access from a single authentication layer.
Frequently asked questions
Q: Which VPN platforms does WWPass integrate with?
A: Confirmed VPN integrations include Fortinet, Cisco, Juniper, and OpenVPN. Integration uses RADIUS and Kerberos for VPN authentication alongside SAML and OIDC for broader infrastructure. WWPass engineers are available for customized integration assistance where needed.
Q: Does WWPass work for Windows remote desktop and VMware environments?
A: Yes. WWPass supports remote desktop access through Windows Remote Desktop and VMware environments on computers and thin clients. For Windows computer authentication, Winlogon provides strong authentication for personal accounts, LDAP-connected accounts, and Microsoft Entra ID environments through the same WWPass Key.
Q: What assurance level does WWPass reach for high-security remote access?
A: With a hardware WWPass Key and PIN or biometric, authentication reaches Authentication Assurance Level 3 (AAL3) as defined in NIST SP 800-63B, the highest level defined. This makes the hardware token the appropriate choice for high-security remote access environments including regulated industry and government infrastructure.
Q: What happens if a remote employee loses their WWPass Key?
A: The employee uses their Service Key to revoke the lost key and issue a replacement. VPN and remote desktop access is revoked immediately upon revocation. No IT involvement is required. The WWPass Key App can also be restored using a registered backup email. There is no VPN password to reset because there is no VPN password.
Q: Does WWPass support continuous authentication for persistent VPN sessions?
A: Yes. WWPass supports ongoing monitoring of connection parameters including IP address range, time of day, browser type and version, and behavioral characteristics during active sessions. Where parameters fall outside defined ranges, the system provides alerts and can automatically revoke access rights without requiring re-authentication.
The remote access credential problem
VPN credentials and remote desktop passwords are among the highest-value targets in enterprise environments. A stolen VPN password gives an attacker persistent access to the entire network from anywhere in the world. Unlike a compromised web application, a compromised VPN session is indistinguishable from a legitimate one.
Remote and hybrid workforces expanded the attack surface. Employees authenticate from personal devices, home networks, shared workstations, and contractor laptops — environments IT cannot fully control. Every VPN password in that environment is a liability.
VPN authentication without passwords
WWPass integrates with VPN infrastructure to replace username and password authentication with cryptographic key-based access. Confirmed VPN integrations include Fortinet, Cisco, Juniper, and OpenVPN. Integration uses standard protocols including RADIUS and Kerberos alongside SAML and OIDC for broader infrastructure.
The same WWPass Key the employee uses for web applications and SaaS tools authenticates them into the VPN. No separate VPN password to set, remember, reset, or expose. If a key is lost or a device is compromised, the key is revoked immediately through self-service — no waiting for IT, no window of exposure while a ticket is processed.
Remote desktop and Windows authentication
Remote desktop access through Windows and VMware environments is also supported through the same WWPass Key. Computers, thin clients, and virtual desktop environments all authenticate through the same cryptographic key infrastructure.
For Windows computer authentication specifically, Winlogon provides strong authentication for Windows personal accounts, LDAP-connected accounts, and Microsoft Entra ID environments. The same key works across all three Windows authentication contexts without requiring separate credentials for each.
For high-security remote access environments, the hardware WWPass Key — available as a USB token, NFC token, or smartcard — provides Authentication Assurance Level 3 (AAL3) as defined in NIST SP 800-63B. A health insurance company's system administrators access corporate resources through VMware and Windows Remote Desktop using the hardware WWPass Key specifically because of the assurance level it provides in their regulated environment.
One key for all remote access
The same WWPass Key authenticates across every remote access method:
Corporate VPN: Fortinet, Cisco, Juniper, OpenVPN
Remote desktop: Windows Remote Desktop, VMware environments
Windows computer login: personal, LDAP, and Entra ID accounts via Winlogon
Web applications and SaaS tools via SAML, OAuth2, and OIDC
Enterprise applications via SSO
No separate credential per access method. No password sprawl across VPN, remote desktop, and application logins. One key for everything.
Continuous authentication for persistent sessions
Removing the credential from the login event addresses initial access. Persistent remote sessions introduce a second risk: a compromised session that stays active after the login event passes.
WWPass supports continuous authentication for persistent sessions: ongoing monitoring of connection parameters including IP address range, time of day, browser type and version, and behavioral characteristics. Where parameters fall outside defined ranges, the system provides alerts and can automatically revoke access rights without requiring the user to re-authenticate through a credential flow that does not exist.
This is the post-login defence layer that credential-based remote access systems cannot provide — because they have no mechanism to revoke a valid credential mid-session without invalidating it for every future session too.
What changes for IT teams
No VPN passwords to manage. Self-service key management means employees provision, rotate, and revoke their own access without raising helpdesk tickets.
No shared device passwords. Each user authenticates through their own cryptographic key on shared workstations, thin clients, and kiosk terminals.
No credential database to protect. WWPass stores no usernames or passwords. A breach of remote access infrastructure yields no reusable credentials.
Immediate revocation. A lost device or compromised key is revoked in seconds by the user through their Service Key. No window of exposure while IT processes a reset request.
One integration layer. SAML, OAuth2, OIDC, RADIUS, and Kerberos cover the full stack of VPN, remote desktop, and application access from a single authentication layer.
Frequently asked questions
Q: Which VPN platforms does WWPass integrate with?
A: Confirmed VPN integrations include Fortinet, Cisco, Juniper, and OpenVPN. Integration uses RADIUS and Kerberos for VPN authentication alongside SAML and OIDC for broader infrastructure. WWPass engineers are available for customized integration assistance where needed.
Q: Does WWPass work for Windows remote desktop and VMware environments?
A: Yes. WWPass supports remote desktop access through Windows Remote Desktop and VMware environments on computers and thin clients. For Windows computer authentication, Winlogon provides strong authentication for personal accounts, LDAP-connected accounts, and Microsoft Entra ID environments through the same WWPass Key.
Q: What assurance level does WWPass reach for high-security remote access?
A: With a hardware WWPass Key and PIN or biometric, authentication reaches Authentication Assurance Level 3 (AAL3) as defined in NIST SP 800-63B, the highest level defined. This makes the hardware token the appropriate choice for high-security remote access environments including regulated industry and government infrastructure.
Q: What happens if a remote employee loses their WWPass Key?
A: The employee uses their Service Key to revoke the lost key and issue a replacement. VPN and remote desktop access is revoked immediately upon revocation. No IT involvement is required. The WWPass Key App can also be restored using a registered backup email. There is no VPN password to reset because there is no VPN password.
Q: Does WWPass support continuous authentication for persistent VPN sessions?
A: Yes. WWPass supports ongoing monitoring of connection parameters including IP address range, time of day, browser type and version, and behavioral characteristics during active sessions. Where parameters fall outside defined ranges, the system provides alerts and can automatically revoke access rights without requiring re-authentication.
Get WWPass
Download the WWPass Key app and test authentication without a username or password.
Get WWPass
Download the WWPass Key app and test authentication without a username or password.
