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

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
medium	V-266147	SRG-NET-000512-ALG-000064	F5BI-AP-300041	SV-266147r1024374_rule	2024-09-20	1

Description
Application protocol anomaly detection examines application layer protocols such as SMTP 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 SMTP proxy must be included in the ALG. This ALG will be configured to inspect inbound and outbound SMTP and extended SMTP 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 SMTP 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 SMTP proxy must be included in the ALG. This ALG will be configured to inspect inbound and outbound SMTP and extended SMTP 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 SMTP communications traffic, this is not applicable. SMTP Profile: From the BIG-IP GUI: 1. Local Traffic. 2. Profiles. 3. Services. 4. SMTP. 5. Click the name of the SMTP profile. 6. Verify "Protocol Security" is checked. SMTP Virtual Server: 1. Local Traffic. 2. Virtual Servers. 3. Virtual Server List. 4. Click the name of the SMTP virtual server. 5. Verify the SMTP profile is selected in the "SMTP Profile" drop-down list. If the BIG-IP appliance is not configured to inspect inbound and outbound SMTP and Extended SMTP 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 SMTP communications traffic, this is not applicable. SMTP Profile: From the BIG-IP GUI: 1. Local Traffic. 2. Profiles. 3. Services. 4. SMTP. 5. Click the name of the SMTP profile. 6. Verify "Protocol Security" is checked. SMTP Virtual Server: 1. Local Traffic. 2. Virtual Servers. 3. Virtual Server List. 4. Click the name of the SMTP virtual server. 5. Verify the SMTP profile is selected in the "SMTP Profile" drop-down list. If the BIG-IP appliance is not configured to inspect inbound and outbound SMTP and Extended SMTP communications traffic for protocol compliance and protocol anomalies, this is a finding.

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

✔️ Fix

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