Identity and Access Management
Also called IAM.
The system of identities, roles, and policies that gates access to cloud resources.
What it is
The collection of users, groups, roles, and policies that defines who or what can perform which actions on which cloud resources. It is the primary control plane for authorization across an account or organization.
Why it matters
IAM is the front door of every cloud environment, so misconfigured or over-broad policies are a leading root cause of compromise and a first stop in any cloud investigation.
In practice
An analyst reviewing an intrusion finds a policy granting wildcard actions on all resources, the pivot point the attacker used to escalate.
What to look for
- Policies with wildcards on actions or resources.
- Users or roles with no recent activity that still hold broad rights.
- Access granted directly to users instead of through groups or roles.
Common mistake
Reviewing policies once at setup. Permissions drift as people and services change, so review them on a schedule.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Amazon GuardDuty Cloud service
AWS threat detection that analyzes CloudTrail, VPC flow logs and DNS logs.
-
Microsoft Defender for Cloud Commercial
Posture and threat protection for Azure, AWS and Google Cloud.
-
Wiz Commercial
Maps cloud resources, identities and exposures into one graph of risk.
-
Prowler Open source
An open source tool that checks cloud accounts against benchmarks such as CIS.
Read next
- Over-Permissioned Role: An identity granted far more access than its actual job requires.
- Role Assumption: Temporarily taking on a role's permissions to act as a different identity.
- Cloud Privilege Escalation: Abusing IAM relationships to gain higher access than originally granted.