返回资讯中心
外部精选
软件工程
#开发者实时流

You're paying for a WAF. Is it blocking anything?

Pablo Camino, Founder of Plimie · October 16, 2026

Hacker News 最新pcaminog2026/10/16 · 2026/10/1612 分钟阅读

以下正文同步自 Hacker News 最新,版权归原站所有,已转换为易读排版。

Pablo Camino, Founder of Plimie · October 16, 2026

A web application firewall is one of those line items that feels finished the moment it shows up on the invoice. The contract is signed, the feature is “on,” and someone ticked the box on the security questionnaire. But “on” and “protecting you” are not the same thing.

A WAF can be enabled and still block nothing at all. Rules sit in log-only mode after a cautious rollout and never get promoted. Managed rulesets are available on the plan but were never deployed to the sites that matter. Exceptions written during an incident three years ago quietly cover half the application.

None of this produces an alert. Traffic flows, the site works, and the dashboard shows a reassuring number of “events.” In this post we’ll go through why this happens, and walk through a self-check you can do in about ten minutes to find out whether your WAF is actually enforcing anything.

Almost every WAF rollout follows the same, sensible path: deploy in a monitoring mode first, watch for false positives, then switch to blocking. The trouble is the last step. It needs someone to own it, and a reason to do it, and both tend to disappear once the initial project closes.

There are a few common ways it goes wrong:

Each of these is a reasonable decision in the moment. Together, they can leave you with a WAF that produces logs, not protection.

You don’t need a penetration test to get a first answer. You need read access to your WAF configuration and its event logs, and a bit of honesty about what you find. Work through these five steps in order.

Export or view the full list of active rules and rulesets, and write down the action each one takes. Group them into three buckets:

block / challenge -> actually enforcing log / count / simulate -> observing only disabled -> not doing anything

If most of your rules, or your most important managed ruleset, land in the second bucket, you’ve already found the main issue.

Check whether the managed rulesets included in your plan are actually deployed, and to which hostnames. “Available” in the UI is not the same as “deployed.” Write down which public hostnames are covered and which aren’t.

A quick way to make this concrete is to list your public hostnames from DNS and compare:

hostname managed ruleset action www.example.com yes block api.example.com no - app.example.com yes log

Any public hostname with “no” in the second column is unprotected by the rules you’re paying for.

Filter your WAF event log for the last week and group by action. You’re looking for the ratio between “would have blocked” and “blocked.”

If you see a steady stream of matches against obvious attack signatures (SQL injection, path traversal, known scanner user agents) and every one of them was logged and allowed through, the rules are working as detectors and failing as a firewall.

This is the core difference the whole check comes down to. A rule in log-only mode sees the attack and records it. A rule in block mode stops it before it reaches your origin. Both produce an event. Only one of them protects you.

List every skip, bypass, or allowlist rule. For each one, ask:

An exception that bypasses the whole WAF for a broad path is functionally the same as turning the WAF off for that path. Treat these as the highest priority to review.

Pick a hostname you own and send a request that a standard ruleset should match, without any real payload. A classic, harmless example is a query string containing a recognizable test pattern:

curl -s -o /dev/null -w "%{http_code}\n"
"https://www.example.com/?q=%3Cscript%3Ealert(1)%3C%2Fscript%3E"

If your WAF is enforcing, you’ll typically get a block or challenge response (often a 403). If you get a 200, look for the matching event in the log. If the event is there with a log-only action, you’ve confirmed the problem end to end. Only test hosts you own and are authorized to test, and let your security team know before you do.

Don’t flip everything to block at once. That’s how WAF projects get rolled back. A safer sequence:

A WAF that only logs is not useless. The logs are valuable, and monitoring mode is the right way to start. But if it has been in monitoring mode for months, you’re paying for protection and getting telemetry. The fix is rarely technical. It’s usually a missing owner and a step that never got scheduled.

The ten-minute check above will tell you which situation you’re in. If you’d rather have a second pair of eyes, that’s what we’re building at Plimie: a read-only review that checks whether the features you pay for are actually deployed and set up right, without changing anything in your account. Our pilot is free and invite-only, and you can request a free review here.

正文由 探How 从来源站点 RSS 同步,内容未经改写;遇到排版缺失或需要图片、视频时请以原文为准。

打开原文
去社区讨论 →