Frameworks

What is the difference between GRC and ISMS?

Direct answer

GRC (Governance, Risk, and Compliance) is a broad management discipline covering how an organisation directs strategy, manages risk, and meets regulatory obligations across all domains. An ISMS (Information Security Management System) is a specific implementation of governance and risk management focused on information security, typically conforming to ISO 27001. An ISMS is one component within a wider GRC programme.

What does an ISMS require under ISO 27001?

An ISMS is defined by the requirements of clauses 4 to 10 of ISO/IEC 27001:2022, which no certified organisation can exclude. In short:

  • A defined scope (clause 4.3) and an information security policy (clause 5.2).
  • A risk assessment process and a risk treatment process (clauses 6.1.2 and 6.1.3), with their results retained, a Statement of Applicability and a risk treatment plan.
  • Information security objectives (clause 6.2) and evidence of competence (clause 7.2).
  • Control of documented information (clause 7.5): version, approval, availability and retention.
  • Monitoring and measurement (clause 9.1), internal audit (clause 9.2) and management review (clause 9.3).
  • Nonconformities and corrective action (clause 10.2).

The controls themselves come from risk treatment. Annex A lists 93 controls in four themes, and each one is included or excluded with a justification. The full list of required documents is in Which documents does ISO 27001 require?

What does GRC cover that an ISMS does not?

An ISMS answers one question: is information adequately protected? A GRC programme answers the same question for every obligation the organisation carries, and keeps them consistent.

  • Governance: policies, roles, objectives and oversight that apply across domains, not only to information security.
  • Risk: one risk method and one register for security, privacy, continuity, supplier and wider business risks, so they can be compared and escalated the same way.
  • Compliance: several frameworks and laws at once, for example ISO 27001, SOC 2, NIS2, DORA for financial entities, and privacy laws such as the GDPR and the Swiss FADP.

These programmes share the same building blocks: risks, controls, owners, documents and evidence. Run separately, each one rebuilds them. Run as one GRC programme, a control is built once and counts for every obligation it serves. See cross-framework control mapping.

Who needs an ISMS, and who needs a wider GRC programme?

An ISMS is the usual starting point for an organisation that wants ISO 27001 certification, or whose customers ask how it protects their data. It is also a sound base for NIS2: the cybersecurity risk-management measures of Article 21(2) of the Directive, such as risk analysis, incident handling, business continuity and supply chain security, overlap with what an ISMS already covers. See does ISO 27001 cover NIS2?

A wider GRC programme becomes necessary once a second framework, a sector regulation or a privacy programme arrives. The common mistakes at that point are:

  • Building a second, parallel set of controls and policies for the new framework.
  • Keeping a separate risk register per programme, with different scales.
  • Treating the ISMS as a document set for the auditor rather than a system that runs all year.
  • Leaving the ISMS scope undefined, so nobody can say which sites, entities or products it covers.

How do the ISMS and the GRC programme fit together in Acuna GRC?

In Acuna GRC, ISO 27001 is one framework you adopt in the Comply workspace, next to SOC 2, NIS2 or any other. Scopes, such as a legal entity, a site or a business unit, record where it applies. Its requirements then sit in Implement with the others, and a measure in the Measure Library can address clauses from several frameworks at the same time. Reference measures from the Common Measures library arrive already mapped across frameworks.

The rest of the ISMS runs on the same data as every other programme:

  • Risks, threat sources and treatment plans in Operate, with an approval workflow and a yearly review.
  • Policies and procedures in Documents, with approvers, numbered revisions and a review date.
  • Records, audits (Internal, External or Certification), issues and corrective actions in Assure.

Health is computed from what controls and tasks actually do and rolls up to each requirement, so the ISO 27001 view and the NIS2 view read the same underlying work.

How Acuna GRC handles it

Acuna GRC is a GRC platform that runs an ISMS as one programme among others, alongside data privacy, business impact analysis, supplier risk and enterprise risk, all on one set of data.

Sources

  1. ISO/IEC 27001:2022, clauses 4 to 10 and Annex A
  2. Directive (EU) 2022/2555 (NIS2), Article 21

This page explains the rules in general terms and is not legal advice.

Frequently asked

Is an ISMS the same thing as ISO 27001?

No. ISO/IEC 27001 is the standard that sets the requirements for an ISMS. The ISMS is the management system itself: your policies, roles, risk decisions, controls and reviews. Certification shows that your ISMS meets the standard.

Can a GRC platform replace an ISMS?

No. A platform holds and connects the ISMS records and shows whether controls run, but the ISMS is the way people govern information security. The decisions, approvals and reviews still have to happen.

Should we start with ISO 27001 or with a full GRC programme?

Most organisations start with the obligation they face first, often ISO 27001. Building it on a structure that can take further frameworks avoids redoing the work when NIS2, DORA, SOC 2 or a privacy programme follows.

See how Acuna GRC runs this.

Tell us your frameworks and your team. We show you how Acuna GRC runs the program.

Hosted in Switzerland, the EU or the US