Identity and Access Management (IAM)
Domain 5 of the ISC2 CISSP exam outline effective 15 April 2027 carries 13.6% of the exam weight. It covers 6 objectives and 35 study topics, listed below with short explanations written for exam preparation.
Open the Domain 5 mindmap Take the practice test Study the flashcards
5.1 Manage physical and logical access to assets (e.g., provision, control, review, revoke)
- Information
- Access to data governed by classification and need to know.
- Systems
- Operating system and platform access.
- Devices
- Endpoints, mobile and IoT devices.
- Facilities
- Badges, locks, mantraps, guards.
- Applications
- Application-level roles and entitlements.
- Services
- APIs and cloud services.
- Identities
- Human and non-human identities (service accounts, workloads, devices) provisioned, controlled, reviewed and revoked through their lifecycle.
5.2 Design identification and authentication strategy (e.g., people, devices, and services)
- Groups and roles
- Assign permissions to groups or roles, not individuals, for manageability.
- Authentication, Authorization, Accounting (AAA)
- Prove identity, grant permissions, record activity. MFA combines factor types: something you know, have, are.
- Session management
- Timeouts, re-authentication, secure session tokens, binding sessions to devices.
- Registration, proofing and identity establishment
- Verify identity before issuing credentials (NIST SP 800-63A identity assurance levels).
- Federated identity management (FIM)
- Trust between identity providers and relying parties across organizations.
- Credential management systems
- Password vaults and secrets managers.
- Single sign-on (SSO)
- One authentication grants access to many systems. Convenience versus single point of compromise.
- Just-in-time (JIT) access
- Privileges granted only when needed, for a limited time.
- Passwordless authentication
- FIDO, WebAuthn, passkeys and biometrics. Public key based and phishing resistant.
5.3 Federated identity with a third-party service
- On-premises
- Identity provider hosted internally, for example AD FS.
- Cloud
- Identity as a service (IDaaS) such as Entra ID or Okta.
- Hybrid
- Directory synchronization between on-premise and cloud identity.
5.4 Implement and manage authorization mechanisms
- Role-based access control (RBAC)
- Permissions follow job role. Good for stable organizations.
- Rule-based access control (RuBAC)
- Global rules apply to all subjects, for example firewall ACLs.
- Mandatory access control (MAC)
- System enforces labels and clearances. Users cannot change permissions.
- Discretionary access control (DAC)
- Owner decides who gets access, for example NTFS permissions.
- Attribute-based access control (ABAC)
- Policies evaluate subject, object, action and environment attributes.
- Risk-Adaptable Access Control (RAdAC)
- Decisions adapt in real time to risk signals such as location, device health and behavior.
- Access policy enforcement
- PDP evaluates policy; PEP enforces the decision at the resource.
5.5 Manage the identity and access provisioning lifecycle
- Account access review
- Periodic recertification of user, system and service accounts by managers and owners, catching privilege creep.
- Provisioning and deprovisioning
- Automate joiner, mover, leaver processes. Disable promptly on exit.
- Role definition and transition
- Maintain role models; remove old access when people move.
- Privilege escalation
- Controlled elevation (administrator groups, sudo) with auditing of its use and least privilege.
- Service accounts management
- Inventory, least privilege, no interactive logon, vaulted and rotated secrets.
5.6 Implement authentication and authorization systems
- OpenID Connect (OIDC) and OAuth Study topic
- OAuth 2.0 delegates authorization with access tokens. OIDC adds an identity layer with ID tokens (JWT).
- SAML Study topic
- XML-based assertions between identity provider and service provider, common for enterprise web SSO.
- Kerberos Study topic
- Ticket-based authentication with a KDC (AS and TGS). Sensitive to time synchronization.
- RADIUS and TACACS+ Study topic
- RADIUS: UDP, encrypts only the password, combines authentication and authorization. TACACS+: TCP, encrypts the full payload, separates AAA functions.
Key concepts for Domain 5
- Identification, authentication, authorization, accountability
- Claim identity, prove it, get permissions, and be held responsible through logging.
- Type 1 and Type 2 errors
- Type 1 is false rejection (FRR); Type 2 is false acceptance (FAR). CER/EER is where they meet; lower is better.
- OAuth is authorization
- OAuth is not authentication. OIDC adds authentication on top.
- MAC versus DAC
- MAC is system enforced by labels. DAC is owner discretion. RBAC is role-based and nondiscretionary.
Key terms and acronyms
- AAA
- Authentication, Authorization, Accounting.
- MFA
- Multi-Factor Authentication.
- FIDO2
- Standards (WebAuthn and CTAP) for phishing-resistant passwordless authentication.
- SSO
- Single Sign-On.
- FIM
- Federated Identity Management.
- JIT
- Just-in-Time access.
- SAML
- Security Assertion Markup Language.
- OIDC
- OpenID Connect.
- JWT
- JSON Web Token.
- KDC
- Key Distribution Center (Kerberos).
- TGT
- Ticket Granting Ticket.
- RADIUS
- Remote Authentication Dial-In User Service.
- TACACS+
- Terminal Access Controller Access-Control System Plus.
- PDP / PEP
- Policy Decision Point / Policy Enforcement Point.
- RAdAC
- Risk-Adaptable Access Control.
- RuBAC
- Rule-Based Access Control.
- WebAuthn
- W3C Web Authentication API, part of FIDO2.
- Passkey
- FIDO credential (key pair) that replaces a password, synced or device-bound.
- CER
- Crossover Error Rate, also EER.
- PAM
- Privileged Access Management.
Where candidates lose marks
- Access control models
- Federation protocols
- Provisioning lifecycle
- Biometric error rates
Sample practice questions
Q1. Which protocol separates authentication, authorization and accounting and encrypts the entire packet body?
- RADIUS
- TACACS+
- LDAP
- Kerberos
Show answer
B. TACACS+ TACACS+ uses TCP, separates AAA and encrypts the full payload. RADIUS encrypts only the password.
Q2. A user who moved departments still has access from the old role. What process best detects this?
- Account access review
- Password rotation
- Biometric enrollment
- Kerberos ticket renewal
Show answer
A. Account access review Periodic access reviews catch privilege creep.