Study guide
1.2 Exam Outline Effective Date and Eight-Domain Map
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
1.2 Exam Outline Effective Date and Eight-Domain Map
Key Takeaways Explain This Topic AI
The current CISSP exam outline is effective April 15, 2024 and should drive the content map for study.
The eight domains cover governance, data, engineering, networks, identity, assessment, operations, and software development security.
Domain weights guide emphasis, but the domains are integrated in real security decisions and should not be studied as silos.
Security and Risk Management is the heaviest domain at 16 percent and provides decision language used across the other seven domains.
Last updated: May 2026
The Outline Is the Map
The CISSP exam outline effective April 15, 2024 is the source of record for the current content map in this guide. That date is not trivia; it is a source-control marker. When old notes mention different item counts, stale domain wording, or an older content split, the current outline wins. A disciplined CISSP learner tags notes, flashcards, and practice explanations to the current domains so that study time follows the body of knowledge ISC2 has published.
The outline says CISSP validates deep technical and managerial knowledge and experience to design, engineer, and manage the overall security posture of an organization. The phrase overall security posture is important because the domains are interdependent. Security architecture depends on risk appetite. Identity depends on personnel security and data classification. Operations depends on logging, incident response, business continuity, and change management. Software development security depends on governance, testing, supply chain controls, and secure design principles.
Domain Weight Management question
Security and Risk Management 16% What risk, policy, legal, ethical, and governance duties frame the decision?
Asset Security 10% What information or asset is owned, classified, handled, retained, or destroyed?
Security Architecture and Engineering 13% What design principles and controls satisfy security requirements?
Communication and Network Security 13% How should connectivity be segmented, protected, monitored, and operated?
Identity and Access Management 13% Who gets access, under what proof, by what authority, and for how long?
Security Assessment and Testing 12% How do we prove controls work and report deficiencies?
Security Operations 13% How do we run, monitor, respond, recover, and improve?
Software Development Security 10% How is software governed, built, tested, deployed, and maintained securely?
The weights should influence study time, but they should not make you ignore lower-weight domains. Asset Security and Software Development Security are each 10 percent, yet both often drive major enterprise risk. Mishandled data can create privacy, legal, and operational harm. Weak software governance can introduce vulnerabilities into every business process that depends on applications. A CISSP-level study plan treats weights as a planning tool, not a value judgment about what matters in practice.
Security and Risk Management deserves special attention because it supplies the language of many correct decisions. Ethics, governance, legal and regulatory requirements, investigations, policy documents, business continuity, personnel security, risk management, threat modeling, supply chain risk, and awareness programs all live in that domain. These topics do not stay isolated. They affect how you select encryption, approve remote access, test controls, onboard vendors, respond to incidents, and set secure development requirements.
A practical way to study the domain map is to follow the lifecycle of a sensitive system. First, leadership defines business goals, risk appetite, policies, and legal obligations. Next, the organization identifies assets and data handling requirements. Architects design secure systems and networks. Identity teams define authentication, authorization, and provisioning. Assessment teams test controls. Operations teams monitor, respond, and recover. Development teams maintain secure code and pipelines. The same system passes through all eight domains.
The exam outline also helps you reject misleading study shortcuts. A list that focuses almost entirely on cryptography formulas, network ports, or access-control acronyms is incomplete because it misses governance, risk treatment, assurance, operations, and software lifecycle issues. A list that only discusses policy is also incomplete because CISSP expects you to understand technical and managerial knowledge together. The right balance is not policy versus technology; it is technology selected and managed through policy, risk, and evidence.
Use domain weights to schedule review blocks. Start with the official percentage, then adjust for your weakness. A network engineer may need more time on legal, governance, software security, and assessment. A GRC analyst may need more time on architecture, cryptography, networks, and operations. The CISSP exam is broad because security leaders must communicate across specialties. Your study plan should intentionally cross-train the domains you do not use every day.
Integrated Scenario Workflow
Identify the business objective and risk owner.
Classify the data and assets involved.
Define security requirements and design principles.
Select network, identity, and platform controls.
Document policy, standards, procedures, and guidelines.
Test controls and report results to accountable stakeholders.
Operate, monitor, respond, recover, and improve.
Feed lessons learned into software, supplier, and architecture decisions.
When reading a scenario, ask which domain is primary and which domains constrain the answer. A question about vendor connectivity may primarily involve Communication and Network Security, but it may also involve supply chain risk, contractual requirements, identity federation, logging, data classification, and incident response. A strong answer respects the whole map. It chooses a control that fits the stated requirement and also fits governance, assurance, and operations.