Closed yogibear15 closed 11 months ago
ASM's (and Silverline's) sensitive parameter setting == 'mask value in logs' in XC. By default, the 'password' parameter is marked sensitive.
When converting a policy from ASM/SL, the sensitive parameter 'password' is defined in XC service policy not as a parameter but as a cookie:
The expected behavior is for the Type to Parameter, not Cookie.
Not only cookies in my case the parameter named password is added as an HTTP header for some reason in the WAF XC policy.
Will need to check again after the updates.
Fixed in the latest release.
ASM's (and Silverline's) sensitive parameter setting == 'mask value in logs' in XC. By default, the 'password' parameter is marked sensitive.
When converting a policy from ASM/SL, the sensitive parameter 'password' is defined in XC service policy not as a parameter but as a cookie:
The expected behavior is for the Type to Parameter, not Cookie.