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


Review where backend code enforces object-level authorization for private records and resources.

# Object-level authorization checks in source code


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

The same record may be reachable in several parts of the codebase. Authorization has to hold in each one. This scenario looks for code paths where that decision is missing or inconsistent.

It applies to repositories that implement access to private records or resources. A finding can point you to the relevant handler or data access layer so you know where to review the policy. For the deployed application view, see [BOLA testing for web applications](https://www.superagent.sh/docs/products/red-teaming/attack-scenarios/application-private-records).

The app lists this scenario as **Access another user's objects through a missing policy check** (`REPO-01`) in [Repository Red Teaming](https://www.superagent.sh/docs/products/red-teaming/repositories).

## Standards and guidance

[CWE-862 Missing Authorization](https://cwe.mitre.org/data/definitions/862.html)

---
Source: https://www.superagent.sh/docs/products/red-teaming/attack-scenarios/repository-object-permissions
Index: https://www.superagent.sh/llms.txt
