WAF
ボットがアプリに届く前に止めます。本物のユーザーもいくらか巻き込みます。
このページはまだ日本語に翻訳されていません。
The WAF stands for a web application firewall such as ModSecurity with the OWASP Core Rule Set.
When to place it#
Place it when bots take a large share of your traffic and load your App Servers, or when logins spike from bots. It unlocks with Web application firewall.
Turn on Under attack mode only while a DDoS lasts.
The Bots Sandbox shows the symptom.
サンドボックスボットApdexを0.9以上に90秒間保ってください。How it works#
Place it in front of your App Servers. It takes every request kind and sends on what it lets through. It blocks a share of bots, and a smaller share of real users with them. Blocked users fail as blocked. See WAF.
Each size step doubles its capacity. It spans every zone.
Options#
| 設定項目 | 設定値 | 表示条件 |
|---|---|---|
| パラノイア | 1 / 2 / 3 / 4 | 常時 |
| 攻撃時 | 通常 / 攻撃時 | 常時 |
Paranoia: how hard the rules look. A higher level blocks more bots, blocks more real users, and costs more CPU per request, so the WAF handles less traffic.
Under attack: challenges every request while it is on. It blocks nearly all junk, blocks some real users, and adds latency. Turn it off when the flood ends.
How it fails#
Overloaded, it drops requests before they reach the App Servers. A high paranoia level makes this happen sooner.
A high level blocks real users and costs revenue.
Without a WAF, Bot surge, Credential stuffing, and DDoS hit harder and more often.
Regex backtracking#
Signs: Its Inspector reads "A rule backtracks. CPU at 100%." Every WAF runs out of CPU. See ReDoS.
Do now: Press Disable rule.
Prevent: No Research prevents it. A WAF always carries the risk of a bad rule.
DDoS#
Signs: Its Inspector reads "A flood of junk traffic." and demand runs at ×50 of junk.
Do now: Press Under attack on the WAF. It challenges every request and adds latency.
Prevent: Keep a WAF and a CDN at the edge: Web application firewall and Content delivery. Turn Under attack mode off when it ends.
Instance failure#
Signs: The WAF's card goes grey, its Inspector reads "The host under this VM died. It still bills.", and the requests sent to it are stranded.
Do now: Press Replace in its Inspector and pay the price. It comes back cold.
Prevent: Run a second copy: Load balancing puts the copies behind a Load Balancer, and Health checks skip the dead host.
Region outage#
Signs: Every Node in one region goes grey at once, and that region's board goes grey with them.
Do now: Press Fail over on the banner. It needs Multiple zones and a second open region, and starts the Node again in the nearest other region, cold, for the price of a replacement. Otherwise it comes back when the incident ends: 180 sim seconds in the catalog, 60 once the error budget counts.
Prevent: Research Multiple regions and GeoDNS, then run a copy of it in a second region.
Tips#
Start at the default level and raise it only when bots still get through.
Turn Under attack mode off when the DDoS ends.
ルール#
- 追加のコピーは 1 つ前より 25% 高くなります。
- 売却すると、最後のコピーの価格の 50% が戻ります。
- サイズは 6 段階です。1 段ごとに容量と支出が倍になります。
一緒に使えるもの#
次に取るリサーチ#
Webアプリケーションファイアウォールを手に入れると、次のリサーチがそれを土台に進みます。
セキュリティ#
これらの脆弱性がこのコンポーネントを狙います。猶予期間が終わる前にパッチを当てます。
- CVE-2026-1337, CVSS 9.8