Risk

GRC and risk management trends: what 2026 brought and what carries into 2027

· 10 min read ·

In November 2026, the GRC trends that were forecast for the year can now be read against data. The cost of breaches rose again, vulnerability exploitation became the leading way into breaches, AI appeared on both sides of risk, and Brazilian regulation moved, not always in the expected direction. This review brings together what 2026 showed and what carries into the 2027 agenda for CISOs, CROs and GRC leaders.

This piece started life as a list of trends for 2026 and was revised in November, with the year almost over. That is why each trend comes with the data point that confirmed or corrected it, and the report edition it came from.

Which forces shaped GRC in 2026?

Four forces dominated the agenda: vulnerability volume, the cost of incidents, regulation and the board's demand for clarity. They do not act in isolation. Volume puts pressure on prioritisation, regulation demands evidence that controls work, and the board wants to know what an incident would cost, not how many alerts are still open.

Volume sets the tone. In 2025, 48,185 CVEs were published, 20.6% more than the 39,962 in 2024, excluding rejected entries (Jerry Gamblin, 2025 CVE Data Review, based on NVD and CVE List data). According to NIST, CVE submissions grew 263% between 2020 and 2025. In response, since 15 April 2026 the National Vulnerability Database (NVD) has prioritised enrichment for CVEs in CISA's KEV catalogue, those used by the US federal government and those affecting critical software. The rest stay in the database but are not scheduled for immediate enrichment (NIST, NIST Updates NVD Operations to Address Record CVE Growth, April 2026).

In practice, teams that waited for NVD analysis before deciding what to fix now wait longer, or never get that analysis at all. Combining CVSS, EPSS, KEV and asset criticality is no longer a refinement; it is a precondition for prioritising, as we show in 48,000 CVEs a year: where to start.

The attack vector confirmed the urgency. In the 2026 edition of its Data Breach Investigations Report, published in May, Verizon reports that 31% of breaches began with vulnerability exploitation, which overtook the use of stolen credentials for the first time in 19 years. The same report records third-party involvement in 48% of breaches (Verizon, 2026 DBIR).

How did AI change compliance, and risk itself, in 2026?

AI moved forward on two fronts at once. In GRC operations, it began supporting classification, cross-framework control correlation, evidence organisation and prioritisation. On the risk side, it became a new vector that needs its own governance.

In operations, the model that holds up is human-in-the-loop: AI suggests, prioritises and documents, and a person makes the final decision, with a record of the context behind each recommendation. Teams that are starting out usually gain most by first automating repetitive, low-risk tasks, as we show in AI compliance automation: where to start. The gain also shows up in incidents: in the 2026 edition of its Cost of a Data Breach report, IBM links extensive use of AI and automation in security to savings of US$1.93 million per breach, compared with organisations that use none (IBM, Cost of a Data Breach Report 2026).

On the risk side, the signals came from more than one source. In the 2025 edition of the same report, IBM estimated that heavy use of shadow AI, meaning unapproved AI tools, added US$670,000 to the global average cost of a breach (IBM, 2025 Cost of a Data Breach Report). In 2026, the DBIR found that frequent use of AI tools by employees jumped from 15% to 45% in a single year, and IBM warned of companies adopting agentic AI without strengthening security and governance for agents. The conclusion for 2027 is straightforward: an inventory of models and agents, a usage policy and access control belong in the GRC programme like any other risk (see AI Governance Software: What It Is and How to Choose It).

What changed in Brazilian regulation in 2026?

Regulatory pressure came from three fronts: financial services, data protection and sustainability. And the biggest news of the year was a step back.

In financial services, CMN Resolution No. 4,893/2021, issued by Brazil's National Monetary Council (CMN), remains the baseline for institutions authorised by the Central Bank of Brazil (BACEN). It requires a cyber security policy (art. 2) and an action and incident response plan (art. 6), both approved by the board of directors or, where there is none, by the executive board (art. 9). It also requires governance procedures and checks on the provider before contracting material data processing, data storage and cloud computing services (arts. 11 and 12). CMN Resolution No. 5,274, of December 2025, expanded the minimum list of controls in the policy (art. 3, § 2), adding items such as encryption, intrusion detection, vulnerability remediation, digital certificate management and cyber intelligence. The details are in Brazil's CMN Resolution 5,274/2025: what changed for financial sector cybersecurity and, for suppliers, in Third-party risk and CMN Resolution 4,893.

Abstract digital background representing data protection and secure network connections

In data protection, Brazil's General Data Protection Law (LGPD) still requires a legal basis for each processing activity (art. 7), records of processing operations (art. 37) and security measures to protect personal data (art. 46). The map of regulations from the ANPD, the national data protection authority, that detail these obligations is in ANPD regulations: a map of what your company must comply with.

In sustainability, the timetable changed. CVM Resolution No. 193/2023 made the sustainability-related financial information report, based on the ISSB standard, mandatory for listed companies from financial years starting in 2026. CVM Resolution No. 244, of 29 May 2026, revoked that requirement. The report remains voluntary and, from 1 January 2027, a listed company that chooses not to file it must explain its choice in a market announcement. Companies that opt to report must publish for at least three consecutive financial years and, for years starting in 2026 or later, obtain reasonable assurance from an independent auditor registered with the CVM.

For the GRC leader, the practical effect is the same on all three fronts: one control has to answer to several standards and several audiences. Mapping controls across frameworks once, on a single inventory, stops each new requirement from becoming a project that starts from scratch.

Why has cyber risk settled on the board's agenda?

Because it now has a price. In its 2025 Public Company Board Practices and Oversight Survey, the NACD, the US association of corporate directors, reports that 77% of directors already discuss the material and financial implications of cyber incidents (NACD, July 2025). In April 2026, the NACD and the Internet Security Alliance published the fifth edition of the Director's Handbook on Cyber-Risk Oversight, with expanded guidance on emerging technologies, supply chain risk and incident response coordination, as well as reporting metrics (NACD, April 2026).

The cost of breaches keeps the conversation going. In the 2026 edition of Cost of a Data Breach, IBM records a global average cost of US$4.99 million, up 12% on the previous year and the highest in the series. The hope for relief raised by the 2025 edition, which showed US$4.44 million and the first fall in five years, did not hold.

That changes what is expected of the CISO. The board does not want to hear about CVEs or firewall rules. It wants to understand exposure in terms of revenue, continuity and reputation, with the same indicators every cycle, so it can follow the trend rather than a single snapshot. The step-by-step guide is in How the CISO should report cyber risk to the board.

What carries into 2027, and how to prepare?

Nothing that shaped 2026 shows signs of fading in 2027: vulnerability volume, dependence on third parties, AI on both sides of risk and the board's demand for numbers. Preparing means moving away from fragmentation.

The first step is to unify the control inventory. When the same control serves ISO/IEC 27001, the LGPD, the NIST CSF and the criteria of a SOC 2 report, each piece of evidence counts for several frameworks at once. The second is to prioritise by risk, not by volume. With tens of thousands of CVEs a year, the remediation queue has to combine asset criticality, active exploitation and business impact.

A practical sequence for 2027 planning:

  1. Consolidate risks, controls, assets and suppliers in a single source.
  2. Map controls across the applicable frameworks once.
  3. Organise evidence with a record of source, date and owner.
  4. Inventory AI use, including unapproved tools and agents, and define who approves what.
  5. Set stable risk indicators for board reporting.
  6. Extend risk assessment to third parties and the supply chain.

Eagle, Futture's Enterprise Risk Intelligence platform, was designed around these principles. In the GRC module, a control mapped once can be reused across frameworks, with traceability to each requirement. Eagle's AI suggests priorities and relationships, and the user reviews, approves, rejects or adjusts every relevant result.

The next step is concrete. List the frameworks your company needs to meet in 2027 and check how many controls are, in practice, the same control repeated. The exercise shows the size of today's rework and is a good starting point for unifying risk management.

Further reading: How the CISO should report cyber risk to the board; 48,000 CVEs a year: where to start; AI Governance Software: What It Is and How to Choose It.

Frequently asked questions

Which GRC trends defined 2026?

Four forces: the volume of vulnerabilities and their exploitation as the leading way into breaches, AI showing up both in compliance operations and in the risk itself, regulatory changes in Brazil, and boards asking for cyber risk in financial terms, backed by traceable evidence.

How did AI change risk and compliance management in 2026?

It began supporting classification, control correlation, evidence organisation and prioritisation, in a human-in-the-loop model where a person makes the final decision. At the same time it became a source of risk: unapproved tools and AI agents call for an inventory, a usage policy and access control.

What changed in Brazilian GRC regulation in 2026?

CVM Resolution No. 244/2026 revoked the requirement for listed companies to file an ISSB-based sustainability report; from 2027, those that do not file must explain why. In financial services, CMN Resolution No. 4,893/2021 still applies, as amended by Resolution No. 5,274/2025, which expanded the minimum controls in the cyber security policy.

Why is cyber risk on the board's agenda?

Because it has a direct financial impact. In NACD's 2025 survey, 77% of directors said they already discuss the financial implications of cyber incidents, and the 2026 edition of IBM's report recorded a record global average cost of US$4.99 million per breach.

How should a GRC programme prepare for 2027?

Unify the control inventory, map controls across frameworks once, prioritise vulnerabilities by business risk, inventory AI use, keep evidence traceable and take stable indicators to the board, expressed as financial impact.

Official references

About the author

Founder, Futture.ai | CISSP

Cybersecurity, governance and risk management specialist with over 25 years of industry experience. CISSP-certified, founder of Network Secure and Futture.ai.

Read next

← Back to the blog