Identity and security

Identity work on this site is the IAM, federation and workload-identity model that grants access. It is not a general security-product review.

Who this topic is for

Identity owners and platform engineers who need a trust model that matches the provider they actually run, including a second cloud when one already exists.

Problems these pages cover

  • Human and workload identities share the same long-lived keys.
  • A second provider was added and SSO was copied rather than federated.
  • Break-glass paths are undocumented until someone is locked out.

Recommended reading order

  1. IAM fundamentals
  2. What a cross-cloud security incident changed in a Kubernetes rebuild
  3. Designing multi-cloud identity
  4. Shared responsibility model

Guides in this topic

Ankit Mehta

Designing multi-cloud identity

The single-cloud baseline is IAM fundamentals. Whether a second cloud is justified at all is single cloud vs multi-cloud. AWS IAM Identity Center (used by Control Tower) maps IdP groups to permission sets, then to accounts in Organizations. Azure RBAC maps Entra groups to roles on management groups, subscriptions and resource groups.

Related runbooks

Consulting

Scoped review for this topic: Multi-cloud consulting.