Bug ID 582133: Policy builder doesn't enable staging after policy change on "*" entities (file types, urls, etc.)

Last Modified: Oct 01, 2018

Bug Tracker

Affected Product:  See more info
BIG-IP ASM(all modules)

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2

Fixed In:
13.0.0, 12.1.2

Opened: Mar 21, 2016
Severity: 3-Major

Symptoms

When conditions of "Track Site Change" settings are met the staging flag on "*" entities is supposed to be turned ON in order to learn sub-sequences of site changes without blocking traffic. However it doesn't happen. The staging flag stays OFF.

Impact

in a situation when the protected Web application was changed, ASM can block traffic when it should not be blocked.

Conditions

Staging was set OFF on "*" entity. After that conditions of "Track Site Change" settings are met.

Workaround

Staging flag can be changed manually via GUI

Fix Information

The problem was a sub-sequence of other code changes. The code was fixed he way it should count for "Track Site Change" conditions and change Staging flag when it is needed.

Behavior Change