AWOSS-DEL: Delegation, Authority, And Identity

Objective:

The scoped agentic workspace system should make human delegation, agent authority, identity binding, and approval responsibility explicit so that an agent's actions cannot silently exceed the intended authority of the user, role, or workflow.

Primary layer: runtime platform.

Typical owner: identity/IAM owner and workflow approver.

Applicability:

Applies when agents can act under user, service-account, organizational, workflow, or connector authority.

Level 1 Candidate Requirements

AWOSS-DEL-L1-001: The scoped agentic workspace system MUST document the identity or authority model used when agents invoke tools, connectors, or workspace resources, including whether actions are bound to a human user, role, workflow, service account, shared account, or system identity.

AWOSS-DEL-L1-002: The scoped agentic workspace system MUST identify action classes where an agent acts with delegated, administrative, production, external-communication, sensitive-data, or system authority.

AWOSS-DEL-L1-003: The scoped agentic workspace system MUST identify which human roles can delegate work to agents, which human roles can approve high-impact actions, and whether execution and approval may be performed by the same role.

Level 2 Candidate Requirements

AWOSS-DEL-L2-001: The scoped agentic workspace system MUST enforce least-privilege authority for production agent workflows, limiting agent-accessible actions and resources to the approved purpose, scope, and duration.

AWOSS-DEL-L2-002: The scoped agentic workspace system MUST distinguish ordinary user delegation, administrative authority, production authority, and external communication authority in policy or configuration, including the approval or oversight expectations for each category.

AWOSS-DEL-L2-003: The scoped agentic workspace system MUST record the user, role, service account, workflow identity, or agent identity associated with each high-impact action request and approval decision.

Level 3 Candidate Requirements

AWOSS-DEL-L3-001: The scoped agentic workspace system MUST provide strong separation between agent execution authority and human approval authority for high-impact action classes.

AWOSS-DEL-L3-002: The scoped agentic workspace system MUST periodically review delegated authority paths for excessive privilege, stale access, shared credentials, or unreviewed service-account use.

AWOSS-DEL-L3-003: The scoped agentic workspace system SHOULD support step-up approval or stronger authorization for actions involving production systems, privileged identity changes, sensitive data export, financial impact, or external commitments.

Minimum evidence examples:

• identity and authority model
• agent identity record or equivalent
• role and approver matrix
• runtime permission policy
• authorization or impersonation test record
• sampled high-impact action receipts
• access review or delegated-authority review
• just-in-time or temporary authority record where applicable
• service-account inventory where applicable

Mapping notes:

• The completed crosswalk treats AWOSS-DEL as a candidate-control family shaped by identity, delegation, accountability, human oversight, privilege, and agent-impersonation signals from EU AI Act, OWASP AISVS, AIUC-1, CSA MAESTRO, NIST AI RMF, ISO/IEC 42001, Five Eyes guidance, and MITRE ATLAS. Governance evidence must be paired with runtime or identity-system evidence before stronger implementation claims are made.

Claim limits:

• Authority documentation and receipts support evidence for selected delegation controls. They do not prove legal sufficiency, AISVS conformance, AIUC-1 certificate equivalence, full IAM framework satisfaction, or effective runtime enforcement unless supporting runtime evidence is also present.