Skip to content
SOC 2 Compliance Software

Home / Glossary / Evidence sampling

Glossary, read 12 Nov 2026

Evidence sampling in a SOC 2 examination, defined with a sourced example

All termsRead the guides

The definition of Evidence sampling

NIST's glossary entry, sourced to SP 800-55 Volume 1, defines sampling as "the process of taking samples of something for the purpose of analysis." In a SOC 2 Type 2, the auditor applies that to controls that repeat, such as access removals, change approvals and training completions during the period, instead of re-performing every instance.

The mistake is preparing only the evidence you expect to be picked. Schellman's scoping article says that in a Type 2, you need to provide sufficient evidence for all samples the auditor may select, which means the process must have been in place for the whole period. A control you started in month three has no samples from months one and two.

Sampling interacts with exceptions. Schellman says that when testing finds a single exception, auditors can sometimes increase the sample size to see whether further deviations exist, and if none turn up the one exception stays noted while the control may be deemed effective. A-LIGN describes the same practice. Do not assume a miss ends the test.

A sourced example

Schellman's SOC 1 article answers a common question about an exception in a sample: can more testing show it was not pervasive? Yes, in some instances where testing finds a single exception in the original sample, auditors can increase the sample size. If the extra sample finds nothing else, the single exception stays in the report, but the control may be deemed operating effectively. Schellman: Managing exceptions in SOC 1, read 12 Nov 2026.

Sources

  1. Schellman: Managing exceptions in SOC 1, read 12 Nov 2026
  2. NIST CSRC glossary: sampling, read 12 Nov 2026
  3. Schellman: How to scope a SOC 2 audit, read 12 Nov 2026
  4. A-LIGN: Can you fail a SOC 2 examination, read 12 Nov 2026

Last reviewed 12 Nov 2026.