Skip to content
Sample workspace. All evidence is fictional. Feedback and results last for this page session only. No infrastructure account is connected.

Assessment · assets.example.com

2 things to fix

September 1–7, 2026 · Seven complete UTC days

Request a free review

To fix

2

Plus 1 option for the item above

Rule coverage

4 of 5

Bot evidence needs confirmation

We never change anything.

Read-only

2 things to fix

Managed firewall rules aren't protecting assets.example.com

Managed firewall rules aren't protecting assets.example.com. Run a new scan to see exactly why and how to fix it.

Next step

Run a new scan.

More details
SecurityHigh confidenceHigh priority

Impact

Effort & risk

.

How to measure

Rescan after deployment and review false positives and application error rates.

Assumptions

  • Checked: zone and account managed-firewall entry points. None has an enabled rule that runs a managed ruleset for this site. This can mean no rules exist, all are switched off, or they target other sites only.
  • Deployment absence does not prove an attack occurred.
  • Paid entitlement and commercial value require separate confirmation.

Evidence

  • Zone inventory

    Fictional active zone: assets.example.com.

  • Customer confirmation

    Fictional customer marked this scope production and non-test.

  • Zone managed-WAF entrypoint

    Fixture confirms readable zone scope with no effective deployment.

  • Applicable account managed-WAF entrypoint

    Fixture confirms readable account scope with no applicable deployment.

  • HTTP analytics

    500,000 eyeball requests; 12 GB response bytes; seven complete UTC days; unsampled fixture.

Rule EDGE-001 · Version 2026-10-21.1 · All sources are sample fixtures.

Most static files skip the cache on assets.example.com

58% of requests for images, scripts and styles on assets.example.com went to your server instead of the cache.

Next step

Add a cache rule for static files on assets.example.com.

More details
PerformanceHigh confidenceHigh priority

Impact

116,000 static requests reached your server in 7 days.

Effort & risk

About 30 minutes. Low risk. Clear the cache if anything looks out of date.

How to measure

Compare origin-contact share in equivalent seven-day windows after the change.

Assumptions

  • MISS, EXPIRED, and REVALIDATED indicate origin contact, not guaranteed avoidable traffic.
  • The cohort is confirmed public and static; intentional bypass is excluded.
  • MISS/EXPIRED traffic persists on at least three distinct days in the cohort, not necessarily for the same object.
  • The owner confirmed that purges, deployments, development mode, or cache-policy changes do not explain the window’s misses.

Evidence

  • Zone inventory

    Fictional active zone: assets.example.com.

  • Customer confirmation

    Fictional customer marked this scope production and non-test.

  • HTTP analytics

    500,000 eyeball requests; 12 GB response bytes; seven complete UTC days; unsampled fixture.

  • Cache cohort and configuration review

    200,000 confirmed public static requests; 116,000 origin contacts; 105,000 MISS/EXPIRED. Repeated misses and cache intent confirmed; private/API/auth traffic excluded.

Rule EDGE-007 · Version 2026-10-21.1 · All sources are sample fixtures.

Option for the item above: Tiered caching is off for assets.example.com

Tiered caching is off, so every cache miss goes straight to your server.

Turn on tiered caching.

105,000 cache misses reached your server in 7 days.

Risk: Low risk.

Measure: Compare origin fetches, latency, and errors across equivalent windows.

Coverage & limitations

EDGE-008 · No finding

No referenced load-balancer pools in the covered scope.

EDGE-003 · Needs evidence

Owner confirmation of Enterprise bot analysis entitlement and edge functions signal use is required.

Request a free review