Study guide

6.7 IAM Case Lab

CISSP Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: CISSP Orientation, CAT, and Official Source Control

1.1 Credential Scope, CISSP Mindset, and Search Language 1.2 Exam Outline Effective Date and Eight-Domain Map 1.3 CAT Format, 100-150 Items, and Forward-Only Rules 1.4 Passing Grade, Results, Feedback, and Retake Policy 1.5 Experience, Endorsement, and Associate of ISC2 Path 1.6 Pricing, AMF, CPE, and Maintenance Overview

2 Chapter 2: Security and Risk Management

2.1 Professional Ethics, CIA, and Security Governance 2.2 Policies, Standards, Procedures, Guidelines, and Control Ownership 2.3 Legal, Regulatory, Privacy, and Investigation Context 2.4 Risk Identification, Analysis, Treatment, and Reporting 2.5 Business Continuity, BIA, and Recovery Prioritization 2.6 Personnel Security, Training, Awareness, and Culture 2.7 Threat Modeling, Supply Chain Risk, and Third-Party Governance 2.8 Security and Risk Management Case Lab

3 Chapter 3: Asset Security and Data Lifecycle

3.1 Asset and Data Classification, Ownership, and Roles 3.2 Handling Requirements, Labeling, Privacy, and Cross-Border Data 3.3 Data States and Protection Methods: DLP, DRM, and CASB 3.4 Data Lifecycle, Retention, Remanence, and Destruction 3.5 Secure Provisioning, Inventory, and Asset Management 3.6 Asset Security Case Lab

4 Chapter 4: Security Architecture, Engineering, and Cryptography

4.1 Secure Design Principles and Security Models 4.2 Control Selection, System Security, and Architecture Risk 4.3 Cryptography Foundations: Symmetric, Asymmetric, Hashing, and PKI 4.4 Cryptographic Lifecycle, Key Management, and Attack Patterns 4.5 Cloud, Container, IoT, Edge, and Shared Responsibility Architecture 4.6 Physical Site, Facility, and Environmental Security 4.7 Information System Lifecycle Engineering and Retirement 4.8 Architecture and Engineering Case Lab

5 Chapter 5: Communication, Network Security, and Zero Trust

5.1 Network Architecture, OSI/TCP/IP, and Secure Design 5.2 Secure Protocols, Encryption in Transit, and Channel Protection 5.3 Segmentation, Microsegmentation, SDN, VPC, and Zero Trust 5.4 Wireless, Cellular, Remote Access, and Third-Party Connectivity 5.5 Network Components: NAC, IDS/IPS, Firewalls, and Endpoints 5.6 Monitoring, Observability, Capacity, and Resilient Communications 5.7 Communication and Network Security Case Lab

6 Chapter 6: Identity and Access Management

6.1 Identity Proofing, Authentication, Authorization, and Accountability 6.2 Access Control Models: RBAC, MAC, DAC, ABAC, and Risk-Based Access 6.3 Federation, SSO, MFA, Passwordless, and Session Management 6.4 Provisioning, Deprovisioning, JML, and Access Reviews 6.5 Service Accounts, Non-Human Identities, and Privilege Management 6.6 Physical, Logical, Cloud, and Hybrid Access Boundaries 6.7 IAM Case Lab

7 Chapter 7: Security Assessment, Testing, and Audit Strategy

7.1 Assessment, Test, and Audit Strategy Selection 7.2 Control Testing, Vulnerability Assessment, and Penetration Testing 7.3 Log Review, Code Review, Misuse Cases, and Compliance Checks 7.4 Security Process Data, KPIs, KRIs, and Reporting 7.5 Remediation, Exceptions, Risk Acceptance, and Evidence Quality 7.6 Security Assessment and Testing Case Lab

8 Chapter 8: Security Operations, Incident Response, and Resilience

8.1 Investigations, Evidence, Forensics, and Legal Readiness 8.2 Logging, Monitoring, SOC, and Alert Triage 8.3 Configuration, Change, Patch, and Vulnerability Operations 8.4 Incident Management, Containment, Eradication, and Recovery 8.5 Disaster Recovery, Backup, Availability, and Resilience 8.6 Physical Security Operations and Safety 8.7 Security Operations Case Lab

9 Chapter 9: Software Development Security and DevSecOps

9.1 Secure SDLC Governance and Requirements 9.2 Architecture, Threat Modeling, and Design Review 9.3 Secure Coding, Code Review, and Application Testing 9.4 CI/CD, Source Control, and Environment Separation 9.5 Software Supply Chain, Third-Party Components, and Deployment 9.6 DevSecOps Vulnerability Management and Release Risk 9.7 Software Development Security Case Lab

10 Chapter 10: Integrated CISSP Governance Scenario Labs

10.1 Enterprise Risk Committee Decision Lab 10.2 Cloud Migration Security Architecture Lab 10.3 Ransomware Incident and Business Continuity Lab 10.4 Identity Modernization and Zero Trust Lab 10.5 Third-Party Breach and Contract Governance Lab 10.6 Secure SDLC Transformation Lab 10.7 Full CISSP Manager Simulation

11 Chapter 11: Final Review, Endorsement, CPE, and Test-Day Strategy

11.1 Final 45-Day CISSP Study Plan 11.2 CAT Timing and Forward-Only Decision Workflow 11.3 Mixed-Domain Remediation and Manager Mindset Review 11.4 Test-Day Checklist and Pearson VUE Readiness 11.5 Endorsement, Associate Path, and Work Experience Documentation 11.6 CPE, AMF, and Three-Year Maintenance Plan 11.7 CISSP Final Mixed Review

6.7 IAM Case Lab

Key Takeaways Explain This Topic AI

A practical IAM review connects identity proofing, role design, federation, privileged access, session control, and lifecycle governance.

The strongest recommendations usually reduce standing privilege, clarify ownership, and improve deprovisioning evidence.

IAM risk decisions should be documented in business language so executives can see impact, likelihood, control cost, and residual risk.

Case analysis should identify root causes rather than treating every access problem as a password or help desk issue.

Last updated: May 2026

Scenario: Meridian Health Analytics IAM Review

Meridian Health Analytics is a mid-sized company that processes clinical quality data for hospitals. It has 1,800 employees, 400 contractors, several SaaS platforms, a hybrid directory, and cloud analytics workloads. The company grew through two acquisitions, and access processes vary by business unit. Leadership asks for an IAM review after a contractor account was used to download sensitive reports two months after the contract ended.

The incident investigation finds several contributing causes. HR tracked employees but not all contractors. Application owners approved access by email, and those messages were not tied to expiration dates. Some SaaS applications used SSO, but others had local accounts. Cloud administrators shared a legacy emergency account during outages. Data warehouse roles were broad because analysts moved between projects quickly. Badge access was removed manually and sometimes lagged account disablement.

A narrow technical response would reset passwords and close the contractor account. That is not enough. The CISSP response is to identify control failures across the IAM lifecycle. Identity proofing was inconsistent for contractors. Authorization was too broad in the data warehouse. Accountability was weak for shared cloud administration. Deprovisioning was incomplete. Federation coverage was uneven. Access reviews were not evidence driven.

Initial Risk Register

Risk Business impact Likelihood driver Priority control

Contractor access remains after contract end Unauthorized data access and reporting obligations No authoritative contractor source Sponsor-owned identities with end dates

Broad analyst roles expose unrelated hospital data Privacy and contractual breach Convenience-driven role design Project-based roles and data owner review

Shared cloud emergency account hides actions Weak investigation and admin misuse risk Outage workaround became routine PAM, unique admin identities, break-glass review

Local SaaS accounts bypass termination Stale external access Incomplete federation and app inventory SSO onboarding and deprovisioning test

Badge removal lags account disablement Facility and equipment exposure Manual physical access process Integrated leaver checklist and evidence

The first recommendation is to establish an authoritative identity lifecycle. Employees come from HR. Contractors come from a vendor or sponsor system with named business sponsors, start dates, end dates, and required recertification. Workloads come from approved deployment pipelines or cloud inventory. Every identity must have an owner and a termination condition. This creates the foundation for provisioning, deprovisioning, and review.

The second recommendation is to redesign access around least privilege. Analysts should not receive broad access to all hospital data because projects change. A better design uses baseline analyst access plus project-specific access approved by data owners, with expiration aligned to the project. Sensitive exports require logging and possibly step-up authentication. Unused project access is removed during reviews.

The third recommendation is to expand federation and central session control. SaaS applications should be inventoried, assigned owners, and categorized by data sensitivity. High-risk SaaS applications should use SSO, MFA, role mapping, and automated deprovisioning where supported. Local accounts should be exceptions with compensating review and a remediation date. The team should test whether disabling a central identity actually blocks active sessions and downstream access.

The fourth recommendation is to implement privileged access management for administrators. Cloud admins should use unique privileged identities separate from daily accounts. Standing global administrator rights should be reduced. Elevation should be time limited, approved or policy driven, and logged. Break-glass access should remain available for outages but be protected, alerted, and reviewed after use. Shared emergency accounts should not be normal operating procedure.

The fifth recommendation is to connect physical and logical lifecycle steps. A leaver workflow should disable directory access, revoke sessions, remove SaaS access, collect devices, recover badges, terminate VPN, rotate exposed shared secrets, and preserve evidence. High-risk departures require coordination before notification. Routine contractor endings should be driven by end dates so access does not depend on someone remembering to file a ticket.

90-Day Remediation Plan

Build an application, identity, and entitlement inventory for the systems that store or process sensitive data.

Create a contractor identity source with sponsor ownership, end dates, and automated disablement triggers.

Move priority SaaS applications to SSO with MFA, owner-approved role mapping, and tested deprovisioning.

Replace shared cloud administration with unique privileged accounts, PAM workflows, and monitored break-glass access.

Redesign data warehouse roles around projects, data owner approval, expiration, and separation of duties.

Run a targeted access review for contractors, privileged users, broad analyst roles, and local SaaS accounts.

Report metrics to leadership: stale accounts removed, privileged accounts reduced, applications federated, and review remediation completed.

A good executive message avoids technical overload but keeps risk concrete. Meridian is not simply missing a tool. It lacks consistent lifecycle governance across human, contractor, cloud, SaaS, and physical access. The organization should invest first where the incident showed direct risk: contractor deprovisioning, sensitive data authorization, federation coverage, privileged access, and review evidence.

The case also shows why least privilege must be practical. If analysts genuinely move between projects quickly, the access process must be fast enough to support work. That may mean preapproved project roles, data owner workflows, and automated expiration. If the process is too slow, users will pressure managers into broad permanent access. Security governance should make the right path efficient and auditable.

Finally, Meridian should define residual risk and exceptions. Some legacy SaaS platforms may not support automated deprovisioning. Some emergency access may be required during identity provider outages. Some badge systems may need manual integration. Each exception should have an owner, expiration, compensating control, and remediation plan. A risk-aware IAM program does not pretend every issue is fixed immediately; it makes accepted risk explicit and managed.