Bug ID 726090: No Bot Defense Logs when ASM Policy is used without Proactive Bot Defense

Last Modified: Jul 12, 2023

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

Known Affected Versions:
13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4

Fixed In:
14.0.0.5, 13.1.1.2

Opened: Jun 28, 2018

Severity: 2-Critical

Symptoms

Device ID challenges are not logged in the Bot Defense Request Log (local and remote) when associating the Bot Defense logging profile to the virtual server.

Impact

There are no logs to show the browser challenges and the requests from clients that do not support JavaScript.

Conditions

-- Device ID is enabled on the ASM Policy. -- DoS profile with Proactive Bot Defense is not associated with the virtual server.

Workaround

There is no workaround at this time.

Fix Information

Requests are now logged to the Bot Defense Request Log with Device ID enabled on the ASM Policy and no associated DoS profile.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips