Study guide
11.5 Endorsement, Associate Path, and Work Experience Documentation
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.5 Endorsement, Associate Path, and Work Experience Documentation
Key Takeaways Explain This Topic AI
CISSP certification requires passing the exam and meeting the work-experience and endorsement requirements.
Candidates need at least five years of cumulative full-time experience in two or more current CISSP domains.
One year of experience may be satisfied by an approved degree or credential, but only one year can be waived.
Candidates without the required experience may become an Associate of ISC2 and have six years to earn the required experience.
Last updated: May 2026
Certification Is More Than the Exam Event
CISSP is intended for experienced security practitioners, managers, and executives who can lead an organization's information security program. Passing the exam is a major milestone, but certification also depends on experience and endorsement. The source brief states that candidates must have at least five years of cumulative full-time experience in two or more of the eight current CISSP domains. That experience requirement should be planned and documented with the same care as study.
The experience requirement is domain-based. Work does not need to carry a CISSP title, but it should align to the current domains: Security and Risk Management, Asset Security, Security Architecture and Engineering, Communication and Network Security, Identity and Access Management, Security Assessment and Testing, Security Operations, and Software Development Security. Many roles span multiple domains. A security analyst may handle monitoring, incident response, vulnerability management, identity reviews, and audit evidence.
A software security lead may handle secure SDLC, threat modeling, code review, and release governance.
A bachelor's or master's degree in computer science, IT, or a related field, or an additional ISC2-approved credential, may satisfy up to one year of the experience requirement. Only one year can be waived. This distinction matters. A candidate cannot stack several degrees and credentials to remove multiple years. The waiver can help, but the CISSP remains an experience-based certification.
Candidates who do not yet have the required experience may become an Associate of ISC2 by passing the CISSP exam and then have six years to earn the five required years. This path is important for candidates who are growing into security leadership but have not yet accumulated the full experience record. It should be represented accurately: passing the exam alone does not automatically make someone a CISSP-certified professional if the experience and endorsement requirements are not complete.
Documentation item Good evidence Weak evidence
Role history Employer, title, dates, full-time status, supervisor or reference Vague memory of working in security
Domain mapping Specific duties mapped to at least two CISSP domains Listing all domains without support
Responsibility Policies owned, systems managed, assessments led, incidents handled Tool names without duties or scope
Waiver support Degree or approved credential record if used Assuming multiple waivers can stack
Associate path Plan to earn remaining experience within six years Calling the credential complete before requirements are met
Start documentation by building a role timeline. For each position, record dates, employment type, responsibilities, systems or processes supported, and the CISSP domains involved. Focus on what you actually did. If you wrote access review procedures, that may support Security and Risk Management and Identity and Access Management. If you performed restoration testing and incident response, that may support Security Operations. If you governed code review and deployment controls, that may support Software Development Security and Security Assessment and Testing.
Avoid inflated domain mapping. More domains are not automatically better if the evidence is thin. A defensible endorsement package is specific, honest, and tied to actual responsibilities. For example, saying managed IAM lifecycle for 4,000 employees, including provisioning standards, quarterly access reviews, and privileged access exceptions is stronger than saying did IAM. Saying led annual tabletop exercises for ransomware recovery with business owners is stronger than saying handled business continuity.
Think like an auditor when assembling evidence. The question is not whether you feel experienced. The question is whether a reasonable reviewer can understand the dates, scope, duties, and domain relationship. Keep documentation professional and concise. Do not include confidential customer data, sensitive architecture details, secrets, or internal incident specifics. Describe responsibilities at an appropriate level of abstraction while preserving enough detail to support the claim.
Experience Mapping Workflow
Build a chronological work history with dates and full-time status.
For each role, list major security responsibilities.
Map each responsibility to one or more current CISSP domains.
Identify at least two domains supported by cumulative full-time experience.
Determine whether a one-year waiver applies and collect supporting records.
Identify an endorser or prepare for the applicable ISC2 endorsement process.
If experience is incomplete, document the Associate of ISC2 path and remaining gap.
Endorsement planning is also an ethics exercise. CISSP is tied to professional trust. Do not exaggerate dates, titles, authority, or domain coverage. If your role contributed to a control but did not own it, say that accurately. If you supported incident response but did not lead it, describe the support role. Honest precision is stronger than broad claims because it shows judgment and respect for the credential.
The final review period is a good time to assemble this material because it reinforces the domains. Mapping your real work to the outline helps you see CISSP as a professional practice rather than a study abstraction. It also reduces post-exam friction. When the exam event is over, you should already understand whether you are pursuing certification endorsement immediately or using the Associate path while earning the remaining experience.