The F5 BIG-IP appliance that intermediary services for FTP must inspect inbound and outbound FTP communications traffic for protocol compliance and protocol anomalies.

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
medium	V-266148	SRG-NET-000512-ALG-000065	F5BI-AP-300042	SV-266148r1024375_rule	2024-09-20	1

Description
Application protocol anomaly detection examines application layer protocols such as FTP to identify attacks based on observed deviations in the normal RFC behavior of a protocol or service. This type of monitoring allows for the detection of known and unknown exploits which exploit weaknesses of commonly used protocols. Since protocol anomaly analysis examines the application payload for patterns or anomalies, an FTP proxy must be included in the ALG. This ALG will be configured to inspect inbound and outbound FTP communications traffic to detect protocol anomalies such as malformed message and command insertion attacks.

Description

Application protocol anomaly detection examines application layer protocols such as FTP to identify attacks based on observed deviations in the normal RFC behavior of a protocol or service. This type of monitoring allows for the detection of known and unknown exploits which exploit weaknesses of commonly used protocols. Since protocol anomaly analysis examines the application payload for patterns or anomalies, an FTP proxy must be included in the ALG. This ALG will be configured to inspect inbound and outbound FTP communications traffic to detect protocol anomalies such as malformed message and command insertion attacks.

ℹ️ Check
If the BIG-IP appliance does not provide intermediary/proxy services for FTP communications traffic, this is not applicable. FTP Profile: From the BIG-IP GUI: 1. Local Traffic. 2. Profiles. 3. Services. 4. FTP. 5. Click the name of the FTP profile. 6. Verify "Protocol Security" is checked. FTP Virtual Server: 1. Local Traffic. 2. Virtual Servers. 3. Virtual Server List. 4. Click the name of the FTP virtual server. 5. Verify the FTP profile is selected in the "FTP Profile" drop-down list. If the BIG-IP appliance is not configured to inspect inbound and outbound FTP communications traffic for protocol compliance and protocol anomalies, this is a finding.

ℹ️ Check

If the BIG-IP appliance does not provide intermediary/proxy services for FTP communications traffic, this is not applicable. FTP Profile: From the BIG-IP GUI: 1. Local Traffic. 2. Profiles. 3. Services. 4. FTP. 5. Click the name of the FTP profile. 6. Verify "Protocol Security" is checked. FTP Virtual Server: 1. Local Traffic. 2. Virtual Servers. 3. Virtual Server List. 4. Click the name of the FTP virtual server. 5. Verify the FTP profile is selected in the "FTP Profile" drop-down list. If the BIG-IP appliance is not configured to inspect inbound and outbound FTP communications traffic for protocol compliance and protocol anomalies, this is a finding.

✔️ Fix
FTP Profile: From the BIG-IP GUI: 1. Local Traffic. 2. Profiles. 3. Services. 4. FTP. 5. Click the name of the FTP profile. 6. Check "Protocol Security". 7. Click "Update". FTP Virtual Server: 1. Local Traffic. 2. Virtual Servers. 3. Virtual Server List. 4. Click the name of the FTP virtual server. 5. Select the FTP profile from the "FTP Profile" drop-down list. 6. Click "Update". Refer to vendor documentation for more information.

✔️ Fix

FTP Profile: From the BIG-IP GUI: 1. Local Traffic. 2. Profiles. 3. Services. 4. FTP. 5. Click the name of the FTP profile. 6. Check "Protocol Security". 7. Click "Update". FTP Virtual Server: 1. Local Traffic. 2. Virtual Servers. 3. Virtual Server List. 4. Click the name of the FTP virtual server. 5. Select the FTP profile from the "FTP Profile" drop-down list. 6. Click "Update". Refer to vendor documentation for more information.