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 4 of 4

Dashboards, scorecards, reports and AI risk indicators

1 min read

The outline names three ways to deliver results, and each suits a different rhythm and reader. Picking the wrong one is a common reporting failure, because the format sets how current and how detailed the reader expects the information to be.

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

Reporting must match the audience. A board governs, so a short board briefing should state exposure as business impact and name the decisions or resources being requested. Hostname lists, firewall rule changes and raw alert counts belong with technical teams.

Example: instead of "we saw 9,000 alerts," tell directors that a supplier outage could stop online orders for two days and ask them to approve funding for a second supplier.

The outline also lists AI-specific KRIs. For a model that scores loan applications, tracking model drift, the declining performance of a model as real-world conditions move away from its training data, can serve as one: it moves before bad decisions pile up and can be given a threshold that triggers review or retraining.

Request volumes or vendor claims describe usage, not rising exposure.

Check yourself

1. Three artifacts are proposed: a screen the operations team watches through the shift, a quarterly sheet rating each control area against its target, and a written quarterly narrative explaining what changed and why. Which names them in order?

2. A company runs an AI model that scores loan applications. Risk staff want an AI-specific key risk indicator on the governance dashboard. Which measure fits that purpose?

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 →