STIGhubSTIGhub
STIGsRMF ControlsCompare
STIGhub— A free STIG search and compliance tool·STIGs updated 3 days ago
Powered by Pylon·Privacy·Terms·© 2026 Beacon Cloud Solutions, Inc.
← Back to Cisco ASA VPN Security Technical Implementation Guide

V-239965

CAT II (Medium)

The Cisco ASA remote access VPN server must be configured to use a separate authentication server than that used for administrative access.

Rule ID

SV-239965r666301_rule

STIG

Cisco ASA VPN Security Technical Implementation Guide

Version

V2R2

CCIs

CCI-000187

Discussion

The VPN interacts directly with public networks and devices and should not contain user authentication information for all users. AAA network security services provide the primary framework through which a network administrator can set up access control and authorization on network points of entry or network access servers. It is not advisable to configure access control on the VPN gateway or remote access server. Separation of services provides added assurance to the network if the access control server is compromised.

Check Content

In the example below, radius server at 10.1.1.2 is used for administrative access authentication while the LDAP server will be used for granting remote access to the network.

aaa-server LDAP protocol ldap
aaa-server LDAP (INSIDE) host 10.1.1.1
…
…
…
aaa-server RADIUS_GROUP protocol radius
aaa-server RADIUS_GROUP (INSIDE) host 10.1.1.2
 key *****
…
…
…
aaa authentication serial console RADIUS_GROUP LOCAL
aaa authentication ssh console RADIUS_GROUP LOCAL

If the ASA is not configured to use a separate authentication server than that used for administrative access, this is a finding.

Fix Text

Configure the ASA to use a separate authentication server as shown in the example below.

ASA2(config)# aaa-server LDAP protocol ldap
ASA2(config)# aaa-server LDAP (INSIDE) host 10.1.1.1