Agent identity
Identify agents through authenticated, server-bound principals rather than self-reported names.
View in the catalogPlatformIdentity & PolicyThe right authority.
IDENTITY & POLICY
The right authority.
Nothing more.
Connect every action to an identity, a scope and a current policy. Keep personal access and company authority separate.
Discuss your use caseI01—I10 / 10 CAPABILITY AREAS
THE QUESTION THIS PILLAR ANSWERS
Who can do what, and why?
Human identity
Keep the authenticated human authorizer distinct from the client and executing agent.
View in the catalogService accounts
Scope organization-owned identities for unattended workloads without permanent employee impersonation.
View in the catalogRoles and scopes
Limit operations and resources within the applicable tenant, project, application and environment.
View in the catalogPolicy engine
Evaluate shared, versioned rules using trusted inputs. Distinguish observation, warnings, approval and enforcement.
View in the catalogPermissions and entitlements
Intersect policy, consent, delegated authority, resource permissions and plan eligibility.
View in the catalogCredential vaults
Protect independently selected accounts and credentials, with scoped reauthorization and disconnection.
View in the catalogDelegation
Grant bounded, expiring task or child-agent authority without widening the parent’s scope.
View in the catalogMulti-tenant isolation
Preserve tenant and personal/business boundaries across reads, writes, sessions, caches and exports.
View in the catalogCompliance rules
Apply organization-defined requirements through supported controls. Rules alone do not establish certification.
View in the catalogILLUSTRATIVE WORKFLOW
An approval does not outlive its authority.
An agent can request a sensitive action, but approval is only one part of the decision. Re-evaluate the requester, resource and current authority before the protected effect.
A connected account, a paid plan or a model-supplied agent name is not authorization.
BUILD WITH INTENTION