Study guide
10.4 Identity Modernization and Zero Trust 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
10.4 Identity Modernization and Zero Trust Lab
Key Takeaways Explain This Topic AI
Zero trust is a governance and architecture strategy based on explicit verification, least privilege, and assumed breach.
Identity modernization must cover users, devices, workloads, service accounts, privileged access, and lifecycle governance.
Conditional access and risk-based controls require trustworthy identity attributes, device signals, logging, and exception handling.
The CISSP manager should sequence modernization to reduce material risk without breaking essential business workflows.
Last updated: May 2026
Modernization Scenario: Remote Work Outgrew the Old Perimeter
A professional services firm grew through acquisitions and now has five directories, several VPNs, inconsistent MFA, unmanaged contractor accounts, and local administrator rights on many laptops. Sensitive client documents are stored in cloud collaboration platforms. Executives want a zero trust program, but business units fear disruption because consultants work from client sites, airports, and home networks. The security team proposes turning off all VPNs within three months.
The CISSP response should convert the slogan into architecture principles and a staged roadmap. Zero trust does not mean trusting nothing in a literal sense. It means no implicit trust based only on network location. Access should be explicitly verified, least privilege should be enforced, and systems should be designed as if breach is possible. Identity, device posture, application context, data sensitivity, and behavior should influence access decisions.
Identity consolidation is often the first foundation. The firm needs authoritative identity sources for employees, contractors, partners, service accounts, and workloads. Each identity should have an owner, status, start date, end date where appropriate, and attributes such as department, role, manager, location, and employment type. Without reliable attributes, conditional access policies may block the wrong people or allow risky access.
MFA must be risk based and operationally realistic. Privileged users, remote access, sensitive client repositories, financial systems, and identity administration should receive stronger controls first. Phishing-resistant authenticators may be required for administrators and executives. Contractors may need sponsor approval, expiration, and limited application access. Exceptions should be documented, time-limited, and reviewed.
Device trust is another pillar. A managed laptop with encryption, current patches, endpoint protection, screen lock, and healthy posture is different from an unmanaged device in an internet cafe. Conditional access can require device compliance for sensitive data while allowing lower-risk web access from unmanaged devices with restrictions. The policy should consider user populations, accessibility, field work, and emergency access.
Privileged access requires special treatment. Local administrator rights on laptops, standing domain administrator access, and shared emergency accounts create high impact. A modernization program should implement privileged access management, just-in-time elevation, separate admin accounts, session logging, password or key rotation, and break-glass procedures. Break-glass accounts should be few, monitored, protected, and tested.
Zero trust pillar Scenario decision Control example Risk if ignored
Identity Which identities are authoritative? Directory consolidation, identity proofing, lifecycle feed Orphaned users and wrong policy decisions
Device Which devices can access sensitive data? Compliance checks, encryption, endpoint health Data access from compromised endpoints
Application Which apps support modern access? Federation, proxy, token controls Legacy bypass and inconsistent enforcement
Data Which content is sensitive? Classification, DLP, access labels Overexposure of client documents
Network How is lateral movement limited? Segmentation and private access paths Compromise spreads after one account is abused
Monitoring How are decisions reviewed? Identity logs, device logs, UEBA, alert runbooks Policy failures remain invisible
Turning off all VPNs quickly may sound modern, but it could break critical legacy workflows and push users to unsafe workarounds. A better approach is application-by-application migration. Modern SaaS and web applications can move to federated access with conditional policies. Legacy applications may need private access gateways, segmentation, or phased replacement. The roadmap should reduce highest risk first while preserving business continuity.
Policy design should avoid both weak defaults and brittle restrictions. A policy might allow a consultant to view low-risk collaboration content from any device after MFA, but require a managed compliant device for confidential client files. It might require step-up authentication to download large volumes of data or change sharing settings. It might block administrative portals from unmanaged devices entirely.
Monitoring is essential because zero trust policies create many signals. Identity provider logs, endpoint posture changes, impossible travel alerts, risky sign-ins, denied access events, new device registrations, privilege elevation, and data downloads should feed detection and response. Metrics should show not only blocked attempts but also exception volume, user impact, and policy coverage. A control that quietly excludes half the applications is not a complete program.
The program also needs communication and training. Users should understand enrollment steps, what changes for remote access, how to request exceptions, and how to report access problems. Help desk teams need scripts for MFA reset, device compliance troubleshooting, and suspected account compromise. Poor support can cause executives to weaken controls just as the program begins to reduce risk.
Zero Trust Modernization Roadmap
Inventory identities, applications, devices, data repositories, and access paths.
Identify high-risk populations: administrators, executives, contractors, and sensitive data users.
Establish authoritative identity lifecycle feeds and remove orphan accounts.
Deploy strong MFA and conditional access for privileged and sensitive access first.
Integrate device posture and endpoint health for high-value applications.
Segment legacy systems and migrate applications to modern access patterns in waves.
Monitor policy decisions, exceptions, user impact, and incident signals.
Review progress against risk reduction, not only deployment counts.
A CISSP manager should frame zero trust as a long-term governance program with architecture checkpoints. The value is not the label. The value is reducing implicit trust, constraining privilege, improving visibility, and making access decisions match current risk. The organization should be able to explain why access was allowed, under what conditions, and how misuse would be detected.