AWS vpn: Rename posture assessment to custom connection authorization; add Cedar policies
Summary
Renames the 'posture assessment' terminology to 'custom connection authorization' throughout the Client VPN connection authorization page, and adds a note that Cedar-based authorization policies can evaluate device posture tokens and user identity, linking to the device posture documentation.
Security assessment
The change documents an authorization capability (Cedar-based policies evaluating device posture and user identity) for Client VPN connection authorization. It is security-relevant guidance about access control but does not reference any specific vulnerability, CVE, or incident, so it is documentation of a security feature rather than a fix.
Evidence
+You can also define Cedar-based authorization policies that evaluate device posture tokens and user identity. For more information, see [Device posture for AWS Client VPN](./device-posture.html).
Diff
diff --git a/vpn/latest/clientvpn-admin/connection-authorization.md b/vpn/latest/clientvpn-admin/connection-authorization.md index e17be4b..2d69fac 100644 --- a//vpn/latest/clientvpn-admin/connection-authorization.md +++ b//vpn/latest/clientvpn-admin/connection-authorization.md @@ -7 +7 @@ -Requirements and considerationsLambda interfaceUse the client connect handler for posture assessmentEnable the client connect handlerService-linked roleMonitor connection authorization failures +Requirements and considerationsLambda interfaceCustom connection authorizationEnable the client connect handlerService-linked roleMonitor connection authorization failures @@ -18,0 +19,2 @@ Currently, the only type of client connect handler that is supported is a Lambda +You can also define Cedar-based authorization policies that evaluate device posture tokens and user identity. For more information, see [Device posture for AWS Client VPN](./device-posture.html). + @@ -110 +112 @@ The Lambda function must return the following fields. - * `posture-compliance-statuses` — Required. If you use the Lambda function for posture assessment, this is a list of statuses for the connecting device. You define the status names according to your posture assessment categories for devices, for example, `compliant`, `quarantined`, `unknown`, and so on. Each name can be up to 255 characters in length. You can specify up to 10 statuses. + * `posture-compliance-statuses` — Required. If you use the Lambda function for custom connection authorization, this is a list of statuses for the connecting device. You define the status names according to your assessment categories for devices, for example, `compliant`, `quarantined`, `unknown`, and so on. Each name can be up to 255 characters in length. You can specify up to 10 statuses. @@ -121 +123 @@ For more information about creating a Lambda function, see [Getting started with -## Use the client connect handler for posture assessment +## Custom connection authorization @@ -123 +125 @@ For more information about creating a Lambda function, see [Getting started with -You can use the client connect handler to integrate your Client VPN endpoint with your existing device management solution to evaluate the posture compliance of connecting devices. For the Lambda function to work as a device authorization handler, use [mutual authentication](./mutual.html) for your Client VPN endpoint. Create a unique client certificate and key for each client (device) that will connect to the Client VPN endpoint. The Lambda function can use the unique common name for the client certificate (that's passed from the Client VPN service) to identify the device and fetch its posture compliance status from your device management solution. You can use mutual authentication combined with user-based authentication. +You can use custom connection authorization to integrate your Client VPN endpoint with your existing device management solution to evaluate the compliance of connecting devices. For the Lambda function to work as a device authorization handler, use [mutual authentication](./mutual.html) for your Client VPN endpoint. Create a unique client certificate and key for each client (device) that will connect to the Client VPN endpoint. The Lambda function can use the unique common name for the client certificate (that's passed from the Client VPN service) to identify the device and fetch its compliance status from your device management solution. You can use mutual authentication combined with user-based authentication. @@ -125 +127 @@ You can use the client connect handler to integrate your Client VPN endpoint wit -Alternatively, you can do a basic posture assessment in the Lambda function itself. For example, you can assess the `platform` and `platform-version` fields that are passed to the Lambda function by the Client VPN service. +Alternatively, you can do a basic device assessment in the Lambda function itself. For example, you can assess the `platform` and `platform-version` fields that are passed to the Lambda function by the Client VPN service. @@ -143 +145 @@ You can view the connection authorization status of connections to the Client VP -When the client connect handler is used for posture assessment, you can also view the posture compliance statuses of devices that connect to your Client VPN endpoint in the connection logs. For more information, see [Connection logging for an AWS Client VPN endpoint](./connection-logging.html). +When using custom connection authorization, you can also view the compliance statuses of devices that connect to your Client VPN endpoint in the connection logs. For more information, see [Connection logging for an AWS Client VPN endpoint](./connection-logging.html).