Last Modified: Jul 12, 2023
Known Affected Versions:
Opened: Dec 17, 2018 Severity: 3-Major
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
More data that expected will be returned to REST clients which may cause confusion. Learning statistics/graphs may have confusing/incorrect numbers.
ASM REST/GUI is used to determine the number of signatures enabled on a Security Policy
inPolicy $filter works again, and the default behavior only returns the signatures that are in the policy.