Study guide

Missed-Question Notebook and Domain Repair

ISC2 Certified in Cybersecurity CC

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

Official 2026 CC Exam Facts and Timeline CAT Format and Beginner Security Judgment Domain Map and Time Allocation 30, 60, and 90 Day Study Plan with Readiness Thresholds

2 Domain 1: Security Principles (24%)

CIA Triad as a Practical Decision Tool Authentication, Authorization, Accounting, and Non-Repudiation Privacy in the CC Outline Beginner Security Decision Scenarios AI Security in Security Principles

3 Domain 1: Risk Management and Security Controls

Risk Identification in Business Context Risk Management Processes Risk Treatment Decisions Security Controls: Technical, Administrative, and Physical

4 Domain 1: Governance, Ethics, Policy, and Privacy

Governance and the ISC2 Code of Ethics Policies, Procedures, Standards, Laws, and Regulations Privacy and AI Governance Due Care, Due Diligence, and Governance Decisions

5 Domain 1: Physical Security Controls

Physical Controls and Their Monitoring Tailgating and Physical Penetration Testing

6 Domain 2: Security Governance - Business Continuity

Business Continuity (BC)

7 Domain 2: Security Governance - Disaster Recovery

Disaster Recovery (DR) Redundancy in Business Continuity and Disaster Recovery

8 Domain 2: GRC Planning

GRC Planning: Purpose, Importance, and Tools

9 Domain 2: Measuring Cybersecurity Effectiveness

Security Metrics, KRIs, and Dashboards AI Security in Governance, Awareness, and Continuity

10 Domain 2 and Domain 5: Security Awareness and Triage

Security Awareness and Organizational Culture Phishing and Password Protection Security Event Triage and Human Review

11 Domain 3: Identity Lifecycle Management

Identification, Authentication, Authorization, and Accountability Multi-Factor Authentication and Password Protection Provisioning, Deprovisioning, and Access Reviews Service Accounts and AI Bots in Identity Management AI Bots and Service Accounts in Identity Management

12 Domain 3: Logical Access Controls

Least Privilege and Separation of Duties DAC, MAC, RBAC, and ABAC

13 Domain 4: Networking Fundamentals

Network Models and IP Addressing Firewalls: Ports and Applications Virtual Private Networks (VPN) Wireless Networks and Embedded Systems

14 Domain 4: Network Security Architecture and Cloud Security

Network Segmentation Defense in Depth and Zero Trust Cloud Characteristics and Shared Security Model Cloud Service Models, Deployment Models, and Shared Security AI in Network Security and Cloud Hosting

15 Domain 5: Incident Response

Incident Response (IR) and the Incident Response Plan Preparing the Incident Response Plan Incident Response Exercises and Tabletops AI in Security Operations and Incident Response

16 Domain 5: Security Monitoring

Logging and Monitoring Security Events

17 Domain 5: Threat Actors and Threat Intelligence

Threat Actors, Threat Intelligence, and Frameworks

18 Domain 5: Data Security

Encryption and Hashing for Data Security Data Handling: Classification, Labeling, Masking, and Sanitization Security of the AI Workspace

19 Domain 5: Asset Protection

Configuration and Change Management Change Management and Asset Protection Asset Lifecycle and End-of-Life Management

20 Domain 5: Data Handling Policy

Data Handling Policy and Classification

21 Domain 5: Security Testing

Security Readiness, Application, and Physical Testing

22 Integrated CC Scenario Labs

Risk and Control Selection Drill Continuity, Recovery, and Response Drill Access Control Design Drill Segmentation and Triage Drill

23 Final 14-Day Review and Exam Readiness

CAT Pacing and 100-125 Item Strategy Missed-Question Notebook and Domain Repair Exam Day Logistics and Rescheduling After Passing: AMF and CPE

Missed-Question Notebook and Domain Repair

Key Takeaways Explain This Topic AI

A missed-question notebook should capture WHY the chosen answer was wrong, not just the correct option.

Weak-point repair is most effective when organized by domain, task, concept, and recurring scenario pattern.

Repeated misses usually reveal a reasoning gap such as confusing authentication with authorization or business continuity with disaster recovery.

Domain weights (24, 17.3, 20, 21.3, and 17.3 percent) help prioritize review time, but no domain should be ignored.

Shift practice from passive rereading to active retrieval, out-loud explanation, and mixed scenario drills.

Last updated: October 2026

Why a Reason-Based Notebook Wins

The final two weeks are not for rereading everything at equal effort; they are for finding weak patterns and repairing them. A missed-question notebook earns its keep only when it records the reason for the miss. "The answer was the second option" teaches nothing. "I picked multi-factor authentication, but the user was already logged in and the real issue was permission to approve payments" teaches a transferable rule: authentication proves identity, authorization decides what an identity may do.

Notebook Format

Keep it compact enough that you will actually maintain it across 14 days.

  • Field Example entry
  • Date 2026-04-29
  • Domain Domain 3 — Identity and Access Management Concepts (20%)
  • Topic Authorization and separation of duties
  • Why I missed it Chose MFA; real problem was one person both approving and paying a vendor
  • Correct rule MFA verifies identity; separation of duties prevents one person holding conflicting powers
  • Repair action Do 10 mixed access-control items, write 3 of my own scenarios

The repair action is the engine. If a miss involved business continuity versus disaster recovery , do not just reread the glossary; write one mini-scenario about keeping operations running (BC) and one about restoring a failed system (DR). If a miss involved DNS, log the clue "IP works, name fails." Active retrieval makes a concept usable under a clock.

Prioritizing With Domain Weights

A weak high-weight domain (Security Principles 24%, Networking and Cloud Security 21.3%, Identity and Access Management 20%) deserves urgent attention. But Security Governance (including BC and DR) and Security Operations and Incident Response each sit at 17.3% — easy points you must not surrender by ignoring them. Weight tells you where to spend more time, never where to spend zero .

Map Misses to Repairs

Weak pattern Likely repair

Confusing CIA goals (confidentiality vs integrity vs availability) Label the single main harm in 20 short scenarios

  • Mixing BC, DR, and IR Sort 15 actions into continuity, recovery, and response columns
  • Missing access-control clues Drill AAA and non-repudiation (subdomain 1.1)
  • Forgetting ports/protocols Tie each port to a symptom , not rote memorization alone
  • Poor operations triage Practice the verbs: first, best, most likely action
  • Scenario Pattern Library

Build one page of if-this-then-that clues and rehearse them until they are reflexive:

Connects by IP but not by name → DNS .

Former employee can still log in → deprovisioning / least privilege .

Repeated requests that overwhelm a public site → availability (but verify the evidence in the stem).

Backups exist but no restore test → recovery confidence is unproven .

One person can both request and approve payment → separation of duties .

A file's hash changes unexpectedly → integrity violation .

A device on the guest network reaches finance servers → segmentation failure .

Three-Part Repair Sessions

Every repair session should run recall, apply, verify . First, close the notes and write everything you remember about the topic. Second, answer scenario items or invent your own. Third, check the source and correct your rule in the notebook. Keep sessions short and specific: "Study networking" is too broad; "Explain DNS, Dynamic Host Configuration Protocol (DHCP), HTTPS, Secure Shell (SSH), Remote Desktop Protocol (RDP), and VPN clues on one page" is actionable.

A Common Trap

Do not let the notebook become a scoreboard of failure that you avoid. It is a map of where points leak. After a few days, sort misses by cause : if most come from rushing, drill slowing down on the final sentence; if from definitions, use flash recall; if from interpretation, practice decision tables. Repairing the cause fixes many future items at once, which is far more efficient than memorizing individual answers.

Turning One Miss Into Five Saved Points

Most CC misses cluster into a small number of root confusions, so each repaired root protects several future items. Consider the most common clusters and the leverage each repair provides. Confusing confidentiality, integrity, and availability is a root that can affect questions in several domains, because many controls are chosen by the goal they protect. Confusing authentication with authorization affects Identity and Access Management items and some triage items, so one repair can pay off in more than one domain.

Sorting business continuity, disaster recovery, and incident response is one skill that supports the lower-weight Security Governance and response items.

Because of this leverage, rank your repair effort by root rather than by count . If your notebook shows ten misses but only three roots, schedule three focused repair sessions, not ten scattered ones. Write the root rule at the top of each session in your own words, then prove it against fresh mixed questions until you can explain why each correct answer is correct without peeking. When you can teach the rule aloud in two sentences, it is repaired.

This explanation step matters: being able to justify a right answer is stronger than recognizing it, because plausible distractors can fool recognition alone.

Source: ISC2 CC Exam Outline effective September 1, 2026 (v01/2026), the five domains and subdomains used to label each missed question, checked 2026-10-22.