Bug ID 789513: User-defined ASM signature ids can be different on BIG-IQ virtual server BIG-IP

Last Modified: May 22, 2020

Bug Tracker

Affected Product:  See more info
BIG-IQ Web App Security (ASM)(all modules)

Known Affected Versions:
5.0.0, 5.0.0 HF1, 5.1.0, 5.2.0, 5.4.0, 5.4.0 HF1, 5.4.0 HF2, 6.0.0, 6.0.1, 6.0.1.1, 6.1.0, 7.0.0, 7.0.0.1

Opened: Jun 04, 2019
Severity: 4-Minor

Symptoms

User-defined ASM signature ids can be different on BIG-IQ virtual server BIG-IP and cause information on event logs to be wrong or missing.

Impact

User-defined ASM signature information on event logs wrong or missing

Conditions

Have two BIG-IP devices and a different user-defined ASM signature on each. Discover & import both devices to BIG-IQ. On BIG-IQ, one signature (the first) got signatureId that match the BIG-IP (30000000) but the second one will have signatureId that ends with '1' because signatureId is unique. When an event that triggered by the second user-defined signature is logged to BIG-IQ, BIG-IQ will show the signature by its signature id which is a different signature on BIG-IQ.

Workaround

None

Fix Information

None

Behavior Change