Bug ID 611151: An upper case JSON sensitive parameter is not masked when ASM policy is case-insensitive

Last Modified: Aug 19, 2026

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

Known Affected Versions:
12.1.0, 12.1.0 hf1, 12.1.0 hf2, 12.1.1, 12.1.1 hf1, 12.1.1 hf2, 12.1.2, 12.1.2 hf1, 12.1.2 hf2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6

Fixed In:
13.0.0

Opened: Aug 16, 2016

Severity: 3-Major

Symptoms

If you configure a sensitive parameter with an upper-case character (like "Password"), the data masking does not take place. When the sensitive parameter is all lower-case (like "password"), the data masking takes place as expected.

Impact

no data masking for a JSON sensitive parameter

Conditions

ASM provisioned ASM policy is case-insensitive JSON profile, w/ a sensitive parameter with an upper-case character

Workaround

N/A

Fix Information

We've made sure that JSON parameters are always treated as case sensitive, regardless of the ASM policy case sensitivity setting.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips