The F5 BIG-IP appliance providing intermediary services for remote access must use FIPS-validated cryptographic algorithms, including TLS 1.2 at a minimum.

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
high	V-266139	SRG-NET-000062-ALG-000011	F5BI-AP-300003	SV-266139r1024837_rule	2024-09-20	1

Description
Without confidentiality protection mechanisms, unauthorized individuals may gain access to sensitive information via a remote access session. Remote access is access to DOD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include broadband and wireless connections. Remote access methods include, for example, proxied remote encrypted traffic (e.g., TLS gateways, web content filters, and webmail proxies). Encryption provides a means to secure the remote connection to prevent unauthorized access to the data traversing the remote access connection, thereby providing a degree of confidentiality. The encryption strength of the mechanism is selected based on the security categorization of the information. This requirement applies to ALGs providing remote access proxy services as part of its intermediary services (e.g., OWA or SSL VPN gateway). Satisfies: SRG-NET-000062-ALG-000011, SRG-NET-000062-ALG-000150, SRG-NET-000063-ALG-000012, SRG-NET-000230-ALG-000113, SRG-NET-000355-ALG-000117

Description

Without confidentiality protection mechanisms, unauthorized individuals may gain access to sensitive information via a remote access session. Remote access is access to DOD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include broadband and wireless connections. Remote access methods include, for example, proxied remote encrypted traffic (e.g., TLS gateways, web content filters, and webmail proxies). Encryption provides a means to secure the remote connection to prevent unauthorized access to the data traversing the remote access connection, thereby providing a degree of confidentiality. The encryption strength of the mechanism is selected based on the security categorization of the information. This requirement applies to ALGs providing remote access proxy services as part of its intermediary services (e.g., OWA or SSL VPN gateway). Satisfies: SRG-NET-000062-ALG-000011, SRG-NET-000062-ALG-000150, SRG-NET-000063-ALG-000012, SRG-NET-000230-ALG-000113, SRG-NET-000355-ALG-000117

ℹ️ Check
If the BIG-IP appliance does not provide intermediary services for remote access (e.g., web content filter, TLS, and webmail), TLS, or application protocols that use TLS (e.g., DNSSEC or HTTPS), this is not applicable. Client SSL Profile From the BIG-IP GUI: 1. Local Traffic. 2. Profiles. 3. SSL. 4. Client. 5. Click on the name of the SSL Profile. 6. Change "Configuration" to "Advanced". 7. Verify "Ciphers" is configured to use NIST FIPS-validated ciphers. 8. Repeat for other SSL Profiles in use. Virtual Server From the BIG-IP GUI: 1. Local Traffic. 2. Virtual Servers. 3. Virtual Server List. 4. Click the name of the virtual server. 5. Verify that the "SSL Profile (Client)" is using a NIST FIPS-validated SSL Profile. 6. Repeat these steps to review all other virtual servers. If the BIG-IP appliance is not configured to use TLS 1.2 or higher, this is a finding.

ℹ️ Check

If the BIG-IP appliance does not provide intermediary services for remote access (e.g., web content filter, TLS, and webmail), TLS, or application protocols that use TLS (e.g., DNSSEC or HTTPS), this is not applicable. Client SSL Profile From the BIG-IP GUI: 1. Local Traffic. 2. Profiles. 3. SSL. 4. Client. 5. Click on the name of the SSL Profile. 6. Change "Configuration" to "Advanced". 7. Verify "Ciphers" is configured to use NIST FIPS-validated ciphers. 8. Repeat for other SSL Profiles in use. Virtual Server From the BIG-IP GUI: 1. Local Traffic. 2. Virtual Servers. 3. Virtual Server List. 4. Click the name of the virtual server. 5. Verify that the "SSL Profile (Client)" is using a NIST FIPS-validated SSL Profile. 6. Repeat these steps to review all other virtual servers. If the BIG-IP appliance is not configured to use TLS 1.2 or higher, this is a finding.

✔️ Fix
Client SSL Profile From the BIG-IP GUI: 1. Local Traffic. 2. Profiles. 3. SSL. 4. Client. 5. Click on the name of the SSL Profile. 6. Change "Configuration" to "Advanced". 7. Configure "Ciphers" to use NIST FIPS-validated ciphers. 8. Click "Update". 9. Repeat for other SSL Profiles in use. Virtual Server From the BIG-IP GUI: 1. Local Traffic. 2. Virtual Servers. 3. Virtual Server List. 4. Click the name of the virtual server. 5. Configure "SSL Profile (Client)" to use a NIST FIPS-validated SSL Profile. 6. Click "Update". 7. Repeat for other virtual servers.

✔️ Fix

Client SSL Profile From the BIG-IP GUI: 1. Local Traffic. 2. Profiles. 3. SSL. 4. Client. 5. Click on the name of the SSL Profile. 6. Change "Configuration" to "Advanced". 7. Configure "Ciphers" to use NIST FIPS-validated ciphers. 8. Click "Update". 9. Repeat for other SSL Profiles in use. Virtual Server From the BIG-IP GUI: 1. Local Traffic. 2. Virtual Servers. 3. Virtual Server List. 4. Click the name of the virtual server. 5. Configure "SSL Profile (Client)" to use a NIST FIPS-validated SSL Profile. 6. Click "Update". 7. Repeat for other virtual servers.