Skip to content
SOC 2 Compliance Software

Home / Glossary / Control activity

Glossary, read 12 Nov 2026

Control activity in a SOC 2 examination, defined with a sourced example

All termsRead the guides

The definition of Control activity

Schellman's walkthrough says Section 4 lists the specific controls in scope, and that a Type 2 report adds the types of testing performed (inquiry, observation and inspection) and the result for each test. This is the section customers' security teams read first when they care about a specific area, such as access or change management.

Most failures come from wording. A control written as "access is reviewed regularly" cannot be tested, while one that promises a quarterly review sets a bar you must clear every quarter. Schellman's exception articles show the pattern: a vendor management program that says subservice organizations are assessed at least annually, and a review that was never completed, produces an exception.

Auditors compare the control as written, the policy behind it and the system as configured. Schellman's SOC 1 example has a control stating a job runs daily; if configuration shows weekly, the auditor checks the policy to decide whether the control or the configuration is wrong. Write controls to match practice, then document the practice.

A sourced example

Schellman's example of a stated control activity: a financial processing job is configured to run daily to support timely data processing. If the auditor inspects the job configuration and finds it set to weekly, the auditor then reads the policy. If the policy says daily, that is a design flaw; if the policy says weekly, the discrepancy must be discussed. Schellman: Managing exceptions in SOC 1, read 12 Nov 2026.

Sources

  1. Schellman: Managing exceptions in SOC 1, read 12 Nov 2026
  2. Schellman: How to read your SOC report, read 12 Nov 2026
  3. Schellman: Qualified opinion in a SOC report, read 12 Nov 2026

Last reviewed 12 Nov 2026.