Softlander Book a call
Agent identity, authorisation, and delegation

Non-human identity governance

Put accountable ownership around non-human identities

The organisation cannot explain which agent accounts are still necessary. The decision is how to put accountable ownership around non-human identities. 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 security governance and platform operations. 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 evidenceIdentity inventories

    Establish the basis for active workload.

  2. Decision boundaryAccountable owner

    Assign review and exception responsibility.

  3. Decision artefactGovernance register

    Retain the scoped finding and its unresolved dependencies.

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

Decision

Frame the decision around active workload

Questions and the evidence they need

Criterion / evidenceActive workload
Inspect identity inventories for the relevant constraint or observation.
Criterion / evidenceAccountable owner
Inspect owners for the relevant constraint or observation.
Criterion / evidenceRetirement control
Inspect usage metadata 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 put accountable ownership around non-human identities. This is relevant to security governance and platform operations when the organisation cannot explain which agent accounts are still necessary. 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 an unused identity keeps permissions because no team owns its periodic review. 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

An inventory becomes governance through ownership decisions

Relationships within identity and delegated authority

Source or conditionActive workload
Reconcile real usage with registered identities.
Crossing or choiceAccountable owner
Assign review and exception responsibility.
Consequence or decisionRetirement control
Remove authority when the business purpose ends.
Follow the check to the accepting resource. Each relationship needs evidence in the actual scope.

What this specialty examines

Governance should connect non-human identities to real operational ownership. Record why the identity exists, where it runs, which resources it reaches and who reviews continued need. A directory entry alone does not show whether the workload is active or justified.

The review should reconcile inventories to active workloads and examine approval, review and removal decisions. 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, central governance improves consistency while local owners understand actual resource needs. 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 active workload

Illustrative working format

BasisIdentity inventories
Use nonsecret metadata to trace issuance, acceptance, and withdrawal responsibility.
ContextOwners
Identify the accountable role and verify its decision rights or availability.
ObservationUsage metadata
Retain the observed conditions and distinguish gaps from contrary evidence.
DependencyApprovals
Connect the accepted action parameters to grant, amendment, expiry, and withdrawal.
Illustrative preparation record. Availability, revision, and handling need confirmation.

Start with identity inventories, owners, usage metadata, approvals and retirement records. 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 an unused identity keeps permissions because no team owns its periodic review 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 active workload through to an accountable finding

From the scoped material to a decision record

  1. Establish conditionsIdentity inventories

    Locate the source of the claimed authority.

  2. Examine the relationshipAccountable owner

    Apply the scoped check to retirement control.

  3. Retain the findingGovernance register

    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 identity inventories, owners, usage metadata, approvals and retirement records with the workflow described by security governance and platform operations. 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

Reconcile identity and workload inventories rather than assuming either is complete. Examine unused grants, unclear ownership and accounts shared across incompatible purposes. Review frequency and removal conditions should follow the operating context and consequence, not merely a uniform calendar exercise.

Select the identity control change

Consolidate the checked paths into a governance register with owner gaps and proposed recertification rules. 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 governance register usable by its owner

Governance register

Illustrative working format

Annotated fieldGovernance register
Identify the assessed workflow, revision, and decision boundary.
Annotated fieldOwner gaps
Name the role, decision right, handoff, and unresolved ownership boundary.
Annotated fieldRecertification rules
Separate demonstrated practice from claims requiring a verified credential authority.
Illustrative artefact structure, not a completed engagement or an observed result.

A useful decision artefact is a governance register with owner gaps and proposed recertification rules. 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 retirement control through a constructed exception

A constructed case and its decision paths

Illustrative scenario

  1. SituationActive workload

    An active machine account has no current business owner.

  2. Question to examineAccountable owner

    Reconcile observed account activity with ownership and retirement records.

  3. Conditional next actionRetirement control

    Assign an accountable owner or pursue removal through the authorised process.

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

Consider a fictional situation: a temporary experimentation account becomes a permanent production dependency without a named service owner. The scenario is illustrative, with no client engagement, executed test or measured improvement implied.

For the experiment account, identify whether it now supports production work. That discovery may require formal ownership and narrower permissions rather than immediate removal. The governance decision should preserve service continuity while resolving unaccountable access.

Scope and next action

Keep the conclusion within named authority paths

Confirm fit before the next commitment

Included boundaryActive workload
This review is limited to named authority paths.
PrerequisiteIdentity inventories
The relevant owner must confirm access and the intended operating conditions.
Claim limitGovernance register
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 the organisation cannot explain which agent accounts are still necessary; 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 orphaned agent identities be handled?

Identify their actual workloads and dependencies before removal. Assign a justified owner and narrow scope where they remain necessary; retire unused authority through a controlled process. Preserve service continuity while resolving unaccountable access.

Which inventories reveal orphaned agent identities?

Start with identity inventories, owners, usage metadata, approvals and retirement records. 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 continued identity need be reviewed?

Reconcile inventories to active workloads and examine approval, review and removal decisions. 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 an identity governance register?

The proposed output is a governance register with owner gaps and proposed recertification rules. 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 an identity be retired rather than renewed?

Retire an identity when its workload or justified purpose has ended. First reconcile dependencies and confirm ownership so removal does not accidentally break an active service or leave another untracked credential behind.

What if existing evidence already answers the question?

Review its scope, provenance and configuration before proposing new work. Existing work from security governance and platform operations 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 identity inventories, owners, usage metadata, approvals and retirement records 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

Least-privilege agent design

Reduce agent permissions to those required by the agreed workflow. The review connects observed action traces, business requirements, permission grants and deny logs to a bounded review of identity and authority, giving the identity control owner a clearer basis for the next action.

Temporary credential architecture

Design short-lived authority that remains usable during real work. The review connects issuance policy, validity periods, renewal paths and task-duration traces to a bounded review of identity and authority, giving the identity control owner a clearer basis for the next action.

Agent impersonation testing

Test whether one actor can convincingly masquerade as an authorised agent. The review connects trusted identity attributes, validation points, test principals and attribution records to a bounded review of identity and authority, giving the identity control owner a clearer basis for the next action.