SensitiveLogProfile
{
"header_field_rules": [
{
"action": "string",
"enabled": false,
"index": 0,
"match": {
"match_criteria": "string",
"match_str": [
"string"
],
"string_group_refs": [
"string"
]
},
"name": "string"
}
],
"uri_query_field_rules": [
{
"action": "string",
"enabled": false,
"index": 0,
"match": {
"match_criteria": "string",
"match_str": [
"string"
],
"string_group_refs": [
"string"
]
},
"name": "string"
}
],
"waf_field_rules": [
{
"action": "string",
"enabled": false,
"index": 0,
"match": {
"match_criteria": "string",
"match_str": [
"string"
],
"string_group_refs": [
"string"
]
},
"name": "string"
}
]
}
Match sensitive header fields in HTTP application log. Field introduced in 17.2.10, 18.1.2. Allowed in Enterprise edition with any value, Essentials, Basic, Enterprise with Cloud Services edition.
Match sensitive URI query params in HTTP application log. Query params from the URI are extracted and checked for matching sensitive parameter names. A successful match will mask the parameter values in accordance with this rule action. Field introduced in 20.1.7, 21.1.2. Allowed in Enterprise edition with any value, Enterprise with Cloud Services edition.
Match sensitive WAF log fields in HTTP application log. Field introduced in 17.2.13, 18.1.3. Allowed in Enterprise edition with any value, Essentials, Basic, Enterprise with Cloud Services edition.