A test of controls is a procedure the auditor performs to determine whether a control operated as described. The four techniques are inquiry, observation, inspection and reperformance. When the evidence is a list or report from your systems, the auditor must also establish that it is complete and accurate. That evidence is called information produced by the entity (IPE). Information that a control itself relies on is called information used in the control (IUC).
The same techniques are used in SOC 1 and SOC 2 examinations.
Key takeaways
- Inquiry alone is never sufficient. It is combined with at least one other technique.
- Sampling is used when a control operates many times. The sample comes from the full population.
- Expect the question “how was this list generated?” for every population.
- Preparing IPE properly is the simplest way to speed up fieldwork.
The four techniques
| Technique | Example |
|---|---|
| Inquiry | Asking the engineering lead how changes are approved |
| Observation | Watching a deployment pipeline block an unapproved merge |
| Inspection | Examining tickets, approvals, configurations, logs |
| Reperformance | Independently re-running a reconciliation or access comparison |
Sampling
For a control that operates per event, such as each new hire or each production change, the auditor requests the complete population for the period and selects items. Sample size depends on how often the control operates and the assessed risk. For periodic controls, such as quarterly reviews, the auditor may examine each occurrence or a selection. Automated controls can often be tested once, provided change management over the system is effective.
IPE: proving a list is complete and accurate
A list of terminated employees, of production changes, or of users with administrator rights is IPE. To rely on it, the auditor looks for:
- The source system and who ran the report.
- The query, filter or parameters used.
- Date and time of generation.
- A record count or other check that nothing was dropped.
- That the output was not edited after export.
A screenshot showing the query and result count, or a screen-share while the report is run, usually satisfies this.
IUC: information your own control relies on
If a manager performs an access review using an exported user list, the review is only as good as the list. The control owner should be able to show how they knew the list was complete. See user access reviews for SOC 2.
How to prepare
- For each population the auditor will ask for, document how it is produced.
- Export from the system of record, not from a maintained spreadsheet.
- Keep exports unaltered, with timestamps.
- Store populations and samples together per control. See audit evidence management.
Frequently asked questions
Why won’t the auditor accept a screenshot?
A screenshot of one record shows one record. It does not show the population or how it was selected.
Are tests listed in the report?
Yes, in a Type 2 report, with results. See what is SOC 2 Type 2.
What happens when a sample item fails?
It is reported as an exception. See qualified vs unqualified opinions.
Sources & further reading
AICPA AT-C sections 205 and 320; AICPA SOC 2 Guide.
Related: Audit methodology, SOC 2 audit timeline.
Work with a licensed CPA firm
Auditsuisse Assurance NA PC is a licensed US CPA firm enrolled in the AICPA Peer Review Program. See our published SOC 2 fees or book a scoping call.