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 →
← Governance, Risk & Compliance

Chapter 3 · Lesson 3 of 4

Key metrics, KPIs and key risk indicators

1 min read

The outline's measurement section starts with key metrics and key risk indicators. A key performance indicator (KPI) reports how well the program is doing what it promised, such as the percentage of servers patched within the agreed window.

A key risk indicator (KRI) is forward-looking: it is chosen because it moves before a loss does, and it has a defined threshold that triggers escalation or action.

The number of privileged accounts without multifactor authentication, escalated to the risk committee once it passes a set level, is a KRI. Counts of closed tickets, spending against budget and past audit findings describe what already happened, so they are status figures rather than KRIs.

A useful metric is tied to an objective and can change a decision. Activity counts such as blocked emails or firewall denies measure how busy the tools are, not whether protection improved. A point-in-time number also needs context.

Example: "312 open vulnerabilities" means little alone, but against a baseline of 400 three months ago and 350 last month, it shows a 22 percent drop from baseline, a trend the reader can act on.

Check yourself

1. A programme reports two figures monthly: the percentage of servers patched within the agreed window, and the number of privileged accounts without multifactor authentication, which escalates to the risk committee once it passes a set threshold. How are these best classified?

2. A risk committee asks the security lead to propose a key risk indicator rather than another status number. Which characteristic must the proposed measure have?

Facts checked 2026-11-15 · Sources: ISC2 Certified in Cybersecurity (CC) Exam Outline, NIST Cybersecurity Framework (CSF) 2.0

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