What do governance, risk, and compliance each mean?
Governance is how an organization makes decisions and assigns accountability. It covers the board and leadership oversight, the policies that express management intent, and the roles that own each outcome. A security policy approved by leadership, with a named owner and a review date, is a governance artifact.
Risk management is the process of identifying what could prevent the organization from meeting its objectives, estimating how likely and how damaging each scenario is, and choosing a response: mitigate, transfer, avoid, or accept. The working record of that process is usually a risk register.
Compliance is the ability to demonstrate that the organization meets external obligations (laws, regulations, customer contracts) and internal ones (its own policies and chosen frameworks). Compliance depends on security controls and the audit evidence that proves they operate.
| Component | Core question | Typical artifacts |
|---|---|---|
| Governance | Who decides, and who is accountable? | Policies, charters, RACI matrices, committee minutes |
| Risk | What could go wrong, and what will we do about it? | Risk register, risk assessments, treatment plans, vendor reviews |
| Compliance | Can we prove we meet our obligations? | Control matrix, evidence, audit reports, certifications |
How do governance, risk, and compliance work together?
The three parts form a loop. Governance sets objectives and risk appetite. Risk management measures what threatens those objectives and selects controls to reduce the risk to an acceptable level. Compliance verifies that those controls exist and work, and reports the results back to governance, which adjusts direction.
When the parts run separately, the same work gets done three times. The security team tracks risks in one spreadsheet, the compliance team maps controls in another, and leadership sees a slide deck that matches neither. Integrating them means one control inventory, where each control links to the risks it reduces, the framework requirements it satisfies, and the evidence that proves it works.
A single control such as "production access requires MFA" can then satisfy a SOC 2 criterion, an ISO 27001 Annex A control, and a NIST 800-53 requirement at once, with one piece of evidence instead of three.
What does GRC mean in cybersecurity?
GRC started as a broad enterprise discipline covering financial, legal, and operational risk. In cybersecurity it narrows to information risk: deciding which security controls the organization needs, and proving they work to customers, auditors, and regulators. Most of that proof is organized around a small set of frameworks.
- SOC 2: AICPA attestation report that SaaS and service companies share with customers.
- ISO/IEC 27001: International standard for an information security management system, with third-party certification.
- NIST CSF 2.0: Voluntary outcome-based framework organized into six functions, including Govern.
- NIST SP 800-53: Detailed control catalog used by U.S. federal systems and FedRAMP.
- CMMC: Department of Defense program that verifies contractor cybersecurity.
Cybersecurity GRC also covers third-party risk management, security awareness, incident response readiness, and privacy obligations that overlap with security.
Who works in GRC?
GRC work shows up under many titles. Common roles include:
- GRC analyst: Maintains the control inventory, collects evidence, supports audits, and tracks remediation.
- Risk manager: Runs risk assessments, owns the risk register, and reports risk posture to leadership.
- Compliance manager: Owns framework programs such as SOC 2 or ISO 27001 and manages auditor relationships.
- IT or internal auditor: Independently tests whether controls are designed and operating as described.
- GRC engineer: Builds the automation behind the program: evidence pipelines, controls as code, and monitoring.
- CISO or security leader: Sets security governance, accepts or escalates risk, and reports to executives and the board.
How GRC engineers automate GRC
Traditional GRC runs on spreadsheets, screenshots, and annual audit cycles. That approach breaks down when infrastructure changes daily. GRC engineering applies software practices to the same goals. The discipline is covered in depth in GRC Engineering 101; typical automation looks like this:
- Evidence from APIs: A scheduled Python job calls the AWS IAM, Okta, or GitHub APIs to export MFA status, access lists, and branch protection settings, then stores timestamped JSON as audit evidence.
- Continuous control checks: AWS Config rules, Azure Policy, or GCP Organization Policies evaluate resources as they change and flag drift, such as an unencrypted storage bucket.
- Policy as code in CI: Open Policy Agent or Checkov checks Terraform plans in a pull request and blocks changes that violate a control before they reach production.
- Machine-readable controls: OSCAL catalogs and system security plans let teams express controls and their implementation as structured data instead of documents.
- Risk data from live systems: Vulnerability, asset, and misconfiguration findings feed the risk register automatically, so risk scores reflect the current environment.
For implementation detail, see policy as code, OSCAL, and continuous compliance monitoring.
Frequently asked questions
What does GRC stand for?
GRC stands for governance, risk, and compliance. Governance sets direction and accountability, risk management identifies and treats threats to objectives, and compliance shows that the organization meets its laws, contracts, and chosen frameworks. Together they form one coordinated program instead of three separate functions.
What is GRC in cybersecurity?
In cybersecurity, GRC is the program that decides which security controls an organization needs, why it needs them, and how it proves they work. It connects security risk to business decisions and maps controls to frameworks such as SOC 2, ISO 27001, NIST CSF, NIST 800-53, and CMMC.
Is GRC a technical job?
Traditional GRC roles lean toward policy, risk analysis, and audit coordination, so deep coding skills have not been required. That is changing in cloud-heavy companies, where GRC teams increasingly pull evidence from APIs and write controls as code. The technical version of the role is usually called GRC engineering.
What is the difference between GRC and GRC engineering?
GRC is the discipline: the goals, frameworks, and oversight. GRC engineering is a way of doing that discipline with software, using scripts, infrastructure as code, and pipelines to collect evidence and enforce controls continuously. Both share the same objectives, only the execution differs.
What frameworks are part of GRC?
Common cybersecurity frameworks in a GRC program include SOC 2, ISO/IEC 27001, the NIST Cybersecurity Framework, NIST SP 800-53, CMMC, PCI DSS, and HIPAA. Most organizations pick the frameworks their customers, regulators, or contracts require, then map one set of internal controls to all of them.
What is a GRC tool?
A GRC tool is software that stores policies, risks, controls, evidence, and audit findings in one place. Some teams use a commercial platform, others build lighter systems from a ticketing tool, a code repository, and cloud-native services. The tool matters less than having an accurate control inventory tied to real evidence.