HomeResearch

Testing access control across accounts

Some of the most damaging flaws in web apps are not clever exploits. They are a missing check: the app answers a request it should have refused, because it never asked who was asking. You can’t find these reliably with one account. You need several.

Horizontal and vertical access

Access control breaks in two directions:

Up to five named identities, plus signed-out

Nullgap live testing lets you add up to five named identities for each target, each with an access level: Admin, Standard user or Read-only. Nullgap also tests as a signed-out visitor. With two accounts at the same level you can test horizontal access; with different levels, vertical access.

Passwords and tokens for these accounts are sealed: encrypted for your workspace and never shown again, not even to you.

The access matrix

For each resource it finds, Nullgap tries to reach it as each identity and records what happened. The result is an access matrix. A cell is marked proven only when the cross-account read passes the same four checks as any other finding.

Sample access matrix: GET /invoices/1002, owned by Standard user B (illustrative)
IdentityExpectedResult
Standard user B (owner)AllowedAllowed
AdminAllowedAllowed
Standard user ARefusedProven: read B’s invoice
Read-onlyRefusedRefused
Signed outRefusedRefused

Here the matrix shows a horizontal flaw: Standard user A can read B’s invoice. The control is A opening A’s own invoice, which behaves normally.

Only what you approve

Read more

✓ Proven fixed

Get your first proof today.

Connect a repository and watch Nullgap find, prove and fix. You only ever see what it could prove.

Free 14-day trial · No card · or book a demo with a security engineer