Study guide
1.5 Experience, Endorsement, and Associate of ISC2 Path
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.5 Experience, Endorsement, and Associate of ISC2 Path
Key Takeaways Explain This Topic AI
CISSP candidates need at least five years of cumulative full-time experience in two or more current CISSP domains.
A qualifying degree or an ISC2-approved credential can satisfy up to one year, but only one year can be waived.
Candidates who pass the exam without required experience may become Associates of ISC2 and have six years to earn the five required years.
Associate of ISC2 status is not the same as being CISSP certified and must be represented accurately.
Last updated: May 2026
Certification Is More Than Passing the Exam
CISSP is an experienced-practitioner credential. ISC2 states that candidates must have a minimum of five years cumulative full-time experience in two or more of the eight domains in the current CISSP exam outline. This requirement is not a decorative hurdle. It reflects the purpose of the credential: validating the ability to apply technical and managerial knowledge across real organizational security responsibilities. A candidate should therefore study the exam and manage experience evidence as parts of one professional process.
ISC2 allows a bachelor's or master's degree in computer science, information technology, or related fields, or an additional ISC2-approved credential, to satisfy up to one year of the required experience. Only one year can be waived. That means a candidate still needs substantial domain experience. A waiver is not a substitute for professional judgment, and it should not be described as eliminating the experience requirement. The safe wording is that one qualifying item may satisfy up to one year.
Path element Official requirement or status Governance-minded action
Experience baseline Five years cumulative full-time experience Map roles and dates to at least two current domains
Domain spread Two or more of the eight CISSP domains Document duties, not just job titles
Education or credential waiver Up to one year, only one year waived Keep evidence and avoid overstating the waiver
- Passing without experience Associate of ISC2 path Track the six-year window to earn required experience
- Certification representation Associate is not CISSP certified Use titles accurately and ethically
The Associate of ISC2 path is important for candidates who can pass the CISSP exam before meeting the experience requirement. Those candidates may become Associates of ISC2 and then have six years to earn the five required years of experience. This path is not a loophole that converts exam success into immediate CISSP certification. It is a structured route for building and documenting the remaining professional experience while being clear about current status.
Accurate representation is a security ethics issue. Associates of ISC2 are not certified as CISSP and should not present themselves as CISSP holders. That distinction protects employers, clients, and the certification program. In risk terms, title misuse creates trust risk and governance risk. A candidate who cannot accurately represent credential status is failing the same integrity standard that security leaders are expected to enforce in access, evidence handling, reporting, and policy compliance.
Experience documentation should be specific enough to withstand review. A job title such as security analyst is less useful than a description of responsibilities tied to domains: access reviews, incident handling, vulnerability assessment, policy implementation, data classification, network segmentation, secure development support, business continuity exercises, supplier assessment, or audit evidence collection. The goal is to show cumulative professional work in domain areas, not to inflate unrelated duties.
A manager-judgment study plan asks how experience changes answer quality. Someone who has performed access recertification knows that approving access is not just a technical grant; it involves owner review, separation of duties, evidence, exceptions, and revocation. Someone who has supported incident response knows that containment decisions affect business continuity, legal preservation, communication, and recovery. CISSP uses broad scenarios because real experience teaches that security decisions have consequences beyond the tool console.
If you are early in your career, use the domain map as a professional development plan. Seek work that exposes you to more than one domain, such as identity operations plus assessment, software security plus risk management, or network security plus incident response. Keep a clean record of projects, dates, responsibilities, supervisors, and outcomes. Do not fabricate or exaggerate experience. The right approach is slower but stronger: earn the experience, preserve evidence, and represent status honestly.
Experience Evidence Checklist
Record employer, role, start date, end date, and full-time or part-time nature.
Map responsibilities to at least two current CISSP domains.
Keep examples of governance, operations, assessment, architecture, identity, data, network, or software security work.
Note supervisors or endorsers who can verify duties.
Preserve evidence of qualifying degree or approved credential if using a one-year waiver.
Track the six-year Associate of ISC2 window if passing before meeting experience requirements.
Use Associate of ISC2 wording accurately until certification requirements are complete.
Endorsement readiness should be built before exam day. That does not mean rushing the process; it means knowing what evidence you have and where gaps exist. A candidate who discovers after passing that experience records are vague has created avoidable administrative risk. Treat the credential path like a control lifecycle: requirements, evidence, validation, approval, maintenance, and monitoring. This reinforces the CISSP mindset while preventing status confusion.