Identity and Access Management Boundaries
What you'll learn: Where the cloud provider's IAM security responsibilities end and yours begin.
The Core Divide
In cloud environments, Identity and Access Management (IAM) is a split responsibility — but the line isn't always obvious. The cloud provider secures the IAM platform itself, while you're responsible for how you configure and use it.
Think of it like a bank vault: the bank builds an impenetrable vault with biometric locks and steel walls (platform security), but you decide who gets keys to your safe deposit box and what they can access inside (configuration and policies).
Provider Responsibilities
Cloud providers secure:
- IAM infrastructure availability — keeping authentication systems online and resilient
- Platform vulnerabilities — patching IAM service software
- Physical security — protecting the servers that run IAM services
- Cryptographic operations — securing credential storage, token generation, and encryption keys
- API security — ensuring the IAM API endpoints themselves resist attacks
They guarantee the mechanism works securely.
Your Responsibilities
You own:
- User and role creation — defining who and what can authenticate
- Permission policies — granting appropriate access levels (least privilege)
- Password and MFA requirements — enforcing strong authentication
- Access key management — rotating credentials, retiring unused keys
- Audit logging review — monitoring who accessed what and when
- Federation configuration — properly integrating external identity providers
- Policy testing — verifying permissions work as intended without over-permissioning
You control who gets in and what they can do.
The Gray Area
Misconfiguration is entirely your problem. A provider won't stop you from creating an overly permissive policy, storing credentials in code, or disabling MFA. The tools are secure; your usage might not be.
Key Takeaway: The cloud provider builds and secures the IAM platform, but you're solely responsible for configuring proper access controls, policies, and credential hygiene — misconfigurations are security incidents you own.