Platform

What is the difference between a measure and a control in GRC?

Direct answer

A measure is a practice your organisation implements to address one or more requirements, such as reviewing access rights every quarter. A control is a verification activity with a frequency that checks the measure is working. A requirement is met by a measure, a measure is verified by a control, and one measure can address clauses in several frameworks.

A measure is a practice your organisation implements to address one or more requirements, such as reviewing access rights every quarter. A control is a verification activity with a frequency that checks the measure is working. In Acuna GRC the chain runs requirement, measure, control, task: a requirement is met by a measure, a measure is verified by a control, and a control is performed through recurring tasks. One measure can address clauses in several frameworks, and each control is judged by record completion, a target value or a checklist. Health starts at the control and rolls up to the measure and the requirement.

Why separate the practice from the check?

Frameworks ask for two different things. First, that a practice is in place: an access policy, a backup routine, a supplier review. Second, that you know it works: ISO/IEC 27001:2022 requires you to monitor and measure the performance of the ISMS (clause 9.1), and a SOC 2 Type 2 report gives an opinion on whether controls operated effectively throughout a period.

Keeping the measure and the control apart serves both:

  • The measure is written once and linked to every requirement it meets, in ISO 27001, NIS2, SOC 2 or any other framework.
  • The control carries what proves operation: an owner, a frequency, a pass criterion and the evidence it produces.
  • When a check fails, you see which practice is weak and every requirement that depends on it.

Without the split, organisations tend to either document practices nobody verifies, or run checks that are not tied to any requirement.

What does a well-defined control need?

A control is only useful if anyone can tell whether it passed. It needs:

  • An owner who performs or signs it.
  • A frequency, such as monthly or quarterly.
  • A clear test: what is checked, and what counts as a pass.
  • The evidence each run produces, kept with a date.
  • What happens on failure: an issue, a corrective action, or an escalation.

In Acuna GRC, the Add Control wizard walks through Basics, Effectiveness, Target or Checklist, Schedule, Related and Review. Each control is judged in one of three ways: Record Completion, a Target Value (entered by hand, taken from a KPI or pulled by a connector), or a Checklist that is answered and signed item by item, which creates one record with a PDF of the signed run. A due control appears in its owner’s My Actions.

What mistakes blur measures and controls?

  • Writing a measure as a one-off project, with no control to check it keeps running.
  • Controls with no frequency, which are never due and so never fail.
  • Checks that test whether a document exists rather than whether the practice happens.
  • Creating one measure per framework for the same practice, which splits the evidence.
  • Attaching evidence to the framework instead of the control, so the same proof is collected several times.

How does Acuna GRC use the distinction to compute health?

Take a quarterly review of access rights. In Implement, the measure "Access rights are reviewed every quarter" is linked to the access control requirements of each framework you run. A control with a quarterly schedule verifies it, judged by record completion, and a recurring task carries out the review and files the record when it is done.

Health starts at the control, from whether it ran on time and from its tasks. A measure’s health combines three dimensions: design, operating (its linked controls) and documentation (its linked documents being current), and the weakest one wins. Requirement health rolls up from the linked measures and controls on the same worse-wins rule. The Health tab on a control shows which dimension drags the score down. See how control health works and how measures and controls link to requirements.

How Acuna GRC handles it

Sources

  1. ISO/IEC 27001:2022, clauses 6.1.3 and 9.1, and Annex A

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

Frequently asked

Is an ISO 27001 Annex A control a measure or a control in this sense?

In Acuna GRC, each Annex A control is a requirement of the ISO 27001 framework you adopted. The practice you put in place to meet it is the measure, and the periodic check that the practice works is the control.

Can one control verify several measures?

Yes. A control is linked to the measures it verifies, and a measure can have several controls. The control’s health then feeds the operating dimension of each linked measure.

Who owns the measure, and who owns the control?

Often different people. The measure owner is accountable for the practice, and the control owner performs or signs the check. Keeping them apart avoids people verifying their own work.

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