Skip to content

Latest commit

 

History

History
44 lines (25 loc) · 2.63 KB

File metadata and controls

44 lines (25 loc) · 2.63 KB
pcx_content_type title weight
concept
Log the payload of matched rules
11

Log the payload of matched rules

The WAF allows you to log the request information that triggered a specific rule of a managed ruleset. This information is known as the payload. Payload logging is especially useful when diagnosing the behavior of WAF rules. Since the values that triggered a rule may contain sensitive data, they are encrypted with a customer-provided public key so that only you can examine them later.

{{

}}

This feature is only available for customers on an Enterprise plan.

{{

}}

Each managed ruleset has its own payload logging configuration. To enable the feature, configure a public key to encrypt the logged payload by doing one of the following:

  • Generate a key pair directly in the dashboard (Cloudflare will only save the generated public key)
  • Enter your own public key

Once enabled, the WAF saves the payload of any rule matches for the managed ruleset configured with payload logging, encrypting the payload with your public key.

To view the content of the payload in clear text, do one of the following:

{{

}}

All Cloudflare logs are encrypted at rest. Encrypting the payload content adds a second layer of encryption for the matched values that triggered a WAF rule.

Make sure you store your private key safely. If you lose the private key, configure payload logging with a new public key. The payload of new requests will be encrypted with the new public key.

Cloudflare cannot decrypt encrypted payloads, since this operation requires your private key. Cloudflare staff will never ask for the private key.

{{

}}

User role requirements

Only users with the Super Administrator role can enable payload logging or edit the payload logging configuration.