Cybersecurity & Information Security

IDOR and BOLA: Object-Level Authorization Testing

6 min readPublished: August 5, 2026

Professional visual illustration of IDOR BOLA in the Web and API PT domain

Quick answer

IDOR BOLA should only be tested in a lab or authorized system. Test Request/Response, server behavior, Roles, State, and impact, using minimal tests that do not damage data.

Web and API security testing should examine the boundaries of trust, permissions, input, State, and business logic. Every test in this article is designed for a lab, CTF, or a system for which explicit authorization has been given. This article focuses on IDOR BOLA and is intended for Web/API PT students. The goal is to provide a working method that can be applied in practice, in a professional interview, and in a work environment, without settling for a dictionary definition.

The main challenge is that data is almost always partial. Role matrix, object identifiers, server-side authorization can indicate a direction, but their meaning depends on time, asset, user, and expected activity. Therefore, we will build the test around an investigative question, required evidence, and clear criteria for completion.

The practical scenario in the article is: a two-account scenario and one resource in the lab. All examples are lab data or process descriptions. When it comes to Penetration Testing, Web, or Cloud, one must only work with explicit permission, a defined Scope, and the ability to stop the test.

What is IDOR/BOLA

The topic 'What is IDOR/BOLA' is a central part of working on IDOR BOLA. It is recommended to break it down into three questions: what is the input, what decision do you want to make, and what evidence is sufficient to justify it. These questions prevent automatic tool usage without understanding the objective.

In practice, record the role matrix, object identifiers, server-side authorization, horizontal/vertical access, response differences, compare to expected behavior, and define at least one Pivot. The result should be testable by another analyst, including limitations and next steps.

Mapping Objects and Owners

The topic 'Mapping Objects and Owners' is a central part of working on IDOR BOLA. It is recommended to break it down into three questions: what is the input, what decision do you want to make, and what evidence is sufficient to justify it. These questions prevent automatic tool usage without understanding the objective.

Testing Between Users

Professional IDOR BOLA testing begins with success conditions and failure conditions. Define a positive Case, a negative Case, a boundary Case, and similar legitimate activity. This allows identification of both False Negatives and False Positives.

In an authorized environment, use a minimal action that proves the claim without causing damage. Save Input, Output, time, and version, and after correction, perform a Retest in the same scenario and also check for Regression on nearby functions.

Impact and Evidence

The topic 'Impact and Evidence' is a central part of working on IDOR BOLA. It is recommended to break it down into three questions: what is the input, what decision do you want to make, and what evidence is sufficient to justify it. These questions prevent automatic tool usage without understanding the objective.

Remediation and Negative tests

Unique Testing Focus Areas

In this topic, it is recommended to build a focused evidence map in advance. The central testing focus areas are: role matrix, object identifiers, server-side authorization, horizontal/vertical access, response differences, audit logs. The list is not an automatic Checklist; each item is chosen because it can link an entity, action, and time, or explain legitimate behavior.

role matrix: Define the expected value, what would be considered an anomaly, and what additional source will corroborate the finding.
object identifiers: Define the expected value, what would be considered an anomaly, and what additional source will corroborate the finding.
server-side authorization: Define the expected value, what would be considered an anomaly, and what additional source will corroborate the finding.
horizontal/vertical access: Define the expected value, what would be considered an anomaly, and what additional source will corroborate the finding.
response differences: Define the expected value, what would be considered an anomaly, and what additional source will corroborate the finding.
audit logs: Define the expected value, what would be considered an anomaly, and what additional source will corroborate the finding.

When one of the focus areas is unavailable, document the gap and choose an alternative. For example, if a Process identifier is unstable, one can use time, Host, User, and Parent; if Payload is encrypted, use Metadata, volume, frequency, and TLS/DNS context.

Recommended Workflow

Define a Scope and one working question regarding IDOR BOLA.
Record the data sources and required evidence: role matrix, object identifiers, server-side authorization, horizontal/vertical access.
Create a short Baseline of normal behavior or expected outcome.
Perform the minimal test in a lab environment and save time, input, and output.
Build a Timeline or comparison table and separate facts from interpretation.
Pivot to an additional source to confirm or refute the initial explanation.
Summarize the decision, limitations, recommended action, and Retest criteria.

Practical Scenario

The chosen scenario involves two accounts and one resource in the lab. The purpose of the exercise is not to demonstrate attack capabilities, but to practice collecting, comparing, and documenting in a safe manner. Before starting, define mock data, a time window, and an expected outcome.

At the end of the exercise, a product should be submitted that another analyst or tester can review: a screenshot or export of the evidence, a short Timeline, an initial assumption, corroborating evidence, a limitation, and a recommendation. When there is insufficient evidence, the correct conclusion is that the scenario was not proven.

Step	What to perform	Output
Preparation	Define Scope, time, and goal. List which fields or evidence from role matrix, object identifiers, server-side authorization are expected to appear.	Short test plan
Data Creation	Perform a safe and simulated action related to IDOR BOLA, without real information or impact on a production system.	Controlled event/Request/Flow
Collection	Collect the raw evidence and context from an additional source. Ensure Time zone, identifiers, and integrity.	Two linked pieces of evidence
Analysis	Write what each piece of evidence proves, what it does not prove, and what is the possible legitimate explanation.	Interim conclusion
Completion	Choose a closing, escalation, Finding or Tuning; add a recommendation and Retest.	Documented output

Practical Checklist

Check and document: Role and session.
Check and document: Endpoint and method.
Check and document: Request/Response.
Check and document: Object identifier.
Check and document: Server-side effect.
Check and document: Control expected and remediation.
State Time zone, tool version, and collection time.
Save the raw data before filtering or modification.
Write what the finding proves and what is still unknown.
Define owner and next action with a due date.

Common Mistakes

Only checking Status code.
Relying on Client-side changes.
Using a dangerous Payload.
Not testing different Roles.
Ignoring business logic.
Reporting without clean Request/Response.

Summary and CTA

IDOR and BOLA: Object-Level Authorization Testing is a topic that connects technical knowledge with work discipline. Start with a question, collect only relevant evidence, maintain context and time, and choose an action that can be justified and retested.

In HPI's Cybersecurity & AI program, these principles are practiced using systems, logs, and labs. A natural next step is to move on to the linked articles, perform the lab exercise, and save the output as part of a professional portfolio.

FAQ

Is it permissible to test IDOR BOLA on a public website?

Not without explicit authorization from the system owner. Even a seemingly simple test can change data, trigger defense mechanisms, or be considered unauthorized access.

What to do when some data is missing?

Document the missing data, check for an alternative source, and reduce the confidence level. Do not fill in fields by conjecture or present 'Unknown' as valid.

How long should evidence be retained?

The time depends on policy, regulation, cost, and the type of event. It's important to define Retention, Legal hold, and the ability to export evidence in a verifiable format in advance.

How to practice without endangering a real system?

Use virtual machines, mock data, CTF, or a dedicated lab. In authorized tests, define Scope, Stop conditions, and backup before starting work.