// Decision comparison
WAF vs pentest
Quick answer
A WAF (Web Application Firewall) and a pentest solve different kinds of problems and do not even compete. The WAF sits at the edge and filters traffic in real time: it blocks known attack patterns (classic injection, automated scanners, abusive bots) before they reach the app. A pentest finds the flaw that exists in your product, especially the logic flaw, which the WAF does not even try to cover because it does not look like an attack: an IDOR is a perfectly valid request with a swapped id.
Rule of thumb: have a WAF (it is cheap defense in depth and reduces noise) but never treat it as a substitute for testing. A WAF does not fix the hole, it makes some harder to reach. If the flaw is logic (improper access, plan bypass), the WAF lets it through, because it is legitimate traffic. Only testing finds it and only a fix closes it.
RET runs this test: a 25-hour Sprint for R$9,500, within 7 business days. See price and timeline for my case
What a WAF covers and what it cannot see
The WAF is strong against the generic and blind to what is specific to your business. It does not know that this user should not see that order; to it, that is a valid GET.
| Situation | WAF | Pentest |
|---|---|---|
| Classic injection / known payload | Blocks a lot | Finds what gets through |
| Scanners and automated bots | Filters at the edge | Not the focus |
| IDOR / access to another tenant’s data | Cannot see (valid request) | Primary focus |
| Plan bypass / billing logic | Cannot see | Primary focus |
| Fixes the cause | No, only mitigates at the edge | Points to the fix |
| Best role | Reduce noise and generic attacks | Find and prove the real one |
The false comfort of "I have a WAF"
The expensive mistake is thinking that turning on a WAF closes security. It reduces the generic attack surface and buys time, but the incident that hurts most in SaaS (cross-tenant leakage, improper access, a plan unlocked without paying) passes through the WAF without triggering anything, because it has no attack signature: it is a well-formed request. The WAF is the seatbelt; testing is finding out whether the car has brakes.
- WAF: keep it on, it is cheap defense in depth.
- Do not trust the WAF for business logic; it does not understand it.
- Test (Risk Review / Pentest) for the flaw the WAF lets through.
Where RET fits
RET neither sells nor replaces a WAF; it finds what the WAF does not cover. Risk Review reads the access, billing and data flows; the Manual Pentest proves what an attacker would reach even with a WAF in front. Keep the WAF at the edge and use RET to make sure that, behind it, the product logic does not hand over what it should not.
Frequently asked questions
If I have a WAF, do I need a pentest?
You do. The WAF blocks generic attacks at the edge, but does not see logic flaws (IDOR, plan bypass, cross-tenant leakage), because those arrive as valid requests. Only testing finds them, and only a fix closes them.
Doesn’t the WAF block IDOR?
Not reliably. An IDOR is a well-formed GET with a swapped id; to the WAF it is legitimate traffic. It does not know that user does not own the object, that is your business rule.
So is a WAF useless?
Far from it. A WAF reduces noise, blocks scanners and known attacks, and is cheap defense in depth. The mistake is treating it as a substitute for testing; it mitigates, it does not fix.
Does RET configure my WAF?
That is not the focus. RET finds and proves the flaw the WAF does not cover (the logic one) and points to the fix at the cause. WAF and testing are different, complementary layers.