// Concept and defense
Broken access control: the OWASP #1 risk in SaaS
What broken access control is
Broken access control is when a user can do or see something they should not: read another customer’s data, reach an admin route without being admin, or edit a resource that is not theirs. It has been number 1 in the OWASP Top 10 since 2021, a position it kept in the 2025 edition, and it is by far the flaw class that most sinks AI-built SaaS, because AI gets "who gets in" (authentication) right and "what each one can do" (authorization) wrong.
The distinction that sums it up: authentication proves who you are; authorization decides what you can do. Broken access control is always an authorization failure, and it happens after login, in the place the demo does not show.
How it shows up in AI-built SaaS
It is not one flaw; it is a family. The most common forms in AI-built products:
- IDOR: swapping an id in the URL/body returns another customer’s resource.
- Privilege escalation: an ordinary user reaches an admin action or route.
- Forced browsing: hitting /admin or /report directly, with no link, works.
- Front-end-only check: the button disappears, but the API still responds.
- Missing tenant scope: a query forgets the customer filter.
How to prevent and test it
The rule is deny by default and verify ownership on the server, on every read and write. Never trust that hiding the button in the front-end protects the action; the access boundary lives on the server, next to the data.
- Check on the server: does this user own this record? have this role?
- Deny by default; grant the minimum by role and by tenant.
- Test with two accounts: logged in as A, try to reach B’s resource.
- Cover unlinked routes (forced browsing) and the API behind the screen too.
Where RET fits
Broken access control is exactly what RET’s Risk Review and Manual Pentest chase first, because it is what most blocks a B2B sale and becomes an incident. The review tests every flow that returns data: who reaches what, with which account, and proves what breaks with reproducible evidence. The Promptbook guides the first pass yourself.
Want to know whether this happens in your system?
Manual pentest for web applications, APIs and apps, from R$9,500, with the Sprint run within 7 business days. We refund 50% if we find no flaw.
Frequently asked questions
Is broken access control the same as IDOR?
IDOR is a FORM of broken access control (swapping an id and reaching someone else’s resource). Broken access control is the larger family, which includes privilege escalation, forced browsing and front-end-only checks. IDOR is the most common.
Why is it OWASP #1?
Because it is easy to introduce (forgetting an ownership check), hard to see in the demo (it happens after login) and high impact (it leaks customer data, breaks the multi-tenant promise). In AI-built SaaS, it is the dominant flaw.
Does strong authentication solve it?
No. Authentication (login, MFA) proves who you are; broken access control is an authorization failure (what you can do after logging in). A perfect login with loose authorization still leaks data.
How do I test it quickly?
Create two accounts, do an action in each, and try, with A’s session, to read/edit B’s resource (swapping ids). If data comes back, it is broken access control. Risk Review does that sweep in depth.
Keep reading
Threat and defense
MCP tool poisoning: how to prevent it
Practical guide
Multi-tenant isolation in SaaS
Threat and defense
Credential stuffing and MFA on the admin panel
Comparison
In-house pentester vs outsourcing the pentest
By tool
Security for apps built with Base44
By city
SaaS security and pentest in Curitiba (PR)