Bug ID 2258301: Declarative policy export encodes signatureId as a string instead of an integer

Last Modified: Sep 29, 2026

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

Known Affected Versions:
17.5.1.5, 17.5.1.6, 17.5.1.8, 17.5.1.9

Opened: Mar 26, 2026

Severity: 4-Minor

Symptoms

When a security policy is exported in declarative (JSON) format, signature identifiers are written as quoted strings (for example, "signatureId": "200204059") rather than numeric integers ("signatureId": 200204059).

Impact

Cosmetic only. The exported JSON does not match the intended schema (integer signatureId), but the string-encoded value remains valid and imports correctly on all WAF platforms, so export and import continue to function.

Conditions

A security policy is exported in declarative JSON format (for example, via the /mgmt/tm/asm/tasks/export-policy endpoint) on an affected version.

Workaround

None. The string-encoded signatureId imports successfully; no action is required. Upgrade to a version containing the fix to obtain integer encoding.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips