What is GRC and Why Every Tech Company Will Eventually Need It
The demo went well. The team you are selling to wants to move forward and commercial terms are agreed. Then the contract reaches their security team and everything stops.
"Do you hold ISO 27001 certification?"
You don't. The deal goes on hold, and a few weeks later you hear they signed with a competitor who did. Your product was fine and your price was fine. Their security team had a checklist and your company could not tick the box. Many technology companies reach this moment sooner or later, and most are not ready for it.
What is GRC
GRC stands for Governance, Risk and Compliance. It is not a product you buy, and it is not a certification you earn once and forget. It is the way an organization runs so that three things stay in step.
Governance
The organization knows who is responsible for what, how decisions get made, and who answers when something goes wrong. It keeps the company working properly whoever happens to be in the room.
Risk
The organization works out what could go wrong, how likely it is and how much damage it would do, then puts controls in place. The goal is not to remove uncertainty, which cannot be done. It is to make the uncertainty visible so it can be managed.
Compliance
The organization follows the laws, regulations and standards that apply to it. Some are legal obligations, such as GDPR and DORA, and breaking them brings fines and sanctions. Others are voluntary or contractual. Nobody forces you to adopt ISO 27001, but customers may refuse to buy without it, and card payment rules require PCI DSS from companies that handle card data.
The three depend on each other. Governance without compliance gives you a company that decides well but breaks the rules. Compliance without risk management follows today's rules and cannot see what is coming. Risk management without governance produces reports that nobody acts on.
Why do we need GRC
The main reason is financial. Companies invest in GRC when the cost of ignoring it grows larger than the cost of building it, and for a growing company that tends to happen sooner than expected.
GDPR fines can reach 20 million euros or 4% of global annual turnover, whichever is higher. DORA applies to EU financial entities and gives supervisors the power to intervene when ICT risk management falls short, with penalties set by each member state. Losing an enterprise deal because you could not answer a vendor security questionnaire can cost more than the work needed to prepare for ISO 27001. Recovering from ransomware commonly takes weeks, not days. And a breach becomes public, which brings customer churn, partner reviews and investor questions before the technical recovery is even finished.
GRC is not paperwork. It is what lets a company keep growing without taking on risks it cannot see.
Real case
Apotheka Loyalty Programme
€3 Million Fine
September 2025
The Estonian Data Protection Inspectorate fined Allium UPI OÜ, the company that runs the Apotheka loyalty programme, 3 million euros. Attackers had accessed the programme's system and a database backup in early 2024 and downloaded customer data, including purchase histories and personal identification codes. The regulator said the security lapses put the privacy of more than 750,000 people at risk. Reports on the decision say it found no multifactor authentication, no activity logging and unsecured database backups. The company disagrees with the decision and is appealing it in court. Basic controls like these are what a GRC programme sets out to put in place.
Source: ERR News →Who is involved in GRC
GRC does not happen in isolation. Most programmes involve four players, and each one has a different job.
The Regulator
Sets legal requirements and enforces them. Bodies like the EBA for banking and EIOPA for insurance set supervisory standards, while national data protection authorities such as CNIL in France and the ICO in the UK enforce data protection law. Where a law applies, the regulator decides what is required, checks it and decides the consequences.
The Customer
Often the real reason a company starts. No law requires ISO 27001 or SOC 2, but enterprise customers ask for them in procurement and in security questionnaires, and a missing answer can stop a deal.
The Auditor
Independently checks that a company's controls meet a standard. For ISO 27001, an accredited certification body runs the audit and issues a certificate. For SOC 2, an independent auditing firm issues an attestation report instead. Either way, they verify. They do not get you compliant.
The Technical Team
Builds and runs the controls that make compliance real. A gap assessment can show what is missing and a policy can state what is required, but neither fixes anything. The technical team does that by implementing the security controls, configuring the infrastructure and producing the evidence the auditor will check.
The regulator and the customer set the bar. The auditor measures it. The technical team builds what is needed to meet it. The requirements are not yours to negotiate and the auditor's verdict is independent, so the part you control is how well your technical team prepares, implements and documents the controls. That is where GRC programmes succeed or fail.
When to start
Most companies only think about GRC when something forces them to: a questionnaire they cannot answer, a regulatory deadline they missed, or an incident they did not see coming. Starting before that moment is cheaper and calmer than starting after it.