Join our Newsletter — 33% off our NHI Course

Platform-level managed identities: where does tenant trust break down?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 1 year ago
Posts: 18346
Topic starter  

TL;DR: Azure’s platform-level managed identities are globally scoped, customer-invisible actors that can create a cross-tenant confused deputy problem when customer-assigned RBAC grants let platform services reach backend resources, according to Vectra AI. The trust boundary fails when a provider-managed identity can act beyond the customer’s direct control.

Editorial analysis by NHI Mgmt Group, based on content published by Vectra AI: “Azure’s Hidden Operators: A Threat Model for Platform-Level Managed Identities”.

Key questions

Q: What breaks when a cloud service uses a provider-owned managed identity outside the tenant boundary?

A: The customer loses direct ownership of the actor while still depending on it for access to backend resources.

Q: Why do provider-managed identities create cross-tenant confused deputy risk?

A: Because a powerful intermediary can be tricked into using its own authority on behalf of a caller that should not inherit that authority.

Q: How can security teams tell whether a managed-identity control is only working at provisioning time?

A: If the control depends on a deployment workflow, but the service can later forward runtime requests to arbitrary backend targets, the check is incomplete.

Practitioner guidance

  • Inventory provider-owned identity touchpoints Identify services where Azure-managed platform identities can access your Key Vault, storage, APIs, or third-party connectors, and classify them separately from customer-managed managed identities.
  • Review runtime proxy and connector flows Test API Connection and similar forwarding paths for path traversal, target-URI manipulation, and scope escape before assuming deployment-time checks cover runtime access.
  • Validate RBAC grants at connection creation Require explicit approval for every customer-assigned RBAC grant that enables a provider-managed identity to reach backend resources, and keep an exception record for each one.

Bottom line: Platform-owned managed identities can act on customer resources without ever becoming customer-owned identities, which changes how governance must be assigned.

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →



   
Quote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.