TL;DR: Cloud-managed non-human identities create different security failure modes across AWS, Google Cloud and Microsoft Entra ID, Vectra AI says, including confused deputy exposure, transitive access abuse and service principal hijacking. Cloud governance has to track which provider owns each trust boundary, or the wrong identity control assumptions carry across platforms.
Editorial analysis by NHI Mgmt Group, based on content published by Vectra AI: “Cloud Security Grey Zone: Who Owns the Risk of Managed Identities?”.
Key questions
Q: Why do multi-cloud environments create more identity risk than single-cloud estates?
A: Because the risk sits in the gaps between providers.
Q: What should security teams look for when a cloud service can act on behalf of another principal?
A: Look for explicit source binding, narrow service scope and evidence that the service cannot be redirected into broader action than intended.
A: Teams lose sight of who actually controls the trust boundary.
Practitioner guidance
- Audit AWS resource policy condition keys Review every cross-service trust relationship for aws:SourceArn or equivalent source-binding conditions, especially where services can act on behalf of another principal.
- Restrict Google Cloud service exposure Keep only the services that are operationally required enabled, then monitor service-agent behaviour for unexpected delegated actions or unusual access patterns.
- Verify Entra service principal protections Check whether appInstancePropertyLock is enabled on high-impact Microsoft first-party applications and confirm which tenant-local principals can accept added credentials.
Bottom line: Cloud-managed identities are not governed uniformly, because each provider exposes a different trust boundary and a different failure mode.
Glossary terms: CSP-Managed Non-Human Identity, Confused Deputy, Service Principal Hijacking, Transitive Access
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Managed identity risk is now a provider-architecture problem, not a single cloud-control problem. AWS, Google Cloud and Microsoft Entra ID each shift trust and control in different ways, so the same defensive checklist will miss the real failure mode in at least one environment. Multi-cloud identity programmes need separate assumptions for who can configure, who can observe, and who can revoke. Practitioners should govern each platform on its own terms rather than assuming managed identities are interchangeable.
A few things that frame the scale:
- NHIs outnumber human identities by 25x to 50x in modern enterprises, according to the Ultimate Guide to NHIs.
A question worth separating out:
A: Credential insertion into tenant-local service principals should be treated as a high-priority escalation path. If administrators can add credentials to a principal tied to a first-party application, the tenant inherits a powerful identity risk that can bypass the intended separation between provider-managed and customer-managed control.
👉 Read our full editorial: Managed identities create different cloud risk models across AWS, Google and Entra