AWS Security ChangesHomeSearch

AWS vpn: Document authorization policy evaluation and device token status in Client VPN connection logs

Service: vpn · 2026-09-30 · Documentation medium

File: vpn/latest/clientvpn-admin/connection-logging.md · Type: logging

Summary

Adds documentation for the `authorization-policy-evaluation` field (result, evaluation-type, shadow-mode, reason, device-token-status, context), device token status failure reasons, the `IncludeAuthorizationPolicyContext` logging option, and example connection logs for permit, deny/error, and periodic re-evaluation denial.

Security assessment

Documents log visibility into authorization decisions (permit/deny/error) and device trust provider validation outcomes, including deny reasons like `policy-deny` and `authorization-policy-deny`, plus the `IncludeAuthorizationPolicyContext` audit option. This is security/audit documentation rather than a fix for a specific vulnerability.

Evidence

+  * `authorization-policy-evaluation` — The result of evaluating the authorization policy, if an authorization policy is configured. This value contains the following subfields:

Diff

diff --git a/vpn/latest/clientvpn-admin/connection-logging.md b/vpn/latest/clientvpn-admin/connection-logging.md
index 58f7243..b076711 100644
--- a//vpn/latest/clientvpn-admin/connection-logging.md
+++ b//vpn/latest/clientvpn-admin/connection-logging.md
@@ -7 +7 @@
-Connection log entries
+Connection log entriesDevice token status failure reasonsConnection logging optionsAuthorization policy log examples
@@ -57 +57 @@ A connection log entry contains the following keys:
-  * `connection-attempt-failure-reason` — The reason for the connection failure, if applicable.
+  * `connection-attempt-failure-reason` — The reason for the connection failure, if applicable. When the authorization policy denies a connection, the value is `authorization-policy-deny`.
@@ -89 +89,15 @@ A connection log entry contains the following keys:
-  * `posture-compliance-statuses` — The posture compliance statuses returned by the [client connect handler](./connection-authorization.html), if applicable.
+  * `posture-compliance-statuses` — The compliance statuses returned by the [client connect handler](./connection-authorization.html) for [custom connection authorization](./connection-authorization.html#connection-authorization-posture-assessment), if applicable.
+
+  * `authorization-policy-evaluation` — The result of evaluating the authorization policy, if an authorization policy is configured. This value contains the following subfields:
+
+    * `result` — The authorization decision (`permit`, `deny`, or `error`). An `error` result can occur when a Cedar policy references an attribute that is absent from the connection context, among other reasons. For example, the client doesn't provide a device token and the policy references that provider's context. An error can also occur when the policy references a SAML or AD attribute that isn't present for the user. When shadow mode is `disabled`, Client VPN denies the connection.
+
+    * `evaluation-type` — The type of evaluation (`connection-attempt` or `periodic`). A `connection-attempt` evaluation occurs when the client connects. A `periodic` evaluation occurs during a re-evaluation of an active session.
+
+    * `shadow-mode` — A string that indicates the shadow mode setting (`enabled` or `disabled`). When `enabled`, Client VPN evaluates the policy without enforcing the decision. When `disabled`, Client VPN enforces `deny` and `error` decisions.
+
+    * `reason` — The reason for the authorization decision. This field is present only for `deny` and `error` results. The current emitted value is `policy-deny`.
+
+    * `device-token-status` — An object that contains the device token status for each device trust provider. Each provider entry contains a `status` subfield (`validated` or `failed`). If the status is `failed`, the entry also includes a `reason` subfield that describes the failure.
+
+    * `context` — The full authorization policy evaluation context. This subfield is included only when `IncludeAuthorizationPolicyContext` is enabled.
@@ -99,0 +114,146 @@ For more information about enabling connection logging, see [AWS Client VPN conn
+When you enable connection logging for a new or existing endpoint, you can set `IncludeAuthorizationPolicyContext` to include the full authorization policy evaluation context in your connection log entries. For more information, see Connection logging options.
+
+## Device token status failure reasons
+
+When the `status` of a `device-token-status` provider entry is `failed`, the entry includes a `reason` subfield. The `reason` subfield can have one of the following values.
+
+  * `token-expired`
+
+  * `signature-invalid`
+
+  * `token-malformed`
+
+  * `tenant-mismatch`
+
+  * `key-resolution-failed`
+
+  * `network-error`
+
+  * `internal-error`
+
+
+
+
+## Connection logging options
+
+You can configure the following option to control the content of your connection logs:
+
+  * `IncludeAuthorizationPolicyContext` — When `true`, connection log entries include the full authorization policy evaluation context. The default is `false`.
+
+
+
+
+## Authorization policy connection log examples
+
+When an authorization policy is configured, connection log entries record the authorization decision. The following example shows a successful connection that was permitted by the authorization policy.
+    
+    
+    {
+      "connection-log-type": "connection-attempt",
+      "connection-attempt-status": "successful",
+      "connection-attempt-failure-reason": "NA",
+      "connection-id": "cvpn-connection-01f248f0e3084e4f2",
+      "client-vpn-endpoint-id": "cvpn-endpoint-0f2d58d4869ece501",
+      "transport-protocol": "udp",
+      "connection-start-time": "2026-09-24 22:22:25",
+      "connection-last-update-time": "2026-09-24 22:22:25",
+      "client-ip": "172.1.0.162",
+      "client-ip-v6": "NA",
+      "common-name": "client1.domain.tld",
+      "device-type": "linux",
+      "device-ip": "72.21.198.66",
+      "port": "5567",
+      "ingress-bytes": "0",
+      "egress-bytes": "0",
+      "ingress-packets": "0",
+      "egress-packets": "0",
+      "authorization-policy-evaluation": {
+        "result": "permit",
+        "evaluation-type": "connection-attempt",
+        "shadow-mode": "disabled",
+        "device-token-status": {
+          "crowdstrike": {
+            "status": "validated"
+          }
+        }
+      },
+      "connection-end-time": "NA",
+      "connection-duration-seconds": "0"
+    }
+
+The following example shows a connection that was denied by the authorization policy.
+    
+    
+    {
+      "connection-log-type": "connection-attempt",
+      "connection-attempt-status": "failed",
+      "connection-attempt-failure-reason": "authorization-policy-deny",
+      "connection-id": "cvpn-connection-0a39f1b3b7082abbb",
+      "client-vpn-endpoint-id": "cvpn-endpoint-0f2d58d4869ece501",
+      "transport-protocol": "udp",
+      "connection-start-time": "NA",
+      "connection-last-update-time": "2026-09-25 17:14:11",
+      "client-ip": "NA",
+      "client-ip-v6": "NA",
+      "common-name": "client1.domain.tld",
+      "device-type": "linux",
+      "device-ip": "72.21.198.66",
+      "port": "28081",
+      "ingress-bytes": "0",
+      "egress-bytes": "0",
+      "ingress-packets": "0",
+      "egress-packets": "0",
+      "authorization-policy-evaluation": {
+        "result": "error",
+        "evaluation-type": "connection-attempt",
+        "shadow-mode": "disabled",
+        "reason": "policy-deny",
+        "device-token-status": {
+          "crowdstrike": {
+            "status": "failed",
+            "reason": "token-malformed"
+          }
+        }
+      },
+      "connection-end-time": "NA",
+      "connection-duration-seconds": "NA"
+    }
+
+The following example shows a session that was terminated when a periodic re-evaluation of the authorization policy no longer met the requirements.
+    
+    
+    {
+      "connection-log-type": "connection-reset",
+      "connection-attempt-status": "NA",
+      "connection-attempt-failure-reason": "NA",
+      "connection-id": "cvpn-connection-01f248f0e3084e4f2",
+      "client-vpn-endpoint-id": "cvpn-endpoint-0f2d58d4869ece501",
+      "transport-protocol": "udp",
+      "connection-start-time": "2026-09-24 22:22:25",
+      "connection-last-update-time": "2026-09-24 22:27:43",
+      "client-ip": "172.1.0.162",
+      "client-ip-v6": "NA",
+      "common-name": "client1.domain.tld",
+      "device-type": "linux",
+      "device-ip": "72.21.198.66",
+      "port": "5567",
+      "ingress-bytes": "21017",
+      "egress-bytes": "16438",
+      "ingress-packets": "330",
+      "egress-packets": "325",
+      "authorization-policy-evaluation": {
+        "result": "deny",
+        "evaluation-type": "periodic",
+        "shadow-mode": "disabled",
+        "reason": "policy-deny",
+        "device-token-status": {
+          "crowdstrike": {
+            "status": "validated"
+          }
+        }
+      },
+      "connection-end-time": "2026-09-24 22:27:43",
+      "connection-reset-status": "NA",
+      "connection-duration-seconds": "318"
+    }
+