Identity security,
understood.
Understand the concepts. Connect the systems. Build the judgment. A practical IAM reference for your first integration and your next production incident.
Start where you are.
01 — THE LEARNING MAPThree ways in. One connected discipline.
Make the concepts click.
Build a clear mental model of identities, authentication, authorization, and governance.
Start with the six pillars 02 / INTEGRATIONSConnect the moving parts.
Understand SAML, OIDC, SCIM, and the decisions behind an application integration.
Explore the protocols 03 / OPERATIONSWork through the real tasks.
Use structured runbooks for onboarding, offboarding, access reviews, and incident response.
Open the runbooksThe Six Core Pillars
Every IAM program is built on these disciplines. Master each to build a mature, auditable security posture.
Authentication
Authorization
Directory Services
Identity Lifecycle
Governance & Compliance
Privileged Access
Key Concepts & Frameworks
Open a concept for explanations, implementation notes, and illustrative examples. Save your progress as you go.
001
SSO allows a user to authenticate once and gain access to multiple applications without re-entering credentials. It leverages a trusted Identity Provider (IdP) and protocols like SAML 2.0 or OIDC.
- Choose an IdP (Okta, Microsoft Entra ID, Ping Identity, Google Workspace)
- Register each Service Provider (app) in the IdP console
- Configure SAML assertions or OIDC claims and attribute mappings
- Map user attributes to app-specific roles and groups
- Test the SSO flow and configure fallback authentication
002
MFA requires two or more verification factors: something you know (password), something you have (TOTP app, hardware key), and something you are (biometric). MFA reduces account compromise risk; resistance to phishing depends on the method and deployment.
- FIDO2 / WebAuthn — phishing-resistant security keys and passkeys
- Authenticator app TOTP — resistant to SIM swapping, but codes can still be phished
- Number-matched push — reduces push fatigue; not inherently phishing-resistant
- SMS OTP — vulnerable to SIM swapping and phishing; use stronger methods when feasible
003
Permissions are assigned to roles, not individuals. Users are granted roles that bundle appropriate permissions for their job function. Simplifies access management; least privilege still depends on role design and review.
- RBAC — permissions tied to named job function roles
- ABAC — attributes (dept, location, device type) determine access
- PBAC — policy engine evaluates all conditions dynamically at runtime
004
"Never trust, always verify." Network location alone does not establish trust. Evaluate identity, device, resource, and policy before access; reassess during the session as supported.
- Verify explicitly — always use all available signals (identity, device, location)
- Use least privilege — JIT and JEA access with time-bound entitlements
- Assume breach — minimize blast radius, segment networks, encrypt in transit
005
PAM secures, controls, and audits access to critical systems by privileged users (admins, service accounts, DevOps). Compromised privileged credentials can give an attacker broad control of critical systems.
- Credential vaulting — auto-store and rotate passwords/SSH keys
- Session recording — capture supported privileged sessions under policy and privacy requirements
- Just-in-Time (JIT) access — elevate only when needed, auto-expire after TTL
- Least privilege enforcement — no standing admin rights for any user
006
SCIM (System for Cross-domain Identity Management) is an open standard for automating user provisioning and deprovisioning between identity systems and cloud applications via a REST API.
- POST /Users — Create new account in target SaaS app
- PATCH /Users/{id} — Update attributes (title, department, manager)
- DELETE /Users/{id} — Delete the resource; use PATCH active:false for account deactivation where supported
007
- SAML 2.0 — XML-based federation widely used for enterprise browser SSO
- OAuth 2.0 — Delegated authorization framework, issues access tokens
- OIDC — OAuth 2.0 + identity layer (ID tokens in JWT format)
008
Periodic campaigns where managers or data owners certify (approve or revoke) user entitlements. Reviews support access-control and audit objectives. Scope and frequency depend on applicable requirements, risk, and organizational policy.
- Privileged accounts — Quarterly (high risk, high change rate)
- Sensitive data access — Semi-annually
- Standard entitlements — Annually
- Contractor / vendor accounts — Monthly or on-contract expiry
Operational Workflows
Operational starting points. Adapt approvals, timing, and evidence requirements to your environment.
No matching runbooks. Try a different task.
Onboarding a New Employee
Offboarding / Termination
Password / MFA Reset
Access Request & Approval
New SaaS App SSO Integration
Suspicious Login Response
Quarterly Access Review Campaign
Audit Evidence Package
IAM Skills Matrix
Technical and operational skills for IAM roles — from analyst to architect level.
| Skill | Category | Practice focus | Notes |
|---|---|---|---|
| SAML 2.0 / OIDC Configuration | Core | Hands-on practice | Critical for SSO integrations |
| Okta Administration | Tool | Hands-on practice | Market-leading IdP |
| Microsoft Entra ID | Tool | Hands-on practice | Essential for Microsoft environments |
| Role & Permission Design | Core | Hands-on practice | RBAC / ABAC modeling |
| SCIM Provisioning | Core | Hands-on practice | Automates lifecycle events |
| Active Directory / LDAP | Tool | Hands-on practice | On-prem directory backbone |
| CyberArk / PAM Tools | Tool | Hands-on practice | Privileged access management |
| Access Certification Campaigns | Gov | Hands-on practice | SailPoint, Saviynt |
| SOX / SOC 2 Controls | Gov | Hands-on practice | Audit evidence prep |
| Conditional Access Policies | Core | Hands-on practice | Zero Trust enforcement |
| OAuth 2.0 / Token Management | Core | Hands-on practice | API & M2M auth flows |
| PowerShell / Graph API Scripting | Ops | Hands-on practice | IAM automation |
| SIEM Log Analysis | Ops | Hands-on practice | Splunk, Sentinel, QRadar |
| Identity Incident Response | Ops | Hands-on practice | Account takeover playbooks |
IAM Tool Landscape
Major platforms across the IAM ecosystem — organized by capability category.
Okta
Microsoft Entra ID
Ping Identity
Google Workspace
Auth0 / CIC
ForgeRock
CyberArk
BeyondTrust
HashiCorp Vault
Delinea
SailPoint
Saviynt
IBM ISIM
Omada
Glossary of IAM Terms
Quick-reference definitions for common acronyms and concepts across the IAM discipline.
Identity Provider
IdPA system that creates, manages, and authenticates digital identities. Issues signed assertions or tokens to relying service providers.
Service Provider
SPAn application that relies on an IdP for authentication. Trusts and validates tokens or assertions issued by the IdP.
Security Assertion Markup Language
SAML 2.0XML-based open standard for exchanging authentication and authorization data between identity and service providers.
OpenID Connect
OIDCIdentity layer built on top of OAuth 2.0. Provides ID tokens in JWT format for authenticating end users.
JSON Web Token
JWTCompact, URL-safe token format for transmitting signed claims. A signed compact JWT (JWS) uses three base64url-encoded segments: header.payload.signature. Encrypted JWTs (JWE) use five segments.
Just-in-Time Access
JITTemporary privilege elevation granted on-demand for a limited TTL, then automatically revoked — eliminating standing privileges.
Privileged Access Management
PAMControls for securing, monitoring, and auditing privileged accounts and credentials across critical infrastructure.
Identity Governance & Admin
IGAProcesses and tools for managing user entitlements, running access certifications, and enforcing policy at enterprise scale.
Segregation of Duties
SoDPolicy preventing any single user from holding conflicting access rights that could enable fraud, error, or unauthorized action.
Least Privilege Principle
PoLPUsers and systems should hold the minimum access rights needed to perform their function — no more, no less.
Customer IAM
CIAMIAM focused on managing external customer identities at scale, with emphasis on UX, privacy consent, and federation.
User & Entity Behavior Analytics
UEBAML-driven analytics that detect anomalous behavior patterns indicative of compromise, insider threat, or lateral movement.
Attribute-Based Access Control
ABACAccess control where decisions are based on user, resource, and environment attributes evaluated dynamically at runtime.
Credential Vaulting
—Securely storing and managing privileged credentials with automated rotation and a check-out workflow for access.
Adaptive Authentication
—Risk-based authentication that dynamically adjusts challenge requirements based on contextual risk signals.
Entitlement
—A specific permission or access right granted to an identity — such as an app role, group membership, or file permission.
Federated Identity
—An arrangement that allows a user to use the same authenticated identity across multiple separate security domains.
Deprovisioning
—The process of removing or disabling a user's access rights when they no longer require them — triggered by JML events.
Discussion Board
Share ideas and ask questions. Use fictional examples; keep client data, credentials, and personal information out of posts.
Keep your reference close.
Standards and vendor documentation for the details that matter. Examples above illustrate concepts; they are not production configurations.
Technical corrections reviewed 19 October 2026 · Independent educational reference by Dheeraj Nimmala.