Identity and Access Management (IAM) Basics
who are you, what may you do, and who checked
Identity and access management is the discipline of making sure the right people and systems have the right access to the right things, for the right reasons, at the right time. Most breaches involve a stolen or misused identity, so IAM is one of the most important areas in security.[1]
The building blocks
- Identification: claiming an identity ("I am Asha").
- Authentication (authN): proving it with a password, MFA, a key or a certificate.
- Authorization (authZ): deciding what that identity may do.
- Accountability: logging who did what so actions can be traced.
People often mix up the second and third: authentication is who you are, authorization is what you are allowed to do.
Access models
- Role-based access control (RBAC): permissions belong to roles such as "payroll clerk", and people are assigned roles. Easy to manage and review.
- Attribute-based access control (ABAC): decisions use attributes of the user, resource and situation (department, data sensitivity, device, time).
- Least privilege: give only the access needed for the job, and no more.
- Segregation of duties: split sensitive tasks so no single person can complete and hide a fraud.
The identity lifecycle
Access should follow the joiner, mover, leaver process: grant what a new starter needs, adjust when someone changes role (and remove what they no longer need), and cut everything promptly when they leave. "Permission creep" from people who changed roles but kept old access is one of the most common audit findings.
Privileged and non-human accounts
- Privileged access management (PAM) protects powerful accounts with vaulted credentials, approval, session recording and just-in-time elevation that expires automatically.
- Service accounts and API keys are identities too. They often have broad access, never expire and no owner, which makes them attractive targets. Give each one an owner, minimum rights and rotation.
Keeping it honest
- Access reviews (recertification): owners periodically confirm who still needs what.
- Single sign-on and MFA reduce password sprawl and strengthen sign-in.
- Logging and monitoring of sign-ins and privilege use.
- Strong, evidence-based processes for requesting and approving access.[2]
Sources
Test yourself
My notes
Private — saved only on this device, never sent anywhere.