Home › Resources › Glossary › Control Testing

Resources · Glossary

What is control testing? Methods, steps and examples

In shortControl testing is the work an auditor does to confirm that a control is designed to address its risk and that it operated as designed during the period under review. The auditor selects a sample, examines the evidence for each item, and records whether the control worked, with any exceptions.

What does control testing involve?

Testing answers two separate questions. Design: if this control were carried out as written, would it deal with the risk? Operation: was it actually carried out, every time it should have been?

A control can be well designed and still fail in operation, for example an access review that is specified quarterly but was done only twice in the year.

What are the methods of control testing?

Weakest aloneInquiry and observation

Asking people how the control works, and watching it being done.

Most commonInspection

Examining records such as tickets, logs, approvals and exports.

StrongestRe-performance

The auditor carries out the control independently and compares the result.

What does a control test look like?

Testing the control 'accounts are disabled on a leaver's last working day'.

ItemWhat it looks like
PopulationAll 84 leavers between 1 Apr and 30 Sep 2026, from the HR report
Sample25 leavers selected at random
ProcedureFor each, compare the last working day with the time the account was disabled
Result22 on time, 3 late: three exceptions
ConclusionControl not operating effectively; finding raised

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

What do frameworks say about testing controls?

FrameworkWhereWhat it asks for
ISO 27001Clause 9.1The organisation evaluates information security performance and the effectiveness of the management system.
ISO 27001Annex A 5.35The approach to information security and its implementation is independently reviewed at planned intervals.
SOC 2Type 2 reportThe auditor tests the operating effectiveness of controls over the period and reports the tests and results.
NIST 800-53SP 800-53AAssessment procedures use three methods: examine, interview and test.

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

What weakens a control test?

01

Sample chosen by the auditee

The team picks the examples it wants to show.

Instead: the auditor selects the sample from the full population.

02

Population not confirmed

The list sampled from is incomplete.

Instead: check the population is complete before sampling.

03

Inquiry alone

The auditor relies on what people say.

Instead: support interviews with records.

How does QULDEX handle this?

Audit Workspace

Plan, test, record findings and report in eight phases, with every step recorded against the audit.

See the module

Control Testing: common questions

What is the difference between a test of design and a test of operating effectiveness?

A test of design asks whether the control, as written, would address the risk. A test of operating effectiveness asks whether it was actually performed as written over the period.

How large should a test sample be?

It depends on how often the control runs, the risk, and the confidence needed. Document the population, the sample size and how items were chosen.

What is an exception?

A sampled item where the control did not operate as designed. The auditor evaluates exceptions to decide whether the control failed.

Test, record the result and raise the finding in one place

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

Schedule
Book a Demo