AWS Security ChangesHomeSearch

AWS vpn: Client VPN federation: default-deny, authorization rules, shared IdP caveat

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

File: vpn/latest/clientvpn-admin/federated-authentication.md · Type: authz

Summary

Adds guidance that authentication alone does not grant network access, that Client VPN denies all access by default, and that network-based authorization rules and security groups must be scoped per user group. Also warns that a shared IdP application uses the fixed service provider audience urn:amazon:webservices:clientvpn, so any user who can authenticate can connect to any Client VPN endpoint using that IdP, and recommends authorization rules to restrict access.

Security assessment

The added text documents authorization best practice (default deny, least-privilege authorization rules, security groups) and discloses a real weakness of shared IdP setups: a fixed audience value means any user who can authenticate through the IdP application can reach any Client VPN endpoint using that IdP. This is hardening/authorization guidance rather than a fix for a specific vulnerability or incident, so it is security documentation with medium impact.

Evidence

+Authentication only establishes the VPN connection. It does not, by itself, grant access to any network or resource. Client VPN denies all access by default, so you control access separately with authorization.

Diff

diff --git a/vpn/latest/clientvpn-admin/federated-authentication.md b/vpn/latest/clientvpn-admin/federated-authentication.md
index 3497601..86dfa0c 100644
--- a//vpn/latest/clientvpn-admin/federated-authentication.md
+++ b//vpn/latest/clientvpn-admin/federated-authentication.md
@@ -12,0 +13,8 @@ AWS Client VPN supports identity federation with Security Assertion Markup Langu
+Authentication only establishes the VPN connection. It does not, by itself, grant access to any network or resource. Client VPN denies all access by default, so you control access separately with authorization. Configure [network-based authorization rules](./client-authorization.html#auth-rules) — and, where applicable, [security groups](./client-authorization.html#security-groups) — to allow traffic. Scope them to grant each group of users only the access it needs. Broad rules, such as granting access to all clients, give any authenticated user access to the associated networks.
+
+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).
+
+###### Sharing your IdP across applications
+
+If you use the same IdP for multiple Client VPN endpoints within your account, the same fixed service provider audience value, `urn:amazon:webservices:clientvpn`, is used. A user who can authenticate through that IdP application can then connect to any Client VPN endpoint using your IdP. To restrict access, we recommend using [authorization rules](./client-authorization.html#auth-rules) as described above.
+