Does each AI agent, pipeline and application have its own cloud identity, not a shared one or a person's credentials?
Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.
Question 23 of the assessment asks: Does each AI agent, pipeline and application have its own cloud identity, not a shared one or a person's credentials? If an agent shares an identity, you cannot tell what it did and you cannot cut its access without breaking other things.
Start the assessment ยท All 40 questions
Why it matters
If an agent shares an identity, you cannot tell what it did and you cannot cut its access without breaking other things.
Answers and what each is worth
| Answer | Value |
|---|---|
| Yes, one identity per agent or application | 1 |
| Some share an identity | 0.5 |
| No or not known | 0 |
How to check it in each cloud
- AWS
- Check that each Bedrock agent, Lambda or container that calls models has its own execution role, and that CloudTrail userIdentity shows distinct roles per agent.
- Azure
- Check that each AI app uses its own managed identity and that Azure OpenAI or AI Foundry role assignments are not made to a shared principal.
- Google Cloud
- Check that each Vertex AI agent or job runs as its own service account, not the default Compute Engine service account.
The fix
Give every AI agent and pipeline a dedicated identity and remove the shared roles and personal tokens it used. Effort: medium.
Where it comes from
- Microsoft cloud security benchmark AI-4: Apply least privilege for agent functions
- NIST SP 800-53 Rev. 5 IA-2: source
Related pages
Sources
- Microsoft cloud security benchmark AI-4, read 16 Nov 2026
- NIST SP 800-53 Rev. 5 IA-2, read 16 Nov 2026
Last reviewed 16 Nov 2026.