CISSP knowledge map
Every objective of the CISSP exam outline (effective April 15, 2024), 1.1 to 8.5, pointing to the lesson that teaches it — or logged as a gap where no lesson exists yet. Objectives are numbered and paraphrased in the guidebook’s own words; the outline text itself is never reproduced.
Published 2026-10-09 · generated from the lesson data · 62 of 62 objectives have a lesson
Full CISSP certification needs five cumulative years of work experience in two or more of the eight domains — a degree or an approved credential can stand in for one year. Passing the exam without the experience makes someone an Associate of ISC2. The lessons teach the bodies of knowledge; they do not confer the certification.
ISC2’s “Exam Guidance for Artificial Intelligence” (September 1, 2026) maps AI-specific security tasks across all eight domains of the CISSP exam outline (still the April 15, 2024 edition) — examinable topics woven into each domain, not separate AI objectives and not third-party commentary. Each domain section below carries its AI note with links to the AI security track lessons.
Domain 1 — Security and Risk Management 16% of the exam
AI note AI assets shift your risk posture — fold ML models and LLMs into the risk frameworks you already use, govern AI ethics and algorithmic bias, and assess AI vendors the way you assess any third party. See: Governing AI, AI supply chain security.
Domain 2 — Asset Security 10% of the exam
AI note Training datasets, pre-trained models, and model weights are high-value assets to classify and handle; protect data integrity across the AI lifecycle and use differential privacy and masking where AI touches PII. See: AI supply chain security, How LLM applications are built and where they are attacked.
| Objective | Topic | Lesson |
|---|---|---|
| 2.1 | Identifying and classifying information and assets | Classifying information and assets: the scheme everything else hangs on |
| 2.2 | Information and asset handling requirements | Handling requirements: what each classification tier demands |
| 2.3 | Secure provisioning: ownership, inventory, asset management | Secure provisioning: ownership, inventory, and the CMDB |
| 2.4 | The data lifecycle: roles, collection, location, retention, remanence, destruction | The data lifecycle: from collection to destruction |
| 2.5 | Asset retention and end-of-life/support | Retention schedules and end-of-life: when to let go, and how |
| 2.6 | Data security controls and compliance | Data security controls: protecting data at rest, in transit, and in use |
Domain 3 — Security Architecture and Engineering 13% of the exam
AI note Host AI compute in secure enclaves, validate inputs against prompt injection and adversarial attacks, and engineer in explainability so an AI's decisions stay auditable. See: Prompt injection, the #1 LLM risk, How LLM applications are built and where they are attacked.
Domain 4 — Communication and Network Security 13% of the exam
AI note Isolate AI training environments with micro-segmentation and zero trust to stop lateral movement, and know how AI-driven NDR finds anomalies that signature-based tools miss. See: Threat modeling AI systems, AI security automation: concepts.
| Objective | Topic | Lesson |
|---|---|---|
| 4.1 | Secure network architecture design | Network architecture: drawing the lines attackers must cross |
| 4.2 | Securing network components | Network components: hardening everything the architecture trusts |
| 4.3 | Secure communication channels | Secure channels: which encrypted path for which traffic, and why |
Domain 5 — Identity and Access Management 13% of the exam
AI note Give AI agents and service accounts full identity-lifecycle treatment under least privilege, and use AI — behavioral biometrics, adaptive authentication — to defend your identity estate in turn. See: AI security automation: concepts, How LLM applications are built and where they are attacked.
| Objective | Topic | Lesson |
|---|---|---|
| 5.1 | Controlling physical and logical access to assets | Identity and access management: who gets in, and to what |
| 5.2 | Identification and authentication strategy | Identity and access management: who gets in, and to what |
| 5.3 | Federated identity with third-party services | Identity and access management: who gets in, and to what |
| 5.4 | Authorization mechanisms and models | Identity and access management: who gets in, and to what |
| 5.5 | Identity and access provisioning lifecycle | Identity and access management: who gets in, and to what |
| 5.6 | Implementing authentication systems | Implementing authentication systems: the rollout, not the theory |
Domain 6 — Security Assessment and Testing 12% of the exam
AI note Red-team AI systems against evasion and extraction attacks, audit model outputs for exploitable logic flaws, and automate vulnerability management with AI-powered scanning. See: Threat modeling AI systems, AI security automation: concepts.
| Objective | Topic | Lesson |
|---|---|---|
| 6.1 | Designing assessment, test, and audit strategies | Assessment strategy: deciding what gets tested, by whom, and how often |
| 6.2 | Security control testing methods | Control testing: choosing the method that proves the claim |
| 6.3 | Collecting security process data | Security metrics: measuring the program without lying to yourself |
| 6.4 | Analyzing test output and reporting | Test analysis and reporting: from ten thousand findings to decisions |
| 6.5 | Conducting and facilitating security audits | Security audits: independence, evidence, and the finding that holds up |
Domain 7 — Security Operations 13% of the exam
AI note Put AI/ML into SOAR to cut alert fatigue, and monitor production models for drift and live adversarial attacks as part of normal operations. See: AI security automation: concepts.
Domain 8 — Software Development Security 10% of the exam
AI note AI-assisted coding ships hallucinated vulnerabilities and insecure generated snippets — catch them with AI security testing in CI/CD, and secure the ML supply chain against model hijacking and inference attacks. See: AI attacks and defenses in the build pipeline, The OWASP LLM Top 10 beyond prompt injection.
| Objective | Topic | Lesson |
|---|---|---|
| 8.1 | Security in the SDLC | Secure SDLC: catching the vulnerability before it ships, Application security: concepts |
| 8.2 | Security controls in development ecosystems | Secure SDLC: catching the vulnerability before it ships, Application security: concepts |
| 8.3 | Assessing software security effectiveness | Secure SDLC: catching the vulnerability before it ships, Application security: concepts |
| 8.4 | Security impact of acquired software | Secure SDLC: catching the vulnerability before it ships, Application security: concepts |
| 8.5 | Secure coding guidelines and standards | Secure SDLC: catching the vulnerability before it ships, Application security: concepts |