Commissioned by Kiteworks
Give each agent workflow a distinct, verifiable identity linked to the person who authorized it. Record its task, permitted data and operations, and when its access should expire. Avoid shared logins that hide which agent acted. An access record should identify both the agent and the human authorization behind its request.
A shared login may show that a system connected while concealing the agent and task. Authenticate the person delegating the work, verify credentials outside the model, and keep the agent, workflow and authorization available to access controls and audit records. Even when an agent inherits approved user permissions, its activity should remain distinguishable from the person acting directly. An identity stated in a prompt is not authenticated identity.
Kiteworks’s Agent Marketplace announcement says governed operations are attributed to the authenticated user who authorized them. Its identity guidance also recommends workflow credentials carrying approved data, operations and expiration. Check what your integration actually issues and inspect an access event to confirm both sides remain attributable. These recommendations do not imply every connection uses the same token structure, and published product descriptions do not guarantee deployment compliance.
Put this into practice
- Authenticate the authorizer and distinguish each agent workflow.
- Verify credential scope, permitted operations and expiry.
- Inspect access records for both agent identity and human authorization.
