Study guide

11.1 Final 45-Day CISSP Study Plan

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

11.1 Final 45-Day CISSP Study Plan

Key Takeaways Explain This Topic AI

The final 45 days should convert broad domain study into integrated risk-based decision practice.

Domain weights guide emphasis, but weak areas and cross-domain judgment should drive daily remediation.

The plan should include scenario review, practice analysis, rest, and official logistics checks.

A final plan is successful when it improves decision quality, not when it simply increases note volume.

Last updated: May 2026

Treat the Last 45 Days Like a Risk Program

The final CISSP review window is not a time to restart from page one or collect more disconnected facts. Treat it like a short security improvement program. Define the objective, identify the highest-risk gaps, select remediation activities, measure progress, and make conscious tradeoffs. The objective is not to memorize every possible detail. The objective is to make better security leadership decisions under time pressure across the eight official domains.

Use the April 15, 2024 CISSP outline as the control framework for the plan. Security and Risk Management carries the largest weight at 16 percent, while Asset Security and Software Development Security each carry 10 percent. The other domains sit between 12 and 13 percent. Those weights matter, but they are not a permission slip to ignore any domain. A weak lower-weight domain can still damage your performance, especially when a scenario combines data classification, identity, operations, and software lifecycle decisions.

The final plan should be mixed-domain by design. CISSP does not reward studying networks as if governance, identity, monitoring, and incident response are unrelated. A remote access scenario may require policy authority, data classification, MFA, VPN or zero trust access design, logging, third-party risk, and incident escalation. The final 45 days should train that integration. After answering a question, write the domain tag, the business risk, the control objective, and the reason each tempting option failed.

Window Primary objective Daily work Evidence to collect

Days 45-31 Baseline and map gaps Mixed practice, domain self-rating, official outline review Error log by domain and decision type

Days 30-16 Remediate weak areas Targeted reading, scenario rewrites, teach-back notes Fewer repeated misses and clearer rationales

Days 15-8 Simulate pressure Timed sets, forward-only answering, fatigue management Stable pacing and reduced second-guessing

Days 7-3 Consolidate High-yield summaries, policy and lifecycle review One-page domain decision sheets

Days 2-1 Protect readiness Light review, logistics check, sleep and nutrition Appointment, ID, route, and rules verified

Days 45 through 31 should produce a realistic baseline. Take mixed sets that touch all eight domains and classify each miss. Avoid a vague label such as forgot concept. Use categories such as missed role of risk owner, confused policy versus procedure, selected tool before requirement, ignored data lifecycle, overfocused on availability, missed least privilege, or failed to consider audit evidence. These categories reveal how you think, which is more useful than counting how many acronyms you know.

Days 30 through 16 should be the main remediation period. For each weak category, create a short scenario and solve it from a manager viewpoint. If you missed backup strategy questions, do not only memorize full, differential, and incremental backups. Build a recovery decision: business impact analysis defines requirements, backup design supports recovery objectives, restoration testing proves viability, access controls protect backup media, and change management keeps the plan current. This kind of review turns definitions into operational judgment.

Days 15 through 8 should include timed work. CISSP uses a computerized adaptive test with a 3-hour maximum, 100 to 150 items, and no review after an answer is finalized. That means the final plan must train forward-only decisions. During timed sets, do not mark questions for later. Read, decide, and move. The goal is to develop a repeatable method: identify the role, identify the asset, identify the risk, eliminate answers that violate the scenario, select the best supported option, and leave it behind.

Days 7 through 3 should focus on consolidation, not panic expansion. Build one-page decision sheets for each domain. Each sheet should include the domain weight, common management verbs, lifecycle steps, control ownership questions, and three scenario traps. For example, the Identity and Access Management sheet might include joiner-mover-leaver, authorization after authentication, privileged access approval, federation trust, service accounts, and periodic review. The goal is quick recall of decision structure.

The last two days should protect performance. Heavy cramming can create false confidence and fatigue. Review logistics, read your error log, revisit official CAT facts, and rehearse the first 10 minutes. Confirm the Pearson VUE appointment, location, identification requirements, travel time, and any accommodation arrangements already approved through ISC2. If you are testing at a center, plan arrival with margin. If a rule is important on test day, it should not be learned at the door.

Final Review Checklist

Map every study session to at least one official CISSP domain.

Keep an error log that records reasoning failures, not only missed topics.

Mix domains daily after the first baseline period.

Practice forward-only answering before the final week.

Review official logistics from ISC2 sources instead of relying on stale notes.

Stop adding new sources when they create confusion without improving decisions.

Preserve sleep, food, travel, and identification readiness as part of the plan.

A good final plan feels more like governance than inspiration. It has scope, priorities, evidence, and constraints. If you only feel busy, the plan is probably too broad. If you can explain why a missed question failed, which domain it maps to, what business risk it represents, and how you will avoid the same reasoning error next time, the plan is doing useful work.