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

Chapters0/43 ▾
  1. 1.Security Principles & Control Types0/5
    1. The CIA triad: confidentiality, integrity and availability
    2. Identification, authentication, authorization and accounting
    3. Authentication factors and true multifactor
    4. Classifying controls by category and by function
    5. Risk transfer, guidelines and due care in this domain
  2. 2.Risk, Policy Hierarchy & Ethics0/4
    1. Threats, vulnerabilities, likelihood and impact
    2. The risk management lifecycle and the four treatments
    3. Laws, frameworks and the policy document hierarchy
    4. Due care, due diligence and the ISC2 Code of Ethics
  3. 3.Governance, Risk & Compliance0/4
    1. What GRC is for, and who is accountable
    2. Frameworks, standards and where obligations come from
    3. Key metrics, KPIs and key risk indicators
    4. Dashboards, scorecards, reports and AI risk indicators
  4. 4.Continuity, Disaster Recovery & Awareness0/4
    1. Redundancy, business continuity and disaster recovery
    2. Business impact analysis, RPO, RTO and alternate sites
    3. Backup types, offline copies and test restores
    4. Security awareness, culture and AI-powered phishing
  5. 5.Identity Lifecycle Management0/4
    1. Roles definition and provisioning new accounts
    2. Access reviews, movers and privilege creep
    3. Deprovisioning leavers and non-human identities
    4. Identity frameworks and tools: SSO, federation, SCIM, PAM and IGA
  6. 6.Logical Access Controls & Models0/4
    1. Least privilege and need-to-know
    2. Separation of duties, dual control and job rotation
    3. Subjects, objects and discretionary access control
    4. MAC, RBAC, rule-based and attribute-based access control
  7. 7.Network Security Concepts0/5
    1. The OSI and TCP/IP models
    2. IPv4 private addresses, NAT and IPv6
    3. VPNs: what they protect and what they do not
    4. Firewalls, ports and applications
    5. Wireless, Bluetooth, ICS and IoT devices
  8. 8.Network Architecture & Cloud Security0/4
    1. Network segmentation, firewall zones and VLANs
    2. Defense in depth and zero trust
    3. Cloud characteristics and deployment models
    4. Service models and the shared security model
  9. 9.Data Security & Security Operations0/5
    1. Data classification, labeling, data states and masking
    2. Retention and media sanitization
    3. Symmetric and asymmetric encryption, hashing and signatures
    4. Logging, monitoring and event triage
    5. Threat actors, threat intelligence and threat frameworks
  10. 10.Incident Response, Assets & Testing0/4
    1. The incident response plan, team and exercises
    2. The incident response life cycle
    3. Asset lifecycle, configuration and change management
    4. Security testing: teams, scans, application tests and physical tests
Saved in this browser. Move it to another device →
← Risk, Policy Hierarchy & Ethics

Chapter 2 · Lesson 1 of 4

Threats, vulnerabilities, likelihood and impact

1 min read

Risk questions start with vocabulary. An asset is anything of value. A vulnerability is a weakness or gap in an asset or control, such as missing patches or a door that does not lock. A threat is something that could exploit that weakness, such as a ransomware group or a flood.

Risk is the possibility of harm where a threat and a matching vulnerability meet. A threat with nothing to act on creates no risk: an office far inland has essentially no storm-surge risk, even though storm surge is real.

Each risk is rated on two factors. Likelihood is how probable it is that the risk happens; impact is how bad the result would be. In a qualitative assessment, people rate both with words or a small scale, often in a workshop, and plot the results on a heat map.

Example on a 1 to 5 scale: a rare outage that would halt production for weeks (likelihood 2, impact 5) scores 2 × 5 = 10, while a frequent but minor printer fault (likelihood 4, impact 2) scores 8. The rare, severe event ranks higher, which is why unlikely scenarios can still need treatment.

The limitation the exam asks about is that qualitative ratings produce no money figures, so they cannot directly support a cost-benefit case. Quantitative assessment adds monetary values for that purpose.

Check yourself

1. An organization has no staff, facilities, or operations within hundreds of miles of any coastline, yet its draft risk register lists hurricane storm surge as a threat. Under CC-level risk concepts, what is this organization's risk from storm surge?

2. A risk team rates each scenario Low, Medium or High using the judgment of department heads in a workshop, then plots the results on a heat map. Which approach is this, and what is its main limitation?

Facts checked 2026-11-15 · Sources: ISC2 Certified in Cybersecurity (CC) Exam Outline, ISC2 Code of Ethics

ISC2 Certified in Cybersecurity (CC) cheat sheet: every key fact on one page →