Bug ID 874185: Incorrect Alarm/Block flags displayed for Signature with previously enforced rule

Last Modified: Apr 17, 2024

Affected Product(s):
BIG-IP ASM(all modules)

Known Affected Versions:
14.1.2,,,,,,,,, 14.1.3,, 14.1.4,,,,,,, 15.0.0, 15.0.1,,,,, 15.1.0,,,,,, 15.1.1, 15.1.2,, 15.1.3,, 15.1.4,, 15.1.5,, 15.1.6,, 15.1.7, 15.1.8,,, 15.1.9,, 15.1.10,,,, 16.0.0,, 16.0.1,,

Fixed In:

Opened: Jan 29, 2020

Severity: 3-Major


When Signature Staging is disabled globally, signatures containing previously enforced rules are displayed with Alarm/Block flags set to 'No'. This occurs even if the signature is fully enabled and the associated Set is set to Learn/Alarm/Block.


The signature appears in the Attack Signature GUI page as having alarm and blocking disabled, although the signature does block correctly.


-- Signature Staging is disabled globally. -- A signature has a previously enforced rule. This occurs when an F5-provided signature is taken out of staging, and the signature is then updated by ASU.



Fix Information


Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips