Softlander Book a call
Agent identity, authorisation, and delegation

Authorisation policy testing

Verify authorisation policy decisions against intended rules

Policy changes are reviewed as text without testing denied paths. The decision is how to verify authorisation policy decisions against intended rules. The work begins with your actual workflow and looks for the evidence that separates intended behaviour from a consequential exception. It is particularly relevant to IAM policy engineers and application owners. A useful outcome is an explicit account of what was examined, what remains uncertain, and which decision the evidence can support.

Book a 30 minute readiness callBrowse this capability group

The identity and delegated authority relationship

  1. Starting evidencePolicy versions

    Establish the basis for expected decision.

  2. Decision boundaryAttribute fixture

    Exercise missing or conflicting context.

  3. Decision artefactPolicy test suite

    Retain the scoped finding and its unresolved dependencies.

Conceptual model. Technical findings do not settle a disputed mandate.

Decision

Frame the decision around expected decision

Questions and the evidence they need

Criterion / evidenceExpected decision
Inspect policy versions for the relevant constraint or observation.
Criterion / evidenceAttribute fixture
Inspect subject-resource fixtures for the relevant constraint or observation.
Criterion / evidenceDeployed evaluator
Inspect action catalogues for the relevant constraint or observation.
Read each criterion against the available evidence before deciding that additional work is needed.

The decision is how to verify authorisation policy decisions against intended rules. This is relevant to IAM policy engineers and application owners when policy changes are reviewed as text without testing denied paths. Name the affected workflow, the consequence of a wrong decision, and the owner who can act on the result. The initial discussion should establish which evidence is already available and which uncertainty is material enough to investigate.

The specific failure hypothesis is that a new allow rule overrides a restrictive condition for an unrelated resource group. It remains a hypothesis until examined in the deployment. Existing internal tests or operating records may already resolve it; identify the uncovered question before commissioning additional work.

Mechanism

Policy tests need explicit denied and ambiguous cases

Relationships within identity and delegated authority

Source or conditionExpected decision
Version the rule and intended interpretation.
Crossing or choiceAttribute fixture
Exercise missing or conflicting context.
Consequence or decisionDeployed evaluator
Compare actual enforcement with the decision table.
Follow the check to the accepting resource. Each relationship needs evidence in the actual scope.

What this specialty examines

Policy testing should exercise the deployed decision path, not only a local policy file. Include rule precedence, missing attributes, broad wildcards and unexpected resource relationships. Explain what an allow or deny means and where that decision is enforced.

The review should exercise allow, deny, missing-attribute and conflicting-rule cases against the deployed policy decision path. Identify the normal route, relevant exceptions and the authoritative record of the outcome. Inspect the relevant business-system record, enforcement event or process evidence alongside any reported status. Keep incomplete cases visible, with an explanation of what their absence prevents the owner from concluding.

The tradeoff to make explicit

For this decision, comprehensive combinations increase assurance evidence while large policy spaces require risk-based selection. Compare the available design or operating choices against the same intended outcome. If one option removes a required control or changes the task boundary, describe that difference before treating its apparent simplicity, speed or lower effort as an improvement. The decision should expose the tradeoff instead of burying it in an aggregate score.

Preparation

Connect the working inputs to the boundary being examined

Evidence packet for expected decision

Illustrative working format

BasisPolicy versions
Confirm the applicable revision and who resolves disputed interpretation.
ContextSubject-resource fixtures
Keep expected behaviour and the limits of the constructed example explicit.
ObservationAction catalogues
Retain the observed conditions and distinguish gaps from contrary evidence.
DependencyExpected decision tables
Identify provenance and the specific decision this material can inform.
Illustrative preparation record. Availability, revision, and handling need confirmation.

Start with policy versions, subject-resource fixtures, action catalogues and expected decision tables. Identify the owner, revision and operating context of each source. Sanitised examples may support initial design, but differences from actual conditions should remain explicit. Where direct access is unsuitable, a customer-controlled evidence or execution route may be considered, with agreed handling and retention.

The scope also needs the identity control owner, agreed expectations for a representative subject-action-resource case, and the authority to inspect the relevant boundary. Specify what evidence would distinguish the failure in which a new allow rule overrides a restrictive condition for an unrelated resource group from acceptable behaviour. If stakeholders disagree about intended behaviour, resolve the interpretation before classifying the observed difference as a defect.

How the work proceeds

Carry expected decision through to an accountable finding

From the scoped material to a decision record

  1. Establish conditionsPolicy versions

    Locate the source of the claimed authority.

  2. Examine the relationshipAttribute fixture

    Apply the scoped check to deployed evaluator.

  3. Retain the findingPolicy test suite

    Record the evidence, open dependencies, and the owner’s next decision.

Proposed sequence; resolve interpretation or access gaps before relying on the next step.

Map principals, resources and authority

Reconcile policy versions, subject-resource fixtures, action catalogues and expected decision tables with the workflow described by IAM policy engineers and application owners. Identify the initiating actor, executing workload, target resource and component that grants access. Prepare paired cases that differ in one material authority condition, such as assignment, tenant, expiry or approval. The preparation output is an action map showing which permission is expected at each boundary and which records can verify it.

Exercise and review the authority path

Keep expected decisions under policy-owner review. An automated test can consistently enforce the wrong interpretation if the table was never agreed. Retain reasons for intentional exceptions and test how they interact with restrictive rules elsewhere in the policy set.

Select the identity control change

Consolidate the checked paths into a policy test suite and discrepancy report with rule-level traceability. Distinguish an identity-verification problem from an excessive permission, lost delegation context or delayed withdrawal. Assign the proposed change to the component that controls the affected action. Before recommending wider use, identify the allowed case and denied counterpart that would demonstrate the revised boundary without breaking legitimate work.

Indicative artefact

Make the policy test suite usable by its owner

Policy test suite

Illustrative working format

Annotated fieldPolicy test suite
Identify the governing revision, exception path, and accountable interpretation owner.
Annotated fieldRule-level traceability
Identify the governing revision, exception path, and accountable interpretation owner.
Annotated fieldAttribute fixture evidence
Retain selection rationale, accepted alternatives, and unexamined task conditions.
Illustrative artefact structure, not a completed engagement or an observed result.

A useful decision artefact is a policy test suite and discrepancy report with rule-level traceability. Supporting material may include selected cases, configuration or process records, evidence references, a disagreement log and prioritised actions. Retain the case selection rationale and material disagreements alongside the result; otherwise the result may be mistaken for complete coverage.

Illustrative scenario

Examine deployed evaluator through a constructed exception

A constructed case and its decision paths

Illustrative scenario

  1. SituationExpected decision

    A missing subject attribute changes a deny decision into an allow.

  2. Question to examineAttribute fixture

    Exercise the missing attribute against the deployed evaluator.

  3. Conditional next actionDeployed evaluator

    Correct the rule or interpretation before accepting the allow result.

Fictional example. No executed test, customer engagement, or measured outcome is implied.

Consider a fictional situation: a rule intended to enable ticket editing also permits bulk export when an action wildcard matches both. The scenario is illustrative, with no client engagement, executed test or measured improvement implied.

For editing versus export, use separate action fixtures that differ only in the operation. A wildcard that admits both should produce an explicit discrepancy. The fix can then be retested without obscuring the original adverse result.

Scope and next action

Keep the conclusion within named authority paths

Confirm fit before the next commitment

Included boundaryExpected decision
This review is limited to named authority paths.
PrerequisitePolicy versions
The relevant owner must confirm access and the intended operating conditions.
Claim limitPolicy test suite
Technical findings do not settle a disputed mandate.
Bring the triggering change and existing evidence; resolve the dependency that could alter the decision.

Identity design and technical testing do not establish a legal mandate or resolve a disputed business authorisation. Qualified IAM review is needed for material control conclusions. Any engagement depends on an agreed scope, qualified team, authorised access and confirmed availability. Bring the affected workflow, its current configuration or process, the triggering change and the evidence already available. The immediate scope question is prompted by the situation in which policy changes are reviewed as text without testing denied paths; confirm which missing observation would change the owner’s next action.

Ways to engage

Related engagement scopes

Agent Release Readiness Review

The Agent Release Readiness Review is a fixed-scope, three-week independent test of one AI agent workflow that shows a release board what the agent does, what it is allowed to do and what happens when it is wrong, and ends in a signed recommendation.

3 weeksRead about this offer

AI Agent Authorisation Review

Make delegated authority inspectable. Trace who an agent acts for, what it can access and how that access can be withdrawn.

Read about this offer

AI Agent Runtime Security Review

Make every delegation explicit. Examine who the agent acts for, where it can execute and which tools it can reach when instructions alone are not enough.

Read about this offer

Continue exploring

Related insights and resources

Whitepaper15 MIN READ

Designing agent authority boundaries

Turn agent permissions into an enforceable action contract. Separate a model's suggestion from a resource owner's authorisation, test the boundary, and make delegation and revocation reviewable.

Agent security6 MIN READ

The permission boundary behind every agent action

An agent can only be evaluated in the context of what its tools allow. Examine identity, delegated authority and action boundaries before you put a workflow in motion.

Whitepaper5 MIN READ

Before your agent can act, define its authority

A working paper for the moment an AI system moves from advice to action. Map identity, permissions, approvals and recovery into an authority model your team can review and test.

A little more clarity

Questions to consider.

Start with the questions that shape a better decision.

How should missing context affect an authorisation decision?

Define the rule explicitly with the policy owner. For protected operations, missing required context should not silently become broad permission. Test absent, malformed and conflicting attributes at the actual enforcement path.

Which decision tables define intended policy outcomes?

Start with policy versions, subject-resource fixtures, action catalogues and expected decision tables. Record their revision, owner and relationship to the intended workflow. Missing context should be identified before interpreting outcomes; a sanitised fixture is useful only when its relevant differences from the operating case are understood.

How should wildcard and precedence rules be tested?

Exercise allow, deny, missing-attribute and conflicting-rule cases against the deployed policy decision path. Observe the authenticated principal, mandate and resource decision separately. Include a permitted action and a denied counterpart so the review can establish whether authority is narrow enough without making legitimate work impossible.

What belongs in a policy discrepancy report?

The proposed output is a policy test suite and discrepancy report with rule-level traceability. Include the selected conditions, supporting observations, unresolved differences and next decision. A reviewer should be able to follow each important conclusion back to its evidence and understand the limits without depending on an undocumented explanation from the author.

When should missing attributes cause denial?

Deny when required context is missing and no explicitly approved rule authorises the operation without it. Test that absence does not trigger a permissive default or bypass a restrictive condition.

What if existing evidence already answers the question?

Review its scope, provenance and configuration before proposing new work. Existing work from IAM policy engineers and application owners may already be sufficient. In that case, capture the decision, unresolved limitations and the change that would require another review. Additional assessment should address a real gap.

What would make the findings inconclusive?

Missing policy versions, subject-resource fixtures, action catalogues and expected decision tables can prevent a reliable interpretation, depending on the case. Record the specific missing observation and its implication. The owner can supply evidence, narrow the claim or defer the dependent decision; an incomplete case should not silently be counted as a pass.

Start with the decision you need to make.

Tell us about the agent workflow you want reviewed, and where you need greater clarity. Scope and availability are confirmed together.

Book a 30 minute readiness call Get the agent release checklist

Connected disciplines

Consent and mandate management

Manage mandates as records that can change and expire. The review connects mandate versions, consent interactions, withdrawal events and execution queues to a bounded review of identity and authority, giving the identity control owner a clearer basis for the next action.

Agent transaction signing

Bind transaction approval to the exact action being executed. The review connects canonical transaction fields, signing flows, verifier rules and replay controls to a bounded review of identity and authority, giving the identity control owner a clearer basis for the next action.

Identity revocation testing

Verify that withdrawn authority stops future agent action. The review connects revocation events, token caches, queued jobs and downstream permission checks to a bounded review of identity and authority, giving the identity control owner a clearer basis for the next action.