AWS Security ChangesHomeSearch

AWS vpn: Client VPN: authentication vs authorization clarified

Service: vpn · 2026-11-05 · Documentation medium

File: vpn/latest/clientvpn-admin/client-authorization.md · Type: authz

Summary

Adds a section explaining that authenticating to a Client VPN endpoint only establishes a connection and does not grant network access; Client VPN denies all access by default and administrators must explicitly configure authorization scoped per user group, and can additionally use authorization policies based on user identity and device health.

Security assessment

The added text documents an authorization best practice: separation of authentication from authorization, deny-by-default behavior, least-privilege scoping of network access per user group, and device-posture-based authorization policies. It is security guidance rather than a fix for a specific vulnerability, so it is medium severity.

Evidence

+Client VPN denies all access by default. To control the networks and resources a connected user can reach, you must explicitly configure authorization to allow traffic and scope it to grant each group of users only the access it needs.

Diff

diff --git a/vpn/latest/clientvpn-admin/client-authorization.md b/vpn/latest/clientvpn-admin/client-authorization.md
index 05d98d2..86d0149 100644
--- a//vpn/latest/clientvpn-admin/client-authorization.md
+++ b//vpn/latest/clientvpn-admin/client-authorization.md
@@ -12,0 +13,8 @@ Client VPN supports two types of client authorization: security groups and netwo
+###### Authentication and authorization are separate
+
+When a user authenticates to a Client VPN endpoint, they establish a VPN connection. That alone does not grant access to any network or resource. This applies to any user who can authenticate, including through a shared SAML IdP application. For information about how authentication works, see [Client authentication in AWS Client VPN](./client-authentication.html).
+
+Client VPN denies all access by default. To control the networks and resources a connected user can reach, you must explicitly configure authorization to allow traffic and scope it to grant each group of users only the access it needs.
+
+Where applicable, you can also authorize the connection itself. Configure an authorization policy to allow or deny connections based on user identity and device health. For setup instructions, see [Device posture for AWS Client VPN](./device-posture.html).
+