STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 3 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Cisco ASA VPN Security Technical Implementation Guide

V-239984

CAT II (Medium)

The Cisco ASA VPN remote access server must be configured to validate certificates used for Transport Layer Security (TLS) functions by performing RFC 5280-compliant certification path validation.

Rule ID

SV-239984r666358_rule

STIG

Cisco ASA VPN Security Technical Implementation Guide

Version

V2R2

CCIs

CCI-000185

Discussion

A certificate's certification path is the path from the end entity certificate to a trusted root certification authority (CA). Certification path validation is necessary for a relying party to make an informed decision regarding acceptance of an end entity certificate. Certification path validation includes checks such as certificate issuer trust, time validity, and revocation status for each certificate in the certification path. Revocation status information for CA and subject certificates in a certification path is commonly provided via certificate revocation lists (CRLs) or online certificate status protocol (OCSP) responses.

Check Content

Verify the ASA validates TLS certificates by performing RFC 5280-compliant certification path validation.

Review the ASA configuration to determine if a CA trust point has been configured as shown in the example below.

crypto ca trustpoint CA_X
 enrollment …
 validation-usage ipsec-client
 validation-usage ssl-client

If the ASA does not validate certificates used for TLS functions by performing RFC 5280-compliant certification path validation, this is a finding.

Fix Text

Configure the ASA to validate certificates used for TLS functions by performing RFC 5280- compliant certification path validation as shown in the example below.

ASA2(config)# crypto ca trustpoint CA_X
ASA2(config-ca-trustpoint)# validation-usage ssl-client 
ASA2(config-ca-trustpoint)# validation-usage ipsec-client