GOVERNANCE, RISK & COMPLIANCE
Governance · Risk management · Frameworks · Controls · Compliance & law · Audits · Third-party risk · BC/DR · Building a program & career
What GRC Is and Why It Pays
- GRC is three joined disciplines: governance sets direction, risk management decides what to worry about, and compliance proves you meet external rules.
- Technical skill breaks in; GRC skill decides what to build, funds it, and keeps the business out of court - that is why GRC roles are paid and in demand.
- The CISO translates between the server room and the boardroom; everyone in security eventually has to speak the language of risk and money.
- Security exists to let the business take risk safely, not to say no - a security team that only blocks gets routed around.
- GRC careers (analyst, auditor, risk manager) are open to people who are organised and clear communicators, not only to deep technical experts.
- The same hacker skills you already have make you a far better GRC professional because you know what the controls are actually defending against.
Think of a chama — a savings group of neighbours. It survives because of three things working together. There is the written constitution and the elected officials who steer it (that is governance). There is the group deciding how much cash is safe to keep, who might run off with it, and what happens if someone defaults (that is risk). And there is the yearly check by an outside member confirming the books match the M-Pesa statement and the group followed its own by-laws (that is compliance). GRC is simply running an organisation the way a well-led chama runs itself: steer it, watch what could go wrong, and prove you kept your own rules.
► Three Words, One Job
GRC stands for Governance, Risk and Compliance. It is the part of security that decides what to protect, how much to spend protecting it, and how to prove to outsiders that you did. A penetration tester finds a hole in a web application. A GRC professional answers a different set of questions: Is this the hole we should care about most? Who owns the decision to fix it? What will a regulator or a customer's auditor say if we do not? How do we show, on paper, that we manage this kind of problem across the whole company and not just this one app?
The three words describe three distinct activities that only work together. Governance is the system of direction and accountability: who decides, who is responsible, what the rules of the house are, and how leadership knows things are working. Risk management is the discipline of finding, measuring and treating the things that could hurt the organisation, and deciding - consciously - which risks to reduce, move, avoid or simply live with. Compliance is meeting obligations that come from outside: laws, regulations, contracts and standards that you did not write but must obey. A mature security program needs all three. Governance without risk management is a rulebook nobody can justify. Risk management without governance is a spreadsheet nobody acts on. Compliance without either is theatre - documents produced for an auditor and ignored the rest of the year.
| Discipline | Core question | Typical output |
|---|---|---|
| Governance | Who decides and who is accountable? | Policies, roles, a security steering committee, board reports |
| Risk | What could hurt us and what do we do about it? | A risk register, risk assessments, treatment plans |
| Compliance | What are we legally and contractually required to do? | Control mappings, audit evidence, attestations, certifications |
► Why GRC Pays More Than It Looks Like It Should
Newcomers often assume the money is in offence - exploit development, red teaming, bug bounties. Those are valuable, but look at who gets hired in a downturn and who sits in the meetings where budgets are set. Organisations spend on security for three reasons: fear of loss, pressure from customers, and pressure from regulators. All three are GRC conversations. A bank in Nairobi, a hospital in Johannesburg, or a SaaS startup selling to US enterprises does not buy a firewall because firewalls are interesting. It buys security because a breach would be expensive, because its biggest customer demands a SOC 2 report before signing, and because the Kenya Data Protection Act or Europe's GDPR carries real penalties. The person who can turn those pressures into a funded, defensible plan is rare, and rarity is what the market pays for.
► The CISO's World
The Chief Information Security Officer (CISO) is the executive who owns security. The job is mostly translation. Downward, the CISO turns business goals and risk appetite into technical priorities for engineers. Upward, the CISO turns a messy reality of vulnerabilities, incidents and near-misses into a handful of sentences a board of directors can act on. The board does not want a list of unpatched servers; it wants to know whether the company is more or less exposed than last quarter, whether spending is proportionate to the threat, and whether a headline-making incident is likely. If you want to understand what GRC is for, imagine you have forty minutes with a board once a quarter and you must leave them informed but not panicked, and willing to fund what you need.
Engineer: "The customer database server is missing three
critical patches and has no multi-factor auth."
Analyst: Logs a risk. Asset = customer PII database.
Likelihood = High (internet-exposed, known exploits).
Impact = High (regulated personal data, 2M records).
Risk mgr: Scores it Critical. Recommends treatment:
patch now, add MFA, segment the network.
Estimated loss if ignored (ALE) = KES 2,000,000/yr.
Cost to fix = KES 250,000 one-off.
CISO: Tells the board: "One of our top five risks.
Cheap to fix, expensive to ignore, and it is in
scope for our SOC 2 audit. I am funding it."
Board: Approves. The patch was never the hard part -
getting it prioritised and paid for was.► Security Exists to Enable the Business
The single most important idea in this whole module is that security is not the opposite of business - it is a condition for doing business safely. A security team whose only word is "no" gets bypassed. People will email spreadsheets of customer data to their personal accounts, spin up unsanctioned cloud servers, and sign contracts with risky vendors, precisely because the official path was too slow or too hostile. The GRC mindset is different: understand what the business is trying to do, find the risk in it, and offer a way to do it with that risk controlled. A good GRC professional is the person who helps the sales team close the enterprise deal by producing the security documentation the customer needs, not the person who slows the deal down.
► The Careers
GRC is one of the most accessible well-paid areas of cybersecurity because it rewards organisation, clear writing and judgement as much as deep technical skill. The common roles form a ladder.
| Role | What they do | Good first role for |
|---|---|---|
| GRC / Security Analyst | Maintain the risk register, map controls to frameworks, gather audit evidence, run awareness training | Entry level - organised, detail-oriented people |
| IT / IS Auditor | Independently test whether controls work, write findings, assess against SOC 2 / ISO / PCI | People who like structured testing and evidence |
| Risk Manager / Analyst | Run risk assessments, quantify exposure, advise on treatment and insurance | People who like decisions and numbers |
| Compliance Manager | Own obligations to regulators and customers, manage audits and certifications | People who like regulation and process |
| Security / GRC Lead, vCISO, CISO | Set strategy, own the program, report to leadership and the board | Experienced generalists who can communicate |
Here is the advantage you have as someone with hands-on hacking skills. Most GRC people have never exploited a misconfiguration or watched a password spray succeed. You have. When you write that multi-factor authentication is a required control, you know viscerally what happens without it. When an auditor ticks a box for "encryption at rest", you can tell whether the implementation is real or cosmetic. The strongest GRC professionals are technically literate, and the strongest technical people understand why the paperwork exists. This module turns your offence knowledge into the judgement that makes you hireable for the roles that set direction and sign the budgets.
- GRC is three joined disciplines: governance sets direction, risk management decides what to worry about, and compliance proves you meet external rules.
- Technical skill breaks in; GRC skill decides what to build, funds it, and keeps the business out of court - that is why GRC roles are paid and in demand.
- The CISO translates between the server room and the boardroom; everyone in security eventually has to speak the language of risk and money.
- Security exists to let the business take risk safely, not to say no - a security team that only blocks gets routed around.
- GRC careers (analyst, auditor, risk manager) are open to people who are organised and clear communicators, not only to deep technical experts.
- The same hacker skills you already have make you a far better GRC professional because you know what the controls are actually defending against.