STIGQter: STIG Summary: F5 BIG-IP TMOS ALG Security Technical Implementation Guide Version: 1 Release: 3 Benchmark Date: 01 Jul 2026:

To protect against data mining, the F5 BIG-IP appliance providing content filtering must prevent code injection attacks launched against application objects including, at a minimum, application URLs and application code.

DISA Rule

SV-266141r1024839_rule

Vulnerability Number

V-266141

Group Title

SRG-NET-000318-ALG-000151

Rule Version

F5BI-AP-300007

Severity

CAT II

CCI(s)

• CCI-002346 - Employs organization-defined data mining prevention techniques for organization-defined data storage objects to protect against unauthorized data mining.
• CCI-002347 - Employ organization-defined data mining detection techniques for organization-defined data storage objects to detect data mining attempts.

Weight

10

Fix Recommendation

From the BIG-IP GUI:
1. Security.
2. Application Security.
3. Security Policies.
4. Policies List.
5. Click the name of the policy.
6. Set "Enforcement Mode" to "Blocking".
7. Select "Attack Signatures".
8. Click the filter at the top left of the signatures window.
9. Select "Buffer Overflow" in the "Attack Type" field and click "Apply".
10. Select all signatures in the filtered list and click "Enforce".
11. Click "Enforce" again.
12. Click the filter at the top left of the signatures window.
13. Select "Server Side Code Injection" in the "Attack Type" field and click "Apply".
14. Select all signatures in the filtered list and click "Enforce".
15. Click "Enforce" again.
16. Click "Apply Policy".

Check Contents

If the ALG does not perform content filtering as part of the traffic management functions, this is not applicable.

From the BIG-IP GUI:
1. Security.
2. Application Security.
3. Security Policies.
4. Policies List.
5. Click the name of the policy.
6. Verify "Enforcement Mode" is set to "Blocking".
7. Select "Attack Signatures".
8. Click the filter at the top left of the signatures window.
9. Select "Buffer Overflow" in the "Attack Type" field and click "Apply".
10. Verify "Block" is checked for all signatures and "Status" is set to "Enforced".
11. Click the filter at the top left of the signatures window.
12. Select "Server Side Code Injection" in the "Attack Type" field and click "Apply".
13. Verify "Block" is checked for all signatures and "Status" is set to "Enforced".

If the BIG-IP appliance is not configured to prevent code injection attacks launched against application objects including, at a minimum, application URLs and application code, this is a finding.

Vulnerability Number

V-266141

Documentable

False

Rule Version

F5BI-AP-300007

Severity Override Guidance

If the ALG does not perform content filtering as part of the traffic management functions, this is not applicable.

From the BIG-IP GUI:
1. Security.
2. Application Security.
3. Security Policies.
4. Policies List.
5. Click the name of the policy.
6. Verify "Enforcement Mode" is set to "Blocking".
7. Select "Attack Signatures".
8. Click the filter at the top left of the signatures window.
9. Select "Buffer Overflow" in the "Attack Type" field and click "Apply".
10. Verify "Block" is checked for all signatures and "Status" is set to "Enforced".
11. Click the filter at the top left of the signatures window.
12. Select "Server Side Code Injection" in the "Attack Type" field and click "Apply".
13. Verify "Block" is checked for all signatures and "Status" is set to "Enforced".

If the BIG-IP appliance is not configured to prevent code injection attacks launched against application objects including, at a minimum, application URLs and application code, this is a finding.

Check Content Reference

M

Target Key

5640