Join our Newsletter — 33% off our NHI Course
Home› Glossary› Threats, Abuse & Incident Response› OWASP A01: Broken Access Control
Threats, Abuse & Incident Response

OWASP A01: Broken Access Control

← Back to Glossary
By NHI Mgmt Group Updated November 16, 2026 Domain: Threats, Abuse & Incident Response

OWASP A01: Broken Access Control is a category of web application weakness where users or systems can do things they should not be able to do. It covers missing authorisation checks, privilege escalation, forced browsing and IDOR style object access failures, where the application exposes actions or data beyond the caller's permitted scope.

What Broken Access Control Really Means

Broken access control is not just a missing permission check, it is any failure to enforce who may act on what, and under which conditions. In practice, that means the application trusts the caller too much, then exposes actions or data that should be blocked by server-side policy.

The weakness often appears in places where the UI looks safe but the backend does not re-check entitlement. That gap is why broken access control can hide in ordinary workflows until someone changes an object ID, reuses a request, or reaches a function that was only intended for a different role.

Common Failure Patterns Behind the Vulnerability

The most familiar patterns are IDOR, forced browsing, missing function-level checks, horizontal and vertical privilege escalation, and client-side enforcement that the server never repeats. These are not separate problems so much as different ways of expressing the same control failure: the application lets the requester choose more than it should.

Broken access control also shows up when ownership checks are incomplete, tenant boundaries are weak, or an application confuses authentication with authorisation. Authentication vs Authorisation is the distinction practitioners need here, because proving who the caller is does not by itself prove what that caller may access.

For web applications, the practical standard is server-side decision making. That usually means checking object ownership, role, tenant, and action scope before the request reaches the data or business logic layer. The OWASP Top 10 A01 Guide is useful because it ties the weakness to the common exploitation patterns practitioners actually test.

Why It Is Dangerous in Real Applications

Broken access control is dangerous because it turns ordinary business functions into unintended entry points. A single missed check can expose customer records, internal documents, admin functions, financial operations, or cross-tenant data, even when the rest of the application looks well built.

Its impact is often larger than the initial flaw suggests. Once a user can read or alter someone else’s object, the same path may enable fraud, data theft, privilege escalation, or chained compromise across adjacent functions. That is why access control failures frequently become the highest-value bug class in an application review.

Many teams underestimate how often this weakness comes from design rather than code style. The problem is not only “forgot to check permission”, it is also “never defined the authoritative decision point”. Guidance on Authorisation Maturity Model helps frame that broader control design issue, from ad hoc checks to explicit policy enforcement.

How to Test and Reason About Exposure

Exposure assessment starts with identifying every object, action, and role boundary the application exposes. The important question is not whether a page is hidden, but whether the backend still accepts a request when the caller changes an identifier, removes a filter, or tries a function they should not reach.

Good testing looks for direct object references, cross-user access, cross-tenant access, method tampering, and state changes that can be triggered without a valid entitlement. That is why the best test cases combine request replay, account switching, negative authorization checks, and review of server-side enforcement paths.

When teams need a structured way to think about enforcement depth, Coarse-Grained vs Fine-Grained Authorisation helps clarify where gateway-level checks stop and object-level controls must begin. For broader policy design, Authorisation Models Guide shows how RBAC, ABAC, and ReBAC can support different decision styles without relying on application folklore.

Detection, Remediation, and Control Design

Remediation is usually about moving the decision to the server, making the decision explicit, and ensuring it is evaluated consistently in every relevant path. That means object-level checks, deny-by-default logic, policy reuse, and enough logging to prove who attempted what and whether the control allowed it.

Post-fix review matters too. If the weakness existed in production, teams should look for abuse of the exposed path, unusual object access, and any data or state changes that happened before the fix. The Authorisation Testing Automation Guide is especially useful for building regression tests so the same gap does not return in the next release.

For a broader secure-development baseline, OWASP ASVS gives practitioners a control-oriented way to verify authorisation, session handling, and access enforcement. The companion OWASP Web Security Testing Guide supports repeatable testing of those controls in web applications.

Risk and Threat Considerations

Broken access control is a high-value weakness because it converts normal application features into attacker-controlled access paths. The most serious outcome is usually not a single page view, but the ability to move laterally across users, tenants, or functions until sensitive data or privileged actions are reached.

Failure mechanism: The application trusts client-supplied object IDs, role claims, or workflow state without re-validating that the caller is entitled to the specific action or resource. That allows direct object access, function abuse, or privilege escalation even when the front end appears restricted.

Impact: Attackers can read, modify, delete, or impersonate across security boundaries, which can lead to data exposure, fraud, account compromise, administrative takeover, and cross-tenant breach.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

OWASP ASVS, NIST SP 800-53 Rev 5 and CIS Controls v8 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
OWASP ASVSV8 — AuthorizationBroken access control is fundamentally an authorization verification problem.
V7 — Session ManagementSession handling affects whether a caller can reuse or escalate access across requests.
V16 — Security Logging and Error HandlingAccess-control failures require auditable logs for detection and post-incident review.
Recommendation — Verify object-level and function-level authorization on every sensitive request path. Validate that sessions cannot be reused to bypass authorization boundaries. Log authorization decisions and investigate anomalous denied or successful access attempts.
NIST SP 800-53 Rev 5AC-3 — Access EnforcementDefines enforcing approved authorizations on system resources and actions.
AC-6 — Least PrivilegeLimits the damage when access control is bypassed or misapplied.
AU-6 — Audit Review, Analysis, and ReportingSupports review of suspicious authorization bypass attempts and misuse.
Recommendation — Enforce approved access decisions at the system boundary and object level. Restrict each account and service to the minimum permissions needed. Review audit records for abnormal access patterns and authorization failures.
CIS Controls v8CIS-6 — Access Control ManagementCovers managing access paths, approvals, and enforcement for users and services.
CIS-8 — Audit Log ManagementProvides detection and investigation support for abuse of exposed access paths.
Recommendation — Centralize access control rules and review them for excessive or inconsistent permissions. Collect and retain logs that show who accessed what and whether access was denied or allowed.

Practitioner Guidance

Why practitioners should care: Broken access control is rarely fixed by one code change, because it usually reflects a control-design problem. Teams should treat it as an application-wide authorisation issue, not a one-off bug in a single endpoint.

Governance implication: Define where the authoritative authorisation decision is made, how it is enforced, and how it is tested before release. If those decisions are left to individual teams or controllers, inconsistent checks will reappear in new features and integrations.

Practitioner takeaway: The safest applications make every sensitive action fail closed unless the server can prove the caller is allowed to perform it.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 16, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org