Delivery
Review events
Security logging is deliberately best-effort: writing an event should never be the reason a legitimate or blocked request fails outright.
How it works
- Security operations shows the event log — filter by event name or IP, page through history, unblock from the row
- Twelve event types cover every enforcement decision — WAF, paths, blocks, policies, rate limits, and the block actions themselves
- Event writes are swallowed on failure — logging is best-effort, enforcement is fail-closed, and the two never trade places
Good to know
- Use the event log to tell a one-off false positive from a pattern worth acting on — blocking the source IP or raising the rate limit