Chapters0/43 ▾
- 1.Security Principles & Control Types0/5
- 2.Risk, Policy Hierarchy & Ethics0/4
- 3.Governance, Risk & Compliance0/4
- 4.Continuity, Disaster Recovery & Awareness0/4
- 5.Identity Lifecycle Management0/4
- 6.Logical Access Controls & Models0/4
- 7.Network Security Concepts0/5
- 8.Network Architecture & Cloud Security0/4
- 9.Data Security & Security Operations0/5
- 10.Incident Response, Assets & Testing0/4
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 →