ResilientX

What Is GRC? Governance, Risk and Compliance

Summary:

What GRC means, where the term came from, what each letter does, how GRC differs across finance, legal and security teams, and one worked example.

GRC stands for governance, risk and compliance: the combined way an organization decides who is in charge and within what limits (governance), ranks and treats what could stop it reaching its objectives (risk), and proves it meets the laws, standards and contracts that apply to it (compliance).

The three only work when they share one set of decisions and one set of evidence. That is the answer to "what is GRC" in brief. The rest of this page explains each letter, where the term came from, what it means to different teams, and how it looks on a real decision. For the security-specific version, including what NIS2 and DORA require, see our complete guide to GRC in cybersecurity.

What does each letter in GRC mean?

Governance is the decision system. It sets objectives, approves policies, defines who may accept which risks, and decides how leadership is kept informed. A governance gap looks like a policy nobody enforces.

Risk management is the prioritization system. It identifies what threatens the objectives, scores each threat consistently, chooses a treatment and tracks what remains. A risk gap looks like a long list of issues worked in the order they arrived. Our guide to GRC risk management shows a risk moving from inherent to residual with real numbers.

Compliance is the proof system. It maps external obligations to internal controls and collects evidence that those controls operate. A compliance gap looks like a team that does the right thing but cannot show it.

Where did the term GRC come from?

The acronym comes from the Open Compliance and Ethics Group. OCEG states that it created the term and used it as early as 2002, and it defines GRC as "the integrated collection of capabilities that enable an organization to reliably achieve objectives" while addressing uncertainty and acting with integrity. OCEG calls the goal Principled Performance.

The key word in that definition is integrated. GRC was coined to describe what happens when governance, risk and compliance stop running as separate functions with separate spreadsheets.

What does GRC mean to different teams?

The same three letters carry different weight depending on who says them. This is a common source of confusion when a GRC project starts.

TeamWhat "governance" means to themWhat "risk" meansWhat "compliance" means
Finance and internal auditInternal control, approvals, segregation of dutiesFinancial and operational riskFinancial reporting rules and audit findings
Legal and ethicsCodes of conduct, board oversightLegal, regulatory and reputational exposureLaws, regulations and investigations
IT and securitySecurity strategy, policies, decision rightsCyber and ICT risk to systems and dataISO/IEC 27001, NIS2, DORA, customer questionnaires
PrivacyData protection accountabilityRisk to individuals' rightsGDPR records, impact assessments, data subject requests

None of these readings is wrong. A GRC program works when the teams agree on one scoring method, one place for policies and one place for evidence, even if each team cares about different rows.

What is a GRC framework?

A GRC framework is the structure you use to organize the work: which controls exist, how risks are scored, who approves what and how often everything is reviewed. Most organizations borrow the structure instead of inventing it.

In security, the common choices are ISO/IEC 27001 and the NIST Cybersecurity Framework 2.0. CSF 2.0, published on 26 February 2024, added GOVERN as a sixth Function, covering how cybersecurity risk management strategy, expectations and policy are established, communicated and monitored. That addition made governance an explicit part of the framework instead of an assumption.

Regulations then sit on top. A European company in scope of NIS2 maps the directive's requirements onto whichever framework it chose, so one control can satisfy several obligations.

What does GRC look like on a real decision?

Take one event: the business wants to onboard a new cloud supplier that will process customer data.

  1. Governance has already set the rule: suppliers handling customer data are tiered as critical and need a security assessment before signature, approved by the CISO.
  2. Risk management runs the assessment, often with a standard questionnaire such as the SIG questionnaire, and records two findings as risks with owners and treatment dates.
  3. Compliance stores the assessment and the approval as evidence, mapped to the supply chain requirement in NIS2 Article 21(2)(d).
  4. Back to governance: one finding sits above appetite, so the CISO either requires a contract clause or escalates the acceptance to leadership.

Without GRC, those four steps happen in three inboxes and the third one is usually skipped.

How do you start with GRC?

Start small and in order: agree the scope, write down who can accept which risks, pick one scoring scale, list your top risks with owners, and map your existing controls to the obligations that apply to you. Our 90-day GRC implementation roadmap turns that into weekly steps.

Once the links between policies, risks, controls and evidence matter more than the lists themselves, a platform helps. ResilientX GRC software keeps frameworks, controls, risks, vendors, assets, policies, audits and evidence in one connected record, with cross-mapped NIS2, DORA, ISO 27001 and GDPR libraries. See ResilientX GRC in action if that is the stage you are at.

Frequently asked questions

What is the difference between GRC and compliance?

Compliance is one of the three parts. It answers whether you meet a specific obligation. GRC also covers the decisions behind it (governance) and the prioritization of what matters most (risk). An organization can be compliant with a standard and still badly governed, for example when controls pass audits but nobody with authority has accepted the risks they leave open.

Is GRC a job title or a software category?

Both. GRC analysts, managers and leads run the processes: policies, risk registers, control testing and audits. GRC software is the tooling that holds those records and links them. The role exists without the software, but the software is usually adopted once spreadsheets can no longer show how a failed control affects a risk.

Who owns GRC in a company?

Leadership owns the decisions, which NIS2 Article 20(1) makes explicit for the management bodies of entities in scope. Day to day, a GRC or compliance lead coordinates the processes, risk owners in the business decide on their risks, and control owners produce the evidence. In security-led programs the CISO usually coordinates all three.

The short version

GRC is governance, risk and compliance run as one system: decisions with clear owners, risks ranked by what they threaten, and evidence that controls work. The term dates from 2002; the need for it has only grown.

See ResilientX GRC in action — book a demo to see policies, risks, controls and evidence in one place.

Run NIS2, DORA, ISO 27001 and GDPR from one control library
Explore ResilientX GRC →