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:
- Horizontal: one user reaches another user’s data at the same level. Customer A opens customer B’s invoice.
- Vertical: a user reaches something meant for a higher level. A read-only member changes a setting only admins should touch, or a signed-out visitor reads a signed-in page.
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.
| Identity | Expected | Result |
|---|---|---|
| Standard user B (owner) | Allowed | Allowed |
| Admin | Allowed | Allowed |
| Standard user A | Refused | Proven: read B’s invoice |
| Read-only | Refused | Refused |
| Signed out | Refused | Refused |
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
- Scope list: every request is checked against the staging addresses you list. Private addresses are never reached.
- Read-only by default: Nullgap does not change state in your app unless you allow it.
- Sealed secrets: account credentials are encrypted and never shown again.