GRC stands for governance, risk and compliance. It sounds like a department in a bank, yet every company already does a bit of all three. The difference is whether it does them with a method or whenever someone remembers.
What each letter means
- Governance: who decides what, under which internal rules, and how you check that those rules are followed.
- Risk: what could go wrong, how much it would hurt and what you do to make it less likely or less serious.
- Compliance: which laws, standards and contracts bind the company and how it shows that it meets them.
Together, the three answer a question for management: do we know what could harm us, and do we have it under control?
It isn't just IT
Many people come to GRC through information security: ISO 27001, NIS2 or GDPR. That's one part. The same method works for more:
- Corporate risk. The client who accounts for too much of your revenue, the person a whole process depends on, the single supplier.
- Criminal compliance. In Spain a company can be held criminally liable for certain offences committed in its name and for its benefit. Having a criminal compliance model in place can exempt it from that liability or reduce it. We explain it in corporate criminal compliance.
- Suppliers. Which third parties touch your data or your operations, and what you require of them.
- Sustainability. The environmental, social and governance data that some large clients and banks already ask their suppliers for. More in ESG and CSRD.
Why it affects mid-sized companies too
Obligations flow down the supply chain:
- Your clients pass them on to you. A company subject to NIS2 has to keep an eye on its suppliers' security, and the supplier is you.
- Some rules don't look at size. GDPR applies to any company that processes personal data. And since 2023, companies with fifty or more employees, and those in certain sectors such as finance whatever their size, must have an internal whistleblowing channel.
- Big contracts ask for it. A certification or a well-answered security questionnaire can decide whether you're in or out.
- AI adds obligations. The EU regulation on artificial intelligence also reaches companies that only use it. We cover it in Responsible AI and the AI Act.
There's also a reason that doesn't come from outside. A company reaches a size where it no longer fits in its founder's head. Writing down the risks and deciding who watches each one stops everything depending on one person's memory.
How to start without setting up a department
With four things, and none of them needs expensive software:
- A list of the obligations that really apply to you, each with someone responsible for it.
- A short risk register, twenty lines rather than two hundred, reviewed once a year.
- A few controls with their evidence: who reviews access rights, when backups are tested, who approves a payment.
- One meeting a year where management goes through it all and minutes are taken.
A piece of advice from people who have done it in-house: only commit to the controls you're actually going to carry out. A control that's declared but not done is worse than not having one, because it's in writing.
When you need a platform
All of the above fits in a spreadsheet at first. When the regulations, the companies or the people involved grow, the spreadsheet stops coping and a GRC platformmakes sense. We mainly work with eramba, and we're an eramba Gold Partner. The product, on the eramba.
The usual mistake is to do it the other way round: buy the platform first and then find out there was nothing to put in it.
In GRC and ESG we explain where we usually start with each client and which standards we cover.
Shall we look at your case?
Tell us what you have today and what you would like to have.