Home › Resources › Glossary › Control

Resources · Glossary

What is a control in audit and compliance?

In shortA control is a measure that reduces a risk or meets a requirement. It can be a policy, a process, a technical setting or a physical safeguard. Auditors test two things about each control: whether it is designed to address the risk, and whether it actually operated as designed during the period under review.

What does a control mean in an audit?

A control exists because of a risk or a requirement. 'Review user access every quarter' is a control; the risk is that people keep access they no longer need.

A good control statement says who does what, how often, and what record it leaves. Without the record, an auditor cannot confirm the control worked, however sound it is.

What are the types of control?

BeforePreventive

Stops a problem from happening. Example: multi-factor authentication.

During or afterDetective

Finds a problem that has happened. Example: a log alert or an access review.

AfterCorrective

Limits the damage and restores normal operation. Example: restoring from backup.

What does a well-written control look like?

A control for removing access when people leave.

ItemWhat it looks like
StatementIT operations disables all accounts of a leaver on their last working day.
Risk addressedFormer staff keep access to systems and data.
TypePreventive
OwnerIT operations lead
EvidenceLeaver ticket with the time each account was disabled

This is an illustration written for this page, not a customer record.

How do frameworks organise controls?

FrameworkWhereWhat it asks for
ISO 27001Annex A93 controls in four themes: organisational, people, physical and technological. You select those your risks need.
SOC 2CC5Control activities are selected and developed to mitigate risks, then deployed through policies and procedures.
NIST 800-53Rev. 5A catalogue of security and privacy controls arranged in 20 families.
NIST CSF 2.0Protect, DetectOutcomes rather than controls; you choose controls that achieve each outcome.

References are to the current editions listed under Sources. Check the edition your auditor is using.

What makes a control weak?

01

No frequency

'Access is reviewed' does not say how often, so it cannot be tested.

Instead: state who does it and how often.

02

No evidence

The control runs but leaves nothing behind.

Instead: decide the record the control produces before it starts.

03

Copied, not chosen

Controls taken from a template address risks you do not have.

Instead: tie each control to a risk or a requirement.

How does QULDEX handle this?

Pre-mapped Control Library

Controls arrive already mapped across frameworks, each with an owner and a status.

See the module

Control: common questions

What is the difference between a control and a policy?

A policy states what the organisation intends. A control is a specific measure that carries the policy out and can be tested.

How many controls does ISO 27001 have?

Annex A of ISO/IEC 27001:2022 lists 93 controls. You do not have to implement all of them, but you must consider each one and justify your choices in the Statement of Applicability.

What is a compensating control?

An alternative measure used when the expected control cannot be applied. It must address the same risk to a comparable degree, and the reason should be documented.

Every control with an owner, a status and its evidence

Controls, evidence, findings and corrective actions in one audit workspace.

Schedule
Book a Demo