Skip to content

Find blocked requests

Find what a WAF blocked in Observability, see which rule did it, and fix false positives.

Updated View as Markdown
  1. Turn logging on, if it isn’t, with scope matched and an environment in the WAF’s project:

    "logging": { "scope": "matched", "environment": "production" }
  2. Search the environment for the WAF’s blocks:

    ezgh obs search --environment production --service ezgh.waf --from 1h --contains '"action":"block"'

    In the console, Find blocked requests on a WAF’s Logging tab opens its logs in Observability.

  3. Read a record’s terminatingRule and matchedRules: they name the rule that blocked the request, with its set. Its path, query, clientIp and userAgent show what was sent and by whom.

To narrow it down, add --matches with a regular expression, such as "path":"/checkout, or another filter of ezgh obs search.

A legitimate request was blocked

  • By a managed rule: add a rule override for its ID, off (or log, outside ezgh/core).
  • By a custom rule: change its conditions, or add an allow rule above it for the request.
  • To check a change first: set the set’s or the WAF’s mode to log. Records then show action log for what it would have blocked.
Navigation

Type to search…

↑↓ navigate↵ selectEsc close