The Cisco ASA remote access VPN server must be configured to map the distinguished name (DN) from the client’s certificate to entries in the authentication server to determine authorization to access the network.

Without mapping the certificate used to authenticate to the user account, the ability to determine the identity of the individual user or group will not be available for forensic analysis.

This requirement only applies to components where this is specific to the function of the device or has the concept of a user (e.g., VPN or ALG). This does not apply to authentication for the purpose of configuring the device itself (i.e., device management).

Review the tunnel group configured for remote access and verify that the DN or UPN from the client’s certificate is used to map to entries in the authentication server to determine authorization as shown in the example below.

tunnel-group ANY_CONNECT type remote-access tunnel-group ANY_CONNECT general-attributes authorization-server-group LDAP authorization-required username-from-certificate use-entire-name

If the ASA is not configured to map the distinguished name or UPN from the client’s certificate to entries in the authentication server to determine authorization, this is a finding.

Configure the ASA to map the DN or UPN from the client’s certificate to entries in the authentication server to determine authorization as shown in the example.

ASA2(config)# tunnel-group ANY_CONNECT general-attributes ASA2(config-tunnel-general)# authorization-required ASA2(config-tunnel-general)# authorization-server-group LDAP ASA2(config-tunnel-general)# username-from-certificate username-from-certificate use-entire-name ASA2(config-tunnel-general)# end