CASA-VN-000400 - The Cisco ASA remote access VPN server must be configured to use LDAP over SSL to determine authorization for granting access to the network - ldap


Protecting authentication communications between the client, the VPN Gateway, and the authentication server keeps this critical information from being exploited.

In distributed information systems, authorization processes and access control decisions may occur in separate parts of the systems. In such instances, authorization information is transmitted securely so timely access control decisions can be enforced at the appropriate locations. To support the access control decisions, it may be necessary to transmit as part of the access authorization information, supporting security attributes. This is due to the fact that in distributed information systems, there are various access control decisions that need to be made and different entities (e.g., services) make these decisions in a serial fashion, each requiring some security attributes to make the decisions.

This applies to VPN gateways that have the concept of a user account and have the login function residing on the VPN gateway.


Step 1: Configure the ASA to use LDAP over SSL as shown in the example below.

ASA2(config)# aaa-server LDAP protocol ldap
ASA2(config)# aaa-server LDAP (INSIDE) host
ASA2(config-aaa-server-host)# ldap-over-ssl enable
ASA2(config-aaa-server-host)# exit

Step 2: Configure the ASA to enforce authorization using the common name (CN) from the user's certificate.

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)# end

See Also

Item Details


References: 800-53|AC-24(1), CAT|II, CCI|CCI-002353, Rule-ID|SV-239966r856174_rule, STIG-ID|CASA-VN-000400, Vuln-ID|V-239966

Plugin: Cisco

Control ID: 7be7bd996168a0922bc8829ee2a3f7c31c0498d6dc4af643e26bb6f40ca86acf