Rate Limiting
Capping how many requests a client can make in a time window.
What it is
A control that restricts the number of requests a given client, key, or IP may issue over a period, throttling or blocking those that exceed the threshold to protect availability and abuse-prone functions.
Why it matters
Its absence enables credential stuffing, brute force, scraping, and denial of service, so missing or weak limits on login and other sensitive endpoints are a frequent and impactful finding.
In practice
Blocking a source after a burst of failed logins to stop a password-guessing run cold.
What to look for
- Many requests from one client or token.
- Login or OTP endpoints without limits.
- Limits applied per IP that rotating proxies get around.
Common mistake
Limiting by IP only. Limit by account and token as well.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
- Email Header Analyzer
Walk the Received chain, and read the SPF, DKIM and DMARC verdicts.
- Phishing Case
A reported invoice email: pull the deciding values out of its raw headers, and say what they establish.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Burp Suite Commercial
An intercepting proxy for testing web apps by hand and with its scanner.
-
ZAP Open source
An open source web app scanner and proxy, often run in CI pipelines.
-
Cloudflare WAF Commercial
Blocks common web attacks at the edge while the code gets fixed.
Read next
- API Security: Protecting application programming interfaces from abuse and data exposure.
- Broken Access Control: Failure to enforce what authenticated users are allowed to do.
- Credential Harvesting Page: A counterfeit login page built to capture entered credentials.