Skip to content
StrikeCyberStrikeCyber
Field Manual · Attack technique

Broken Access Control (IDOR)

Reviewed 13 November 2026Attack technique 1 min read

Quick answer

Broken access control is when an application fails to enforce what each user is allowed to see or do. A common form is an insecure direct object reference (IDOR), where changing an ID in a request returns another customer's data. It is ranked first in the OWASP Top 10 for web applications.

On this page
01

How It Works

Applications often check that a user is logged in but not that the specific record belongs to them. An attacker changes an account number, invoice ID or file reference and receives someone else's data, or calls an administrative API function as a normal user. Multi-tenant SaaS platforms are particularly exposed when tenant boundaries are enforced inconsistently.

02

Why It Matters

Access control flaws expose personal data at scale and are behind many breaches of customer portals and APIs. Scanners rarely find them because they cannot understand who should see what.

03

How to Test for It

  1. Test every function with multiple user roles and tenants side by side.
  2. Change object identifiers in requests, including in APIs and mobile apps.
  3. Attempt administrative functions as low-privilege users.
  4. Check server-side enforcement rather than hidden buttons in the interface.
04

How to Reduce the Risk

Enforce authorisation on the server for every request, deny by default, use centrally tested access control logic, avoid exposing guessable identifiers and include multi-role testing in every penetration test of applications holding personal data.

05

Regulatory and Framework Context

For Australian organisations, access control failures in customer portals can lead to notifiable data breaches under the Privacy Act.

Being exploited now

Threat Radar →

The latest related vulnerabilities confirmed as exploited in the wild.

Latest intel on this topic

Updated hourly from the daily briefing.

Common questions

What is an IDOR?

An insecure direct object reference: the application uses an identifier from the user to fetch a record without checking the user is allowed to access it.

Why don't scanners find access control flaws?

They do not know which data belongs to which user, so finding these flaws needs a tester using several accounts.

For testers: finding write-ups

How this shows up in a penetration test report, with severity, verification and remediation, in the StrikeOps Findings Library.

Change log

  1. 13 November 2026First published.
1300 654 898