A web application firewall dashboard can look reassuring: thousands of blocked requests, familiar attack names, and a line moving in the right direction. None of those numbers answers the question a business is actually paying to resolve. Can an unauthorized person reach customer data, change a transaction, or interrupt an important service?

Start by mapping what the WAF protects and which routes bypass it. Then test the application behind it. A blocked-request count can help describe traffic, but it cannot show whether customer data is protected.

Separate a request reaching the application from an exploit succeeding

A request can pass the firewall and still be harmless because the application rejects it, treats it as ordinary data, or has no vulnerable component. Conversely, a successful account-to-account data request may look completely normal to an attack-pattern detector. The outcome has to be established at the application.

Cloudflare’s September 29 account of adaptive WAF testing describes treating unblocked requests as leads to investigate. The company used human review to establish what those requests actually did. Ask for the same validation in your assessment report.

Ask the assessor to classify observations precisely. Was the request rejected at the edge? Did it reach the origin? Did the application perform an unauthorized action? What evidence establishes that action? These answers prevent a dramatic screenshot of an HTTP response from being mistaken for a demonstrated business impact.

Confirm the protected route is the route customers actually use

Inventory the production hostname, API hostname, regional endpoints, file service, and any direct origin address. For each, identify whether the intended controls apply. A firewall protecting the marketing domain says little about a customer API hosted elsewhere.

For example, a SaaS company may put its browser application behind a WAF while mobile clients use a separate API. Both paths reach the same database. If the assessment covers only the website, it can miss the API’s account-permission checks. Include both paths in the agreed asset list.

Where authorized, test whether the origin accepts equivalent requests outside the intended edge route. Use harmless requests and retain the response and origin configuration evidence. If direct access is required for an operational reason, document the authentication or network restriction that governs it. The goal is to establish the effective boundary, not to assume every alternate endpoint is automatically a vulnerability.

Include requests that are valid but unauthorized

Business logic deserves its own assessment cases. Two test customer accounts can establish whether account A can read account B’s invoice, modify its delivery details, or download its export. Use synthetic records and the application’s normal request formats.

These tests answer questions about ownership and permissions. They do not require a visibly unusual payload. A WAF result cannot replace them because a well-formed request can still ask for the wrong person’s information.

Also review privileged operations. Can an ordinary user choose an administrative role in a request? Does a support action require current authorization? Does a queued export recheck the user when the file becomes available? Select cases from the actual product, rather than making the number of firewall alerts the measure of coverage.

Retest a mitigation without losing legitimate customers

A new blocking rule should have two acceptance conditions. It must stop the demonstrated unwanted behavior, and it must preserve the business operation customers are supposed to complete. A rule that blocks every checkout request can eliminate an attack and eliminate the store’s revenue at the same time.

Build a small regression set around the affected function. Include ordinary inputs, legitimate edge cases, and the reproduced security case. Record results at both the edge and application. If the issue is temporarily mitigated by a rule, keep the underlying application fix assigned to an owner with a date for verification.

What to ask for in a Ceron engagement

Scope a Ceron assessment around the application and the controls protecting its real public interfaces. Specify test accounts, permitted actions, rate limits, and whether direct-origin validation is authorized. For authenticated business logic, provide the roles needed to test the relevant boundaries.

The report should distinguish a confirmed vulnerability, a control gap, and an observation requiring additional evidence. It should also say when a result depends on the tested WAF configuration. After a rule or application change, retest the original path and the legitimate transaction, then document which risk was reduced.

A product owner should be able to follow a finding from the reachable endpoint to the unauthorized action, then see the retest showing that the fix stopped it. Ask for that evidence when deciding whether to close the issue.

Further reading

Ceron’s website audit guide explains scope and deliverables. The retesting guide covers verifying remediation. The SaaS example and regression design above are illustrative assessment recommendations.

Back to the blogExplore Ceron