The F5 BIG-IP appliance providing content filtering must detect use of network services that have not been authorized or approved by the information system security manager (ISSM) and information system security officer (ISSO), at a minimum.

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
medium	V-266160	SRG-NET-000384-ALG-000136	F5BI-AP-300068	SV-266160r1024389_rule	2024-09-20	1

Description
Unauthorized or unapproved network services lack organizational verification or validation, and therefore may be unreliable or serve as malicious rogues for valid services. Examples of network services include service-oriented architectures (SOAs), cloud-based services (e.g., infrastructure as a service, platform as a service, or software as a service), cross-domain, Voice Over Internet Protocol, Instant Messaging, auto-execute, and file sharing. To comply with this requirement, the ALG may be configured to detect services either directly or indirectly (i.e., by detecting traffic associated with a service). This requirement applies to gateways/firewalls that perform content inspection or have higher-layer proxy functionality.

Description

Unauthorized or unapproved network services lack organizational verification or validation, and therefore may be unreliable or serve as malicious rogues for valid services. Examples of network services include service-oriented architectures (SOAs), cloud-based services (e.g., infrastructure as a service, platform as a service, or software as a service), cross-domain, Voice Over Internet Protocol, Instant Messaging, auto-execute, and file sharing. To comply with this requirement, the ALG may be configured to detect services either directly or indirectly (i.e., by detecting traffic associated with a service). This requirement applies to gateways/firewalls that perform content inspection or have higher-layer proxy functionality.

ℹ️ Check
If the BIG-IP appliance does not perform content filtering as part of the traffic management functions, this is not applicable. If using the BIG-IP AFM module to perform content filtering: AFM ACL: From the BIG-IP GUI: 1. Security. 2. Network Firewall. 3. Policies. 4. <Policy Name>. 5. Verify a rule is configured that uses a "Classification Policy". Log Profile: From the BIG-IP GUI: 1. Security. 2. Event Logs. 3. Logging Profiles. 4. Edit the global-network profile. 5. Classification tab. 6. Verify the Log Publisher is set to the desired setting. (For production environments, F5 recommends using remote logging.) If configured rules in the policy do not detect use of network services that have not been authorized or approved by the ISSM and ISSO, at a minimum, this is a finding.

ℹ️ Check

If the BIG-IP appliance does not perform content filtering as part of the traffic management functions, this is not applicable. If using the BIG-IP AFM module to perform content filtering: AFM ACL: From the BIG-IP GUI: 1. Security. 2. Network Firewall. 3. Policies. 4. <Policy Name>. 5. Verify a rule is configured that uses a "Classification Policy". Log Profile: From the BIG-IP GUI: 1. Security. 2. Event Logs. 3. Logging Profiles. 4. Edit the global-network profile. 5. Classification tab. 6. Verify the Log Publisher is set to the desired setting. (For production environments, F5 recommends using remote logging.) If configured rules in the policy do not detect use of network services that have not been authorized or approved by the ISSM and ISSO, at a minimum, this is a finding.

✔️ Fix
AFM ACL: From the BIG-IP GUI: 1. Security. 2. Network Firewall. 3. Policies. 4. <Policy Name>. 5. Configure a rule that uses a "Classification Policy". Note: To create a Classification Policy, go to Traffic Intelligence >> Policies. 6. Click "Commit Changes to System". Log Profile: From the BIG-IP GUI: 1. Security. 2. Event Logs. 3. Logging Profiles. 4. Edit the global-network profile. 5. Check "Enabled" for "Classification". 6. Classification tab. 7. Configure the Log Publisher. (For production environments, F5 recommends using remote logging.) 8. Click "Update".

✔️ Fix

AFM ACL: From the BIG-IP GUI: 1. Security. 2. Network Firewall. 3. Policies. 4. <Policy Name>. 5. Configure a rule that uses a "Classification Policy". Note: To create a Classification Policy, go to Traffic Intelligence >> Policies. 6. Click "Commit Changes to System". Log Profile: From the BIG-IP GUI: 1. Security. 2. Event Logs. 3. Logging Profiles. 4. Edit the global-network profile. 5. Check "Enabled" for "Classification". 6. Classification tab. 7. Configure the Log Publisher. (For production environments, F5 recommends using remote logging.) 8. Click "Update".