Bug ID 753295: ASM REST: All signatures being returned for policy Signatures regardless of signature sets

Last Modified: Jul 12, 2023

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

Known Affected Versions:
14.1.0, 14.1.0.1

Fixed In:
15.0.0, 14.1.0.2

Opened: Dec 17, 2018

Severity: 3-Major

Symptoms

By default, only signatures that are included in the Security Policy enforcement via the Policy's Signature Sets are included in the response to /tm/asm/policies/<ID>/signatures. Additionally, there should be the capability to $filter for either signatures that are in the policy or not in the policy. These filters are not working

Impact

More data that expected will be returned to REST clients which may cause confusion. Learning statistics/graphs may have confusing/incorrect numbers.

Conditions

ASM REST/GUI is used to determine the number of signatures enabled on a Security Policy

Workaround

None

Fix Information

inPolicy $filter works again, and the default behavior only returns the signatures that are in the policy.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips