Identity and Access Management Fundamentals
Identity and access management (IAM) is the set of people, processes, and technology that manages digital identities and controls their access to systems and data. It connects account lifecycles, sign-in checks, access policies, enforcement, and audit records.
itIdentity, access, and cryptography | OpenSkills.info
Course pathWalk it in order
Look it upDip in anytime
Go furtherLeaves this page
Intro
Identity and access management as a control system
Identity and access management (IAM) manages digital identities and controls how those identities use resources. A digital identity is a system's representation of a person, workload, device, or other subject. IAM connects that representation to accounts, authenticators, attributes, permissions, policies, sessions, and audit records.
IAM is not one login screen or one directory. It is a control system spread across the identity lifecycle and the access path. It answers several distinct questions:
- Which subject does an account represent?
- How does the subject prove control of that account?
- Which action may the subject perform on a particular resource?
- Where is that decision enforced?
- How does access change when the subject's relationship with the organization changes?
- Which records explain who requested, approved, received, used, and lost access?
Keeping these questions separate prevents a common mistake: treating successful authentication as permission to do anything.
The identity lifecycle
An identity record usually begins from an authoritative source. A workforce system may supply a person's employment status, manager, and department. A cloud platform may create a workload identity for a service. A partner organization may provide identity information through federation.
Provisioning creates or updates accounts and access from that source. Administration binds attributes, group membership, roles, and authenticators to the account. During use, authentication establishes identity context and authorization evaluates a requested action. Reviews and monitoring look for inappropriate or unused access. Deprovisioning disables accounts, revokes credentials and sessions, and removes grants when the relationship ends.
This lifecycle is often summarized as joiner, mover, and leaver:
Continue the course
This section is part of the paid course.
See pricing to subscribe, or log in if you already have access.
Where this skill leads
Relevant careers
See how this topic contributes to broader role-level skill maps.
Sources
- https://pages.nist.gov/800-63-4/sp800-63.html
Supports
- Digital identity models, subjects, accounts, identity proofing, authentication, federation, and assurance
- Separation of authentication from relying-party authorization
- Quiz answers about authentication and authorization boundaries
- https://pages.nist.gov/800-63-4/sp800-63b.html
Supports
- Authentication factors and authenticator lifecycle
- Session management, reauthentication, expiration, recovery, and revocation
- Quiz answer about active sessions after account changes
- https://pages.nist.gov/800-63-4/sp800-63c.html
Supports
- Identity-provider, relying-party, assertion, trust, identifier, and federation lifecycle concepts
- Local relying-party validation and authorization boundaries
- Quiz answers and reference-link rationale for federation
- https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final
Supports
- Account management, access enforcement, least privilege, separation of duties, audit, and identity controls
- Joiner, mover, leaver governance, access review, reconciliation, and non-human account controls
- Quiz answers about movers, workload inventory, and target-state reconciliation
- https://csrc.nist.gov/projects/role-based-access-control
Supports
- RBAC users, roles, permissions, constraints, history, and ANSI INCITS 359-2004 adoption
- Timeline event dated February 11, 2004
- RBAC reference-link rationale and quiz answer
- https://csrc.nist.gov/projects/role-based-access-control/rbac-library
Supports
- Ferraiolo and Kuhn's 1992 general RBAC model and publication date
- Timeline event for the formal RBAC model
- https://csrc.nist.gov/pubs/sp/800/162/upd2/final
Supports
- ABAC subject, object, operation, environment, attribute, and policy concepts
- Authorization tuple, model comparison, quiz answers, and reference-link rationale
- https://csrc.nist.gov/pubs/sp/800/207/final
Supports
- Resource-focused access, subject and device context, policy decisions, and policy enforcement
- Workload identity, enforcement coverage, and failure considerations
- Quiz answers and advanced reference-link rationale
- https://www.rfc-editor.org/rfc/rfc7644.html
Supports
- HTTP-based cross-domain identity management, users, groups, lifecycle operations, and protocol security
- Federation-versus-provisioning comparison and retry-aware integration discussion
- Quiz answers and reference-link rationale
- https://www.rfc-editor.org/info/rfc7644/
Supports
- SCIM 2.0 publication in September 2015
- Timeline event and dated protocol claim
- https://www.rfc-editor.org/rfc/rfc6749.html
Supports
- OAuth 2.0 authorization framework, roles, limited access, and publication in October 2012
- Timeline relationship between OAuth 2.0 and OpenID Connect
- https://openid.net/specs/openid-connect-core-1_0.html
Supports
- OpenID Connect identity layer, ID Tokens, claims, issuer, subject, audience, nonce, and validation
- Federation validation checklist, quiz answer, and reference-link rationale
- https://openid.net/the-openid-foundation-launches-the-openid-connect-standard/
Supports
- OpenID Connect ratification on February 26, 2014
- Timeline event and significance for interoperable web sign-in
- https://docs.oasis-open.org/security/saml/v2.0/
Supports
- SAML assertions, bindings, profiles, metadata, and enterprise federation
- https://www.oasis-open.org/committees/security/faq.php
Supports
- SAML Technical Committee launch, SAML 1.0 approval, SAML 2.0 approval, and federation inputs
- Timeline event for SAML 2.0 in March 2005
- https://www.oasis-open.org/standard/samlv1-0/
Supports
- SAML 1.0 approval on November 1, 2002
- XML assertions for authentication, attributes, and authorization
- https://www.w3.org/TR/webauthn-2/
Supports
- Public-key credentials, relying parties, authenticators, registration, authentication, and origin binding
- Phishing-resistant authentication and reference-link rationale
- https://www.w3.org/press-releases/2019/webauthn/
Supports
- WebAuthn becoming an official web standard on March 4, 2019
- Timeline event for browser and platform authentication APIs
- https://www.itu.int/rec/T-REC-X.500-198811-S/en
Supports
- X.500 directory concepts, models, and services approved November 25, 1988
- Timeline foundation for distributed directories
- https://datatracker.ietf.org/doc/rfc1487/
Supports
- LDAP publication in July 1993 and client-server directory operations
- Timeline transition from X.500 to lightweight directory access
- https://github.com/sindresorhus/awesome
Supports
- Discovery of the curated Identity and Access Management list
- https://github.com/kdeldycke/awesome-iam
Supports
- Discovery of Keycloak, authentik, Authelia, Kanidm, OpenFGA, and SPIFFE ecosystem projects
- https://www.keycloak.org/documentation
Supports
- Keycloak identity federation, authentication, user management, authorization, and administration guides
- Awesome Links rationale and Landscape placement
- https://www.keycloak.org/
Supports
- Keycloak open-source IAM classification and self-hosted identity-provider role
- https://docs.goauthentik.io/providers/
Supports
- OpenID Connect, OAuth 2.0, SAML, LDAP, proxy, RADIUS, and SCIM provider integrations
- Awesome Links rationale
- https://www.authelia.com/overview/authorization/access-control/
Supports
- Rule-based access control over domains, resources, subjects, networks, methods, and authentication policies
- Awesome Links rationale
- https://kanidm.github.io/kanidm/master/
Supports
- Kanidm account information, authentication, authorization, and service integration roles
- Awesome Links rationale
- https://openfga.dev/docs/fga
Supports
- Relationship-based authorization and external policy-decision architecture
- Awesome Links rationale
- https://spiffe.io/docs/latest/spiffe/concepts/
Supports
- Workload identities, trust domains, short-lived identity documents, and Workload API concepts
- Awesome Links rationale and non-human identity discussion
- https://learn.microsoft.com/en-us/entra/fundamentals/what-is-entra
Supports
- Microsoft Entra identity, access, governance, security, and workload identity roles
- Landscape placement for Microsoft Entra ID
- https://www.okta.com/products/workforce-identity/
Supports
- Workforce authentication, access, governance, and lifecycle capabilities
- Landscape placement for Okta Workforce Identity
- https://www.pingidentity.com/en/platform/pingone-for-workforce.html
Supports
- Workforce identity, access orchestration, application integration, and authentication policy
- Landscape placement for PingOne for Workforce
- https://www.onelogin.com/solutions/workforce-iam
Supports
- Workforce directory, application, device, SSO, MFA, and lifecycle capabilities
- Landscape placement for OneLogin Workforce Identity
- https://jumpcloud.com/support/get-started-directory-integrations
Supports
- Cloud directory synchronization with users, groups, Google Workspace, Microsoft 365, and Active Directory
- Landscape placement for JumpCloud
- https://documentation.sailpoint.com/
Supports
- Identity governance, identities, access, connectors, non-employee, and machine identity management
- Landscape placement for SailPoint Identity Security Cloud
- https://www.cyberark.com/products/workforce-identity/
Supports
- Workforce SSO, adaptive MFA, endpoint authentication, and access controls
- Landscape placement for CyberArk Workforce Identity
