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

The F5 BIG-IP appliance providing content filtering must employ rate-based attack prevention behavior analysis.

DISA Rule

SV-266156r1024848_rule

Vulnerability Number

V-266156

Group Title

SRG-NET-000362-ALG-000112

Rule Version

F5BI-AP-300059

Severity

CAT II

CCI(s)

• CCI-002385 - Protect against or limit the effects of organization-defined types of denial of service events.
• CCI-001094 - Restrict the ability of individuals to launch organization-defined denial of service attacks against other systems.

Weight

10

Fix Recommendation

From the BIG-IP GUI:
1. Security.
2. DoS Protection.
3. Device Protection.
4. Expand each of the applicable families (Network, DNS, SIP) one at a time depending on the traffic being handled by the BIG-IP and do the following for each:
a. Check the box at the top of the list of signatures to select all.
b. Set "Set State" to "Mitigate".
5. Click "Commit Changes to System".

Note: Sites must operationally test or initially use learning mode prior to turning on all of the options in all families to prevent operational impacts, particularly in implementations with large traffic volumes.

Check Contents

If the BIG-IP appliance does not perform content filtering as part of the traffic management functions, this is not applicable.

From the BIG-IP GUI:
1. Security.
2. DoS Protection.
3. Device Protection.
4. Expand each of the applicable families (Network, DNS, SIP) depending on the traffic being handled by the BIG-IP and verify the "State" is set to "Mitigate" for all signatures in that family.

If the BIG-IP appliance is not configured to protect against known and unknown types of DoS attacks by employing rate-based attack prevention behavior analysis, this is a finding.

Vulnerability Number

V-266156

Documentable

False

Rule Version

F5BI-AP-300059

Severity Override Guidance

If the BIG-IP appliance does not perform content filtering as part of the traffic management functions, this is not applicable.

From the BIG-IP GUI:
1. Security.
2. DoS Protection.
3. Device Protection.
4. Expand each of the applicable families (Network, DNS, SIP) depending on the traffic being handled by the BIG-IP and verify the "State" is set to "Mitigate" for all signatures in that family.

If the BIG-IP appliance is not configured to protect against known and unknown types of DoS attacks by employing rate-based attack prevention behavior analysis, this is a finding.

Check Content Reference

M

Target Key

5640