Quibank app: now on the App Store — free, works offline. Get the app ↗

ISC2 Certified in Cybersecurity (CC) Cheat Sheet: Key Facts

Every key takeaway and common trap from the ISC2 Certified in Cybersecurity (CC) study guide on one page, grouped by chapter. Tap a lesson link to read the full explanation.

65 facts · 10 chaptersFacts checked 2026-11-15
  1. Security Principles & Control Types
  2. Risk, Policy Hierarchy & Ethics
  3. Governance, Risk & Compliance
  4. Continuity, Disaster Recovery & Awareness
  5. Identity Lifecycle Management
  6. Logical Access Controls & Models
  7. Network Security Concepts
  8. Network Architecture & Cloud Security
  9. Data Security & Security Operations
  10. Incident Response, Assets & Testing

Chapter 1

Security Principles & Control Types

Key takeaways

Common trap

Quick reference

The CIA triad: confidentiality, integrity and availability →
ScenePillar harmed
Customer list left on a public file share, unchangedConfidentiality
Attacker alters the data an AI model is retrained onIntegrity
Storm cuts power, data intact but unreachable for a dayAvailability
Authentication factors and true multifactor →
LoginFactor typesMultifactor?
Password plus approve a prompt on enrolled phoneKnow plus haveYes
Fingerprint plus code from a key fobAre plus haveYes
Password plus a security questionKnow plus knowNo

Chapter 2

Risk, Policy Hierarchy & Ethics

Key takeaways

Common trap

Quick reference

The risk management lifecycle and the four treatments →
TreatmentWhat happens
AvoidDo not start, or stop, the activity that creates the exposure
Mitigate (reduce)Keep the activity and add controls that lower likelihood, impact or both
Transfer (share)Shift the financial impact to a third party, such as an insurer
AcceptA documented, approved decision to absorb a risk within tolerance

Chapter 3

Governance, Risk & Compliance

Key takeaways

Common trap

Quick reference

Dashboards, scorecards, reports and AI risk indicators →
VehicleWhat it isTypical reader
DashboardVisual, near-real-time monitoringOperations team during a shift
ScorecardPeriodic rating of performance against targetsManagers reviewing control areas
ReportPeriodic written narrative with detail and contextLeadership needing the why behind the numbers

Chapter 4

Continuity, Disaster Recovery & Awareness

Key takeaways

Common trap

Chapter 5

Identity Lifecycle Management

Key takeaways

Common trap

Quick reference

Deprovisioning leavers and non-human identities →
DepartureWhen access is cut
Amicable resignation with noticeLimited access can taper during handover, ending in full deprovisioning
Dismissal or hostile terminationAt or just before notification, planned in advance by HR and security

Chapter 6

Logical Access Controls & Models

Key takeaways

Common trap

Quick reference

Separation of duties, dual control and job rotation →
ControlHow it works
Separation of dutiesDifferent people do different steps of one process
Dual controlTwo people act together on the very same step, like two keys for a vault
Mandatory vacation, job rotationDetective: a stand-in may notice what the regular holder hid

Chapter 7

Network Security Concepts

Key takeaways

Common trap

  • Ping has no port. ICMP is carried directly by IP at Layer 3 and uses message types and codes, so a firewall rule permits ICMP echo request and echo reply rather than opening a port number. → The OSI and TCP/IP models

Quick reference

The OSI and TCP/IP models →
OSI layerJob and data unitTCP/IP layer
1 Physical, 2 Data LinkBits on the wire; frames by MAC address on one segmentNetwork Access (Link)
3 NetworkPackets by IP address; routing between networksInternet
4 TransportSegments; TCP and UDP ports identify conversationsTransport
5 Session, 6 Presentation, 7 ApplicationServices such as web and mailApplication

Chapter 8

Network Architecture & Cloud Security

Key takeaways

Common trap

  • Do not treat zero trust and micro-segmentation as the same thing. Micro-segmentation is a network technique that adds internal perimeters. Zero trust is broader: it centers protection on identities, assets and data and verifies each request. The two are often deployed together. → Defense in depth and zero trust
  • Watch for answers saying a breach in the cloud is entirely the provider's problem, or that a private cloud must be self-hosted. Both are wrong: accountability stays with the customer, and private means single-organization use. → Service models and the shared security model

Quick reference

Cloud characteristics and deployment models →
CharacteristicClue in the scenario
On-demand self-serviceCapacity added through a portal with no human contact at the provider
Broad network accessReached over the network from laptops, tablets and phones
Resource poolingMany tenants share hosts, and capacity is reassigned by demand
Rapid elasticityCapacity grows and shrinks to match load
Measured serviceUse is metered and reported

Chapter 9

Data Security & Security Operations

Key takeaways

Common trap

  • Degaussing is a common wrong answer for solid-state drives. It works only on magnetic media; SSDs store data in flash cells. If the SSDs will be reused, destruction is out too, so the usual Purge choice is a cryptographic erase or the manufacturer's sanitize command. Degaussing is also not an approved Destroy technique under SP 800-88 Rev. 2. → Retention and media sanitization
  • Wrong answers often pair a script kiddie with a long espionage campaign, or a nation-state with quick cash. Match the actor to its motive and resources, and remember that threat intelligence informs decisions; it does not prove attribution for a court case. → Threat actors, threat intelligence and threat frameworks

Quick reference

Symmetric and asymmetric encryption, hashing and signatures →
GoalWhat to use
Only the recipient can read itEncrypt with the recipient's public key
Prove who sent it and that it was not changedDigital signature: hash signed with the sender's private key
Detect any change to a fileHash: one-way, fixed length
Store passwordsSalted hash from a password key-derivation function
Threat actors, threat intelligence and threat frameworks →
ActorMain motivation
Nation-stateEspionage and strategic advantage for a government; well funded and patient
Organized crimeProfit
HacktivistAn ideological or political message
Script kiddieCuriosity or notoriety, using other people's tools

Chapter 10

Incident Response, Assets & Testing

Key takeaways

Common trap

  • Reformatting or reimaging an infected machine right away sounds decisive, but it is eradication too early. Isolate first: containment limits the spread and preserves the evidence needed to learn the scope and whether data was taken. → The incident response life cycle

Quick reference

Security testing: teams, scans, application tests and physical tests →
MethodWhat it does
Vulnerability scanAutomated and broad; reports known weaknesses that may exist, which must be checked for false positives
Penetration testExpert-led; exploits and chains weaknesses to show real impact
Static analysisReads code that is not running; finds source-level defects
Dynamic analysisDrives the running app; finds server misconfiguration, session faults and exposed test paths
Threat modelingDesign-time review of likely threats, such as the STRIDE categories, with a countermeasure for each