Identity and access management
Identity and access management sets who can do what across your cloud environment. Strong identity controls protect accounts and resources while letting the business move at the speed it needs. This capability covers the best practices for protecting privileged accounts, centralizing identity, enforcing least privilege, establishing data perimeters to guard your organization's boundaries, and keeping permissions tuned over time.
Capability intent
-
Workforce identity is centralized, and access to AWS flows by federation from a single authoritative source that synchronises joiner, mover, and leaver changes automatically.
-
The highest-privilege identities — starting with account root users — are protected, monitored, and used only by exception.
-
Permissions default to least privilege and are refined continuously based on what access is actually used.
-
Organization-wide guardrails and data perimeter controls act independently of individual permission grants, keeping trusted identities, resources, and networks in scope.
-
Workloads and machines obtain short-lived credentials through federation, and the long-lived credentials that remain are inventoried, owned, and rotated on a known schedule.
Common issues to watch for
-
Long-lived IAM access keys persist for workloads, CI/CD pipelines, and on-premises systems where federation is available, leaving credentials in systems that rarely rotate them and often have no clear owner.
-
MFA is not enforced on privileged identity provider users beyond the AWS root user requirement, leaving high-risk identities less protected than the controls that guard them.
-
Break-glass processes depend on the same identity provider or account they are meant to work around, so the path to recover access fails at exactly the moment it is needed.
-
Organization-wide guardrails are missing, overly permissive at the root organizational unit, or absent on security and audit accounts, so detective controls can be disabled by an administrator account with unauthorized access.
-
Permissions are copied from prior projects and reviewed only at audit time, so roles accumulate access well beyond current needs and reviews produce activity rather than reduction.