Loading...

CDN.com.tr Help

Read WAF logs

Use WAF logs to explain blocked or challenged traffic without exposing internal log systems.

Read WAF logs

Use WAF logs to explain blocked or challenged traffic without exposing internal log systems.

Panel path

  1. Management Panel
  2. CDN Accounts
  3. Advanced Management WAF
  4. WAF Logs
  5. Support escalation

Prerequisites

  • WAF log query must be limited by selected account and time range.
  • IP, domain, and request details are treated as data fields in screenshots.
  • If no log is found, filter/range checks are shown to the user.

Step-by-step guide

1

Filter WAF logs

Blocked/challenged traffic is explained from customer-facing screens without internal log-system access.

  • Open WAF Logs.
  • Filter by domain, time range, and optionally IP/path.

Expected result: Only selected-account security events are listed.

cdnctl equivalent
cdnctl waf logs list --account <account_uuid> --since 1h
2

Choose the action

For a false positive, adjust the rule or open support; for real attack traffic, keep block/challenge.

  • Read action and rule name.
  • Return to cache/security rule settings if needed.
  • Share timestamp and masked request detail in support ticket.

Expected result: The customer safely understands why a request was blocked.

cdnctl equivalent
cdnctl cdn security rules list --account <account_uuid>

Verification

  • Log response does not include another account event.
  • IP/path data is redacted in docs.
  • Internal log host or service name does not appear in customer guides.

Use cases

A customer reports a request that is blocked by security rules.

Quick workflow

  1. Open WAF logs.
  2. Filter by time/domain/IP.
  3. Inspect action and rule.
  4. Adjust rule or open support ticket.

Checks

  • Selected account has a WAF route.
  • Log query does not leak another account.
  • Support guidance includes timestamp and request details.

Related pages

Purge cached content

Purge a path, saved path, or the whole account and separate CDN cache from browser cache.