The F5 BIG-IP appliance providing remote access intermediary services must be configured to route sessions to an IDPS for inspection.

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
medium	V-266173	SRG-NET-000512-ALG-000062	F5BI-AP-300162	SV-266173r1024854_rule	2024-09-20	1

Description
Remote access devices, such as those providing remote access to network devices and information systems, which lack automated, capabilities increase risk and makes remote user access management difficult at best. 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. Automated monitoring of remote access sessions allows organizations to detect cyberattacks and ensure ongoing compliance with remote access policies by auditing connection activities of remote access capabilities, from a variety of information system components (e.g., servers, workstations, notebook computers, smart phones, and tablets).

Description

Remote access devices, such as those providing remote access to network devices and information systems, which lack automated, capabilities increase risk and makes remote user access management difficult at best. 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. Automated monitoring of remote access sessions allows organizations to detect cyberattacks and ensure ongoing compliance with remote access policies by auditing connection activities of remote access capabilities, from a variety of information system components (e.g., servers, workstations, notebook computers, smart phones, and tablets).

ℹ️ Check
If the BIG-IP appliance does not provide remote access intermediary services, this is not applicable. Verify one of these two options are configured: 1. The network architecture routes traffic inline from the BIG-IP through an IDPS. 2. A Protocol Inspection Profile is configured on the Virtual Server. From the BIG-IP GUI: 1. Local Traffic. 2. Virtual Servers. 3. Virtual Server List. 4. Click on the name of the Virtual Server. 5. Security >> Policies tab. 6. Verify "Protocol Inspection Profile" is set to "Enabled" and the "Profile" drop-down is set to the appropriate value. If the BIG-IP appliance is not configured to route sessions to an IDPS for inspection, this is a finding.

ℹ️ Check

If the BIG-IP appliance does not provide remote access intermediary services, this is not applicable. Verify one of these two options are configured: 1. The network architecture routes traffic inline from the BIG-IP through an IDPS. 2. A Protocol Inspection Profile is configured on the Virtual Server. From the BIG-IP GUI: 1. Local Traffic. 2. Virtual Servers. 3. Virtual Server List. 4. Click on the name of the Virtual Server. 5. Security >> Policies tab. 6. Verify "Protocol Inspection Profile" is set to "Enabled" and the "Profile" drop-down is set to the appropriate value. If the BIG-IP appliance is not configured to route sessions to an IDPS for inspection, this is a finding.

✔️ Fix
Configure one of these two options: 1. Configure the network architecture to route traffic inline from the BIG-IP through an IDPS. 2. Configure a Protocol Inspection Profile on the Virtual Server. From the BIG-IP GUI: 1. Local Traffic. 2. Virtual Servers. 3. Virtual Server List. 4. Click on the name of the Virtual Server. 5. Security >> Policies tab. 6. Set "Protocol Inspection Profile" to "Enabled". 7. Set the "Profile" drop-down to the appropriate value. Note: To create a Protocol Inspection Profile, go to Security >> Protocol Security >> Inspection Profiles. 8. Click "Update".

✔️ Fix

Configure one of these two options: 1. Configure the network architecture to route traffic inline from the BIG-IP through an IDPS. 2. Configure a Protocol Inspection Profile on the Virtual Server. From the BIG-IP GUI: 1. Local Traffic. 2. Virtual Servers. 3. Virtual Server List. 4. Click on the name of the Virtual Server. 5. Security >> Policies tab. 6. Set "Protocol Inspection Profile" to "Enabled". 7. Set the "Profile" drop-down to the appropriate value. Note: To create a Protocol Inspection Profile, go to Security >> Protocol Security >> Inspection Profiles. 8. Click "Update".