API Security
API Security: Why Broken Object Level Authorization Still Tops the OWASP API Top 10
Changing one number in an API request and seeing someone else's data is still the most common serious flaw we find.
Mobile apps, single-page web apps, partner integrations and now AI agents all talk to your systems through APIs. That makes APIs the largest and least visible part of most attack surfaces, and scanners built for web pages often miss their most dangerous flaws.
BOLA: the flaw that will not go away
Broken Object Level Authorization (BOLA), also called IDOR, sits at number one in the OWASP API Security Top 10. The API checks that you are logged in, but not that the record you are asking for is yours. Change /api/orders/1043 to /api/orders/1044 and you see another customer's order. It is simple, it scales to every record, and automated tools rarely catch it because the response looks normal.
The other API risks that matter most
- Broken authentication — weak tokens, tokens that never expire, missing rate limits on login and password reset.
- Broken object property level authorization — APIs that return or accept more fields than they should, such as letting a user set their own role.
- Unrestricted resource consumption — no limits, so one client can run up costs or take the service down.
- Broken function level authorization — normal users calling admin endpoints.
- Improper inventory — old API versions and undocumented shadow APIs still live in production.
How to fix it for good
| Practice | Effect |
|---|---|
| Central authorisation checks on every object access | Eliminates BOLA by design |
| Explicit response schemas | Stops excessive data exposure |
| API inventory from gateway and traffic | Finds shadow and zombie APIs |
| Rate limits and quotas | Limits abuse and cost attacks |
| Manual API penetration testing with multiple user roles | Proves authorisation actually holds |
Test your APIs with real user roles
Our API tests use multiple accounts and roles to find the authorisation flaws scanners miss.
Explore API security testingFrequently asked questions
What is BOLA?
Broken Object Level Authorization is when an API lets a user access or change records belonging to other users because it does not check ownership of each requested object.
Can automated scanners find API vulnerabilities?
They find some issues, but authorisation flaws such as BOLA usually need manual testing with multiple user accounts and roles.
What is a shadow API?
An API endpoint that is live in production but not documented or managed, often an old version or a forgotten test endpoint.
PITOWINGS Research
OSCP, CEH and ECES certified testers, SOC analysts and certified forensic investigators at PITOWINGS.
Keep reading
All articlesPITOWINGS · Insights
AI Security
11 min read
Agentic AI Security in 2026: Prompt Injection, MCP Servers and the OWASP Agentic Top 10
AI agents now read email, call APIs and change records on their own. The attack surface is no longer the prompt; it is everything the agent can see, call and remember.
PITOWINGS · Insights
Cryptography
10 min read
NIST IR 8547 Is Final: RSA and ECC Deprecated After 2030 — Your Post-Quantum Migration Plan
The quantum deadline now has a date on it. Here is what NIST's final transition plan changes, and a practical migration path that starts with knowing where your cryptography is.
PITOWINGS · Insights
Security Operations
9 min read
AI in the SOC: What AI Agents Can and Cannot Do for Threat Detection in 2026
AI can read every alert. It still cannot decide, on its own, whether to take your payment system offline at 3 a.m.


