The recently published “OWASP API security top 10” report analyzes the anti-patterns that lead to vulnerabilities and security risks in APIs. In this 10 part series, we introduce these API anti-patterns. Every API professional should know about these anti-patterns.


Lack of Resources & Rate Limiting from the OWASP API security paper

API security anti-pattern for Lack of Resources & Rate Limiting

Sometimes APIs are published without enforcing limitations on the rate of access per user or per client/app. Such APIs may have poor performance and are susceptible to Denial of Service (DoS) attacks and brute-force attacks on the authentication.

Want to learn more?

Check out the complete OWASP API security paper. To secure access to your APIs, learn more about the OAuth in the OAuth Book, or the OAuth Course. To provide and use identity data in apps and APIs, learn more about OpenID

The 10 most critical API security risks – Part 4: Lack of Resources & Rate Limiting

Also published on Medium.

Matthias Biehl

As API strategist, Matthias helps clients discover their opportunities for innovation with APIs & ecosystems and turn them into actionable digital strategies. Based on his experience in leading large-scale API initiatives in both business and technology roles, he shares best practices and provides both strategic and practical guidance. He has stayed a techie at heart and at some point, got a Ph.D. Matthias publishes a blog at api-university.com, is the author of several books on APIs, and regularly speaks at technology conferences.