waf-review

Review Cloudflare WAF rules, rate limiting, bot management, and edge security configuration.

15|3|Updated Jul 9, 2026
One-click install
npx skills add https://github.com/thefear078/cursor-kit-for-ai --skill waf-review-thefear078
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: waf-review
Source: https://github.com/thefear078/cursor-kit-for-ai/tree/main/plugins/security/skills/waf-review
Command: npx skills add https://github.com/thefear078/cursor-kit-for-ai --skill waf-review-thefear078

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Edge security misconfigurations leave applications exposed: publicly reachable origins bypass the WAF entirely, overly aggressive rules break legitimate traffic, and missing rate limits invite credential stuffing and scraping. This Skill provides a structured audit of Cloudflare edge protection so gaps are found before attackers find them. ## Core Features & Use Cases - Exposure Audit: Verify the origin IP is hidden behind Cloudflare IP allowlists or Tunnel, TLS is Full (strict), and subdomains are correctly proxied. - WAF Rule Review: Check managed rulesets (Cloudflare Managed + OWASP Core), custom rule expressions, rule ordering, and false-positive risks. - Rate Limiting & Bot Posture: Define per-endpoint rate limits for login, OTP, and expensive APIs, and configure bot management without blocking verified bots like Googlebot. - Use Case: Before launching a SaaS app on Cloudflare, run this review to confirm the origin is not directly reachable, login endpoints have per-IP and per-account limits, and webhook allow rules precede challenge rules. ## Quick Start Review my Cloudflare zone configuration for example.com and produce an edge security report covering origin exposure, WAF rules, and rate-limit coverage.

Frequently Asked Questions about waf-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review Cloudflare WAF rules for security gaps?▼

Start with an exposure audit confirming the origin accepts traffic only from Cloudflare IP ranges or Tunnel, then review managed rulesets in Log mode before enforcing. Check custom rule ordering so allow rules for webhooks and health checks precede challenge rules.

How to configure rate limiting on Cloudflare for login endpoints?▼

Set roughly 5 requests per minute per IP on login, register, and password reset endpoints, with tighter 3-5 per minute limits on token and OTP verification. Pair edge limits with app-side per-account throttling since distributed credential stuffing bypasses per-IP rules.

Can Cloudflare WAF protect a publicly reachable origin server?▼

No. If the origin IP is publicly reachable, attackers bypass the WAF and hit the origin directly. Firewall the origin to allow only Cloudflare IP ranges or use Cloudflare Tunnel, and check DNS history and old subdomains for IP leaks.

Why does enabling Cloudflare managed rules break legitimate traffic?▼

Enabling managed rulesets straight to Block mode on an existing app causes false positives that break legitimate flows. Run rules in Log mode for about a week, review flagged traffic, then switch to enforcement.

Should I bot-challenge API routes on Cloudflare?▼

No. Bot challenges break legitimate non-browser API clients. Route API traffic to token authentication plus rate limits instead, and reserve managed challenges for unverified automation on browsing routes while allowing verified bots like Googlebot.