Learn Computer Stuff
Home / Security guidebook / CISSP knowledge map
Security guidebook · Knowledge map

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.

The issuer’s rule, stated once

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.

AI in the outline — exam content, not commentary

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.

ObjectiveTopicLesson
1.1Professional ethics in security workProfessional ethics in security work: the Code is the floor, not the ceiling
1.2Core security concepts: confidentiality, integrity, availability, and related propertiesCore security concepts: the CIA triad and the properties around it
1.3Security governance: aligning security with business strategySecurity governance: aligning security with business strategy
1.4Legal, regulatory, and compliance landscapeLegal, regulatory, and compliance: mapping obligations to evidence
1.5Investigation types and their requirementsInvestigation types: which investigation you're in, and what it demands
1.6Security policy, standards, procedures, and guidelinesSecurity policy, standards, procedures, and guidelines: the document hierarchy
1.7Business continuity requirements: business impact analysis and dependenciesBusiness continuity and disaster recovery: deciding what survives the outage
1.8Personnel security across hiring, employment, and departurePersonnel security: the human side of the employment lifecycle
1.9Risk management concepts, end to endRisk assessment as a worked case
1.10Threat modeling concepts and methodologiesThreat modeling concepts and methodologies: choosing how to think about what can go wrong
1.11Supply chain risk managementSupply chain risk management: trusting what you didn't build
1.12Security awareness, education, and training programsSecurity awareness, education, and training: building the learning program

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.

ObjectiveTopicLesson
2.1Identifying and classifying information and assetsClassifying information and assets: the scheme everything else hangs on
2.2Information and asset handling requirementsHandling requirements: what each classification tier demands
2.3Secure provisioning: ownership, inventory, asset managementSecure provisioning: ownership, inventory, and the CMDB
2.4The data lifecycle: roles, collection, location, retention, remanence, destructionThe data lifecycle: from collection to destruction
2.5Asset retention and end-of-life/supportRetention schedules and end-of-life: when to let go, and how
2.6Data security controls and complianceData 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.

ObjectiveTopicLesson
3.1Secure design principles for engineeringSecure design principles: engineering judgment before controls
3.2Formal security modelsFormal security models: what "secure" means, precisely
3.3Selecting controls from system security requirementsSelecting controls: from requirements to a defensible set
3.4Platform security capabilitiesPlatform security: the ground your architecture stands on
3.5Assessing vulnerabilities across architecture and system typesAssessing vulnerabilities across the architecture
3.6Cryptographic solutions: lifecycle, methods, PKI, key managementApplied cryptography: what the primitives do, and how they break, Cryptography: what the primitives do, and what breaks when you misuse them
3.7Cryptanalytic attack methodsCryptanalytic attacks: how ciphers fail, and what that teaches
3.8Site and facility design principlesSite and facility design: security before the first brick
3.9Site and facility security controlsSite and facility controls: the checklist that holds
3.10The information system lifecycleThe information system lifecycle: security at every gate

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.

ObjectiveTopicLesson
4.1Secure network architecture designNetwork architecture: drawing the lines attackers must cross
4.2Securing network componentsNetwork components: hardening everything the architecture trusts
4.3Secure communication channelsSecure 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.

ObjectiveTopicLesson
5.1Controlling physical and logical access to assetsIdentity and access management: who gets in, and to what
5.2Identification and authentication strategyIdentity and access management: who gets in, and to what
5.3Federated identity with third-party servicesIdentity and access management: who gets in, and to what
5.4Authorization mechanisms and modelsIdentity and access management: who gets in, and to what
5.5Identity and access provisioning lifecycleIdentity and access management: who gets in, and to what
5.6Implementing authentication systemsImplementing 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.

ObjectiveTopicLesson
6.1Designing assessment, test, and audit strategiesAssessment strategy: deciding what gets tested, by whom, and how often
6.2Security control testing methodsControl testing: choosing the method that proves the claim
6.3Collecting security process dataSecurity metrics: measuring the program without lying to yourself
6.4Analyzing test output and reportingTest analysis and reporting: from ten thousand findings to decisions
6.5Conducting and facilitating security auditsSecurity 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.

ObjectiveTopicLesson
7.1Investigations: evidence, techniques, forensicsInvestigations and digital forensics: the management and legal view
7.2Logging and monitoring operationsLogging and monitoring operations: deciding what gets watched, and by whom
7.3Configuration managementConfiguration management: baselines, hardening, and catching drift
7.4Foundational security operations conceptsFoundational security operations concepts: the principles you run on
7.5Resource and media protectionMedia protection: handling the physical object
7.6Incident managementIncident management: the team, the escalation, and the communications
7.7Operating detective and preventive measuresDetective and preventive measures in operation: choosing, placing, and tuning controls
7.8Patch and vulnerability management operationsPatch and vulnerability management operations: from CVE to deployed fix
7.9Change managementChange management: approving the change before it ships
7.10Recovery strategies and resilienceBusiness continuity and disaster recovery: deciding what survives the outage
7.11Disaster recovery processesBusiness continuity and disaster recovery: deciding what survives the outage
7.12Testing the disaster recovery planBusiness continuity and disaster recovery: deciding what survives the outage
7.13Business continuity planning and exercisesBusiness continuity and disaster recovery: deciding what survives the outage
7.14Physical security implementationPhysical security in operation: running the building's defenses day to day
7.15Personnel safety and security concernsPersonnel safety: protecting the people, not just the accounts

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.

ObjectiveTopicLesson
8.1Security in the SDLCSecure SDLC: catching the vulnerability before it ships, Application security: concepts
8.2Security controls in development ecosystemsSecure SDLC: catching the vulnerability before it ships, Application security: concepts
8.3Assessing software security effectivenessSecure SDLC: catching the vulnerability before it ships, Application security: concepts
8.4Security impact of acquired softwareSecure SDLC: catching the vulnerability before it ships, Application security: concepts
8.5Secure coding guidelines and standardsSecure SDLC: catching the vulnerability before it ships, Application security: concepts