Ravindra BagaleCourses & study guides मराठी Track your progress

Ravi Sir's Cards › AWS

WAF managed rules

This revision card explains WAF managed rules. It starts from the need that hand-writing every SQLi regex is brittle; bots evolve weekly. AWS Managed Rules (Common Rule Set, Known Bad Inputs, IP reputation) give a strong baseline. The how-to section covers how to attach Core rule set in count mode first , then review , then switch to block; add rate limits on /login. An example on the card is credential-stuffing spike hits rate-based rule; genuine users still browse the catalog.

WAF managed rules Hand-writing every SQLi regex is brittle; bots evolve weekly. AWS Managed Rules (Common Rule Set, Known Bad Inputs, IP reputation) give a strong baseline. Attach Core rule set in count mode first → review → switch to block; add rate limits on /login. Credential-stuffing spike hits rate-based rule; genuine users still browse the catalog.
WAF managed rules · Download PNG
Read card text

What this card says

Why do we need it?

Hand-writing every SQLi regex is brittle; bots evolve weekly.

What is it?

AWS Managed Rules (Common Rule Set, Known Bad Inputs, IP reputation) give a strong baseline.

AWSManagedRules

How to do it

Attach Core rule set in count mode first → review → switch to block; add rate limits on /login.

Example

Credential-stuffing spike hits rate-based rule; genuine users still browse the catalog.

See all AWS revision cards