F5BI-LT-000083 - The BIG-IP Core implementation must be configured to validate certificates used for TLS functions for connections to virtual servers by constructing a certification path (which includes status information) to an accepted trust anchor.

Warning! Audit Deprecated

This audit has been deprecated and will be removed in a future update.

View Next Audit Version


A trust anchor is an authoritative entity represented via a public key. Within a chain of trust, the top entity to be trusted is the 'root certificate' or 'trust anchor' such as a Certification Authority (CA). A certification path starts with the subject certificate and proceeds through a number of intermediate certificates up to a trusted root certificate, typically issued by a trusted CA. Path validation is necessary for a relying party to make an informed trust decision when presented with any certificate not already explicitly trusted.

Deploying the ALG with TLS enabled may require the CA certificates for each proxy to be used for TLS traffic decryption/encryption. The installation of these certificates in each trusted root certificate store is used by proxied applications and browsers on each client.

NOTE: Nessus has provided the target output to assist in reviewing the benchmark to ensure target compliance.


If intermediary services for TLS are provided, configure the BIG-IP Core to validate certificates used for TLS functions by constructing a certification path with status information to an accepted trust anchor.

See Also


Item Details


References: 800-53|SC-17, CAT|II, CCI|CCI-000185, Rule-ID|SV-215762r557356_rule, STIG-ID|F5BI-LT-000083, STIG-Legacy|SV-74735, STIG-Legacy|V-60305, Vuln-ID|V-215762

Plugin: F5

Control ID: a9c50b9ca2399a56574296a2836ee0608678ecf545f5f2ea9aac7267bf4e3114