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

What GRC is for, and who is accountable

1 min read

GRC combines three disciplines that answer different questions. Governance is the board and senior management function that sets direction, assigns accountability and provides oversight. Risk management identifies, assesses and treats the risks that could stop the organization achieving its mission.

Compliance demonstrates that legal, regulatory and contractual obligations are being met. A GRC program exists to make all three repeatable, and its outputs are artifacts such as policies, a risk register and reports, not a list of products. No program can promise zero incidents.

Compliance is a floor, not a ceiling. An audit checks a defined set of requirements on a defined date, so an organization can pass every test and still carry risks the requirement set never covered, and its exposure changes the day after the audit.

Example: a clinic passes its annual audit in March, then adopts a new cloud scheduling tool in April that no audit control addressed. It is still compliant on paper, but its real risk has changed.

Governance also separates responsibility from accountability. Responsibility for doing the work can be delegated down to system owners and administrators. Accountability for the outcome stays with senior leadership, who approve policy and set direction.

Accepting residual risk is a business decision, so it belongs to the senior manager or system owner accountable for that business function. Analysts measure and advise, administrators implement, and auditors examine, but none of them can commit the organization to carry a loss.

Check yourself

1. A company describes its security programme as "GRC." Which statement best describes what each of the three parts contributes?

2. After mitigation, a documented level of residual risk remains on a business application. Whose formal acceptance does governance doctrine require before the system stays in production?

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 →