Release preparation / engineering fieldbook
WEB APP
PENTESTING
Explore Kroll
Describe the permissions

Describe application roles as permission decisions

A permission map explains who should be able to do what, to which object and in which state. It is more useful for scope preparation than a list of role names alone.

Start with a business operation

For an illustrative project workspace, consider viewing an export. The relevant dimensions may include organization membership, export ownership and whether the export is still valid. An administrator label does not automatically answer all of those questions.

Actor and context Intended decision to confirm with the owner
Member viewing a permitted workspace export Allow under the documented membership rule
Member from another organization Deny access to the other organization’s export
Former member after removal Apply the documented revocation behavior
Support operator Use only the separately authorized support workflow

These are example requirements, not results from an executed assessment. Replace them with the application owner’s actual policy.

Include relationships and transitions

Two people with the same role may own different records. A user’s membership can change after a record or link is created. Note which transitions should affect access and when the application is expected to enforce them.

Ask the product owner to resolve ambiguous rules before the assessment. An assessor can observe behavior, but a business decision about who should be authorized needs an accountable owner.

Prepare identities without exposing real users

Use agreed test accounts and representative records. Keep credentials in a secure handoff channel, not in the permission table. Record role and tenant context so the assessor can interpret observations while minimizing sensitive information.

If a required actor cannot be supplied, preserve that coverage gap. Do not treat inability to examine a boundary as evidence that the boundary is correctly enforced.

Carry the rule into remediation

When a finding is accepted, link it to the specific permission decision. The repair acceptance condition should refer to that rule as well as legitimate allowed behavior. The engineering retest entry shows why a visual interface change and a server-side authorization repair are different claims.

Continue reading

Cite this entry

Web App Pentesting. “Describe application roles as permission decisions.” Reviewed 2026-11-16.
https://webapppentesting.com/role-boundaries/