STIGViewer Support

The Cisco ASA remote access VPN server must be configured to enforce certificate-based authentication before granting access to the network.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-239968CASA-VN-000440SV-239968r954210_ruleCCI-000766high
Description
To assure accountability and prevent unauthenticated access, non-privileged users must utilize multifactor authentication to prevent potential misuse and compromise of the system. Multifactor authentication uses two or more factors to achieve authentication. Use of password for user remote access for non-privileged account is not authorized. Factors include: (i) Something you know (e.g., password/PIN); (ii) Something you have (e.g., cryptographic identification device, token); or (iii) Something you are (e.g., biometric). A non-privileged account is any information system account with authorizations of a non-privileged user. Network access is any access to a network element by a user (or a process acting on behalf of a user) communicating through a network. The DoD CAC with DoD-approved PKI is an example of multifactor authentication.
STIGDate
Cisco ASA VPN Security Technical Implementation Guide2024-08-22

Related Frameworks

1 mapping across 4 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (7) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

IAC-06Multi-Factor Authentication (MFA)
0.50
IAC-06.1Network Access to Privileged Accounts
0.50
IAC-06.2Network Access to Non-Privileged Accounts
0.50
IAC-06.3Local Access to Privileged Accounts
0.50
IAC-06.4Out-of-Band Multi-Factor Authentication
0.50
IAC-10.7Hardware Token-Based Authentication
0.50
TDA-02.2Information Assurance Enabled Products
0.50
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (65) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AC-10Concurrent Session Control
1.00
AC-11Device Lock
1.00
AC-11(1)Pattern-hiding Displays
1.00
AC-17(10)Authenticate Remote Commands
1.00
AC-2(1)Automated System Account Management
1.00
AC-2(10)Shared and Group Account Credential Change
1.00
AC-2(11)Usage Conditions
1.00
AC-2(2)Automated Temporary and Emergency Account Management
1.00
AC-2(3)Disable Accounts
1.00
AC-2(4)Automated Audit Actions
1.00

+55 more (top 10 by confidence shown)

NIST 800-1710 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (1) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

3.5.3
1.00
CCI1 mapping

Details

Check Text (C-239968r954210_chk)

Review the ASA configuration to verify that it enforces certificate-based authentication before granting access to the network as shown in the example below. tunnel-group ANY_CONNECT type remote-access tunnel-group ANY_CONNECT webvpn-attributes authentication certificate If the ASA configuration does not enforce certificate-based authentication before granting access to the network, this is a finding.

Fix Text (F-43160r666309_fix)

Configure the ASA to enforce certificate-based authentication before granting access to the network as shown in the example below. ASA1(config)# tunnel-group ANY_CONNECT webvpn-attributes ASA1(config-tunnel-webvpn)# authentication certificate ASA1(config-tunnel-webvpn)# end