Edge Threat Defenses
Cloudflare filters requests at the edge with managed WAF rulesets, custom rules, rate limits, DDoS mitigation and bot detection. Interviewers ask which control fits and how to tune it.
on this pageshowhide
explore
- Managed WAF Rules6 questions
- Custom Rules & Expressions5 questions
- Request Rate Limits5 questions
- DDoS Mitigation Tuning6 questions
- Bot Scores & Turnstile6 questions
- Origin Lockdown5 questions
questions
page 2 of 2As security lead, how would you roll out Cloudflare's managed WAF rulesets on a live checkout and API, and who should own the exceptions afterwards?
basics
~20 sDeploy the Cloudflare Managed Ruleset first and watch Security Events before enforcing: in Log on Enterprise, or scoped and challenged elsewhere. Add OWASP only if it earns its false positives. Exceptions go through one owner, stay narrow and get reviewed.
How does Cloudflare's Adaptive DDoS Protection build a zone's traffic baseline, and which of its rules do zones on every plan get?
basics
~20 sAdaptive DDoS Protection profiles each zone's daily peak rates over the past seven days at the 95th percentile, then flags traffic that deviates; every plan gets the origin-errors rule, while the location and user-agent rules need Enterprise with Advanced DDoS Protection.
A marketplace's own mobile app gets low Cloudflare bot scores on its checkout API; how do you use JA3 or JA4 fingerprints to let it through safely?
basics
~20 sA native app's TLS stack usually yields the same JA3 or JA4 fingerprint across devices. Find it in Security Analytics, then add a Skip rule matching cf.bot_management.ja4 together with the app's API host and path, placed before the score rule.
showing 31–33 of 33