The F5 BIG-IP must be configured to identify and authenticate all endpoint devices or peers before establishing a connection.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-266171F5BI-AP-300160SV-266171r1024403_ruleCCI-000366medium
Description
Without identifying and authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity.
STIGDate
F5 BIG-IP TMOS ALG Security Technical Implementation Guide2025-06-09

Related Frameworks

4 paths across 3 frameworks
NIST 800-531 mapping
CM-6
1.00
  • DISA · V1R2 · disa_xccdf · related
  • DISA · 2025-01-23 · disa_cci_list · equivalent
NIST 800-1712 mappings
3.4.1
1.00
  • DISA · V1R2 · disa_xccdf · related
  • DISA · 2025-01-23 · disa_cci_list · equivalent
  • NIST · Rev 2 (Feb 2020, errata Jan 2021) · nist_800_171_app_d · equivalent
3.4.2
1.00
  • DISA · V1R2 · disa_xccdf · related
  • DISA · 2025-01-23 · disa_cci_list · equivalent
  • NIST · Rev 2 (Feb 2020, errata Jan 2021) · nist_800_171_app_d · equivalent
CCI1 mapping
CCI-000366
1.00
  • DISA · V1R2 · disa_xccdf · related

Details

Check Text (C-266171r1024403_chk)

If the BIG-IP appliance does not provide remote access intermediary services, this is not applicable. From the BIG-IP GUI: 1. Access. 2. Profiles/Policies. 3. Access Profiles. 4. Click "Edit..." in the "Per-Session Policy" column for the Access Profile. 5. Verify the Access Profile is configured to uniquely identify network devices. If the BIG-IP appliance is not configured to identify and authenticate all endpoint devices or peers before establishing a connection, this is a finding.

Fix Text (F-69998r1023760_fix)

From the BIG-IP GUI: 1. Access. 2. Profiles/Policies. 3. Access Profiles. 4. Click "Edit..." in the "Per-Session Policy" column for the Access Profile. 5. Configure the Access Profile to uniquely identify and authenticate network devices. 6. Click "Apply Access Policy".