> For clean Markdown of this page, append .md to its URL. For the complete documentation index, see https://www.superagent.sh/llms.txt.


Check for broken object-level authorization (BOLA) and insecure direct object references (IDOR) in private records exposed through a web application.

# BOLA testing for web applications


[← Back to attack scenarios](https://www.superagent.sh/docs/products/red-teaming/attack-scenarios)

Broken object-level authorization (BOLA) means the application fails to check whether a user has permission to access a specific record. Insecure direct object reference (IDOR) is a form of this flaw in which access to a record depends on a reference the user can control.

This scenario covers read access to customer records, documents, profiles, and other private data. It is useful when the same application serves multiple signed-in users and each user should see only the records they own or have permission to read.

A finding identifies which records became visible and which account could read them. For updates and deletions, see [resource ownership in web applications](https://www.superagent.sh/docs/products/red-teaming/attack-scenarios/application-resource-ownership). For authorization in the underlying code, see [object-level authorization checks in source code](https://www.superagent.sh/docs/products/red-teaming/attack-scenarios/repository-object-permissions).

The app lists this scenario as **Read another user's private records** (`APP-01`) in [Application Red Teaming](https://www.superagent.sh/docs/products/red-teaming/applications).

## Standards and guidance

[OWASP API1:2023 Broken Object Level Authorization (BOLA)](https://api-security.owasp.org/editions/2023/en/0xa1-broken-object-level-authorization/) · [CWE-639 Authorization Bypass Through User-Controlled Key](https://cwe.mitre.org/data/definitions/639.html)

---
Source: https://www.superagent.sh/docs/products/red-teaming/attack-scenarios/application-private-records
Index: https://www.superagent.sh/llms.txt
