QuorumWiki
Jugar

WAF

Bloquea a los bots antes de que lleguen a la aplicación, y con ellos a algunos usuarios reales.

Esta página aún no está traducida al español.

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.

SandboxBotsMantén el Apdex por encima de 0.9 durante 90 segundos.

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#

ControlValoresCuándo
Paranoia1 / 2 / 3 / 4Siempre
Bajo ataqueNormal / Bajo ataqueSiempre
  • 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.

Reglas#

  • Cada copia adicional cuesta un 25% más que la anterior.
  • Al venderlo se devuelve el 50% de lo que costó su última copia.
  • Tiene 6 tamaños. Cada paso duplica su capacidad y su Gasto.

Funciona con#

Usuarios, Proveedor de autenticación, CDN, API Gateway

Investigación siguiente#

Cuando tengas Firewall de aplicaciones web, estas Investigaciones se apoyan en ella.

Gestión de bots

Seguridad#

Estas vulnerabilidades pueden afectarle. Aplica el parche antes de que acabe el plazo de gracia.

  • CVE-2026-1337, CVSS 9.8

Términos de ingeniería#