Home / Glossary
Glossary, read 12 Nov 2026
40 SOC 2 terms, each defined with a sourced example
Trust Services CriteriaRead the guides
All 40 terms
| Term | Definition |
|---|---|
| Access review | An access review is a recurring check that every account and every privilege still matches a business need |
| Attestation engagement | An attestation engagement is a CPA engagement in which the firm examines a subject, such as controls, against criteria and reports a conclusion on management's assertions |
| Automated evidence collection | Automated evidence collection means pulling control evidence such as configurations, user lists and logs from systems by script or integration instead of by screenshot |
| Bridge letter | A bridge letter is a statement from a company's management, not its auditor, that covers the gap between a SOC report's period end date and the date of the letter |
| Business continuity plan | NIST SP 800-34 Rev. 1 defines a business continuity plan as documented instructions describing how an organization's mission and business processes will be sustained |
| Carve-out method | Under the carve-out method, a SOC report describes the subservice organization's services but leaves its controls out of the system description and the auditor's testing |
| Change management | Change management is the controlled process for proposing, approving, testing and releasing changes to systems |
| Common Criteria | The common criteria are the criteria of the Security category in the 2017 Trust Services Criteria |
| Complementary user entity controls | Complementary user entity controls (CUECs) are controls that a service organization's SOC report expects its customers to operate |
| Continuous control monitoring | Continuous control monitoring is the ongoing checking of whether controls are still operating between audits |
| Control activity | A control activity is a specific, repeatable action a company performs to meet a criterion, such as approving a change before release or reviewing user access |
| Control exception | A control exception is a deviation an auditor records when a control was not suitably designed or did not operate as described |
| Evidence sampling | Evidence sampling is the auditor testing a selection of occurrences of a control rather than every one |
| Gap analysis | A gap analysis compares each Trust Services Criterion you plan to be tested on with the control you operate today and records where the two differ |
| Incident response plan | NIST defines an incident response plan as the documentation of a predetermined set of instructions or procedures to detect |
| Inclusive method | Under the inclusive method, a SOC report includes the subservice organization's controls in the system description and the auditor's testing |
| Information security policy | An information security policy states what the organization requires and why |
| Management assertion | A management assertion is the letter in which a service organization's leadership states that its system description is fairly presented |
| Observation window | The observation window is the period a SOC 2 examination covers when it tests whether controls operated, not only whether they were designed |
| Penetration test | A penetration test is security testing in which assessors mimic real-world attacks to find ways around the security features of an application, system or network |
| Points of focus | Points of focus are the guidance attached to the criteria in the AICPA's 2017 Trust Services Criteria |
| Population list | A population list is the complete set of occurrences of a control during the audit period, from which an auditor selects samples |
| Qualified opinion | A qualified opinion is the auditor's statement that a SOC report is sound except for stated matters |
| Readiness assessment | A readiness assessment is a pre-audit review of your controls against the Trust Services Criteria, done before the formal examination starts |
| Risk assessment | A risk assessment is a systematic examination of risk using disciplined processes, methods and tools (NIST SP 800-30 Rev. 1, via CNSSI 4009) |
| Segregation of duties | Segregation of duties, which NIST calls separation of duties, means no one person holds enough privilege to misuse a system alone |
| Service auditor | The service auditor is the CPA firm that examines a service organization's controls and issues the SOC report |
| Service organization | A service organization is a company that provides a service or system to other companies, and whose controls a SOC report describes |
| SOC 1 report | A SOC 1 report is an examination of controls at a service organization that are likely to be relevant to user entities' internal control over financial reporting |
| SOC 3 report | A SOC 3 report covers the same five Trust Services Criteria categories as SOC 2 with less detail |
| SOC for Cybersecurity | SOC for Cybersecurity is an AICPA engagement in which a CPA reports on an organization's enterprise-wide cybersecurity risk management program |
| SSAE 18 | SSAE No. 18, Attestation Standards: Clarification and Recodification, is the AICPA standard that SOC engagements follow |
| Subservice organization | A subservice organization is a vendor whose controls |
| System description | The system description is management's written account of the service being examined, and it is Section 3 of a SOC 2 report |
| Test of controls | A test of controls is the auditor's procedure to check whether a control was designed properly and, in Type 2, whether it worked |
| Trust Services Criteria | The 2017 Trust Services Criteria, with revised points of focus issued in 2022, are the AICPA control criteria a SOC 2 examination is measured against |
| Unqualified opinion | An unqualified opinion is the clean result of a SOC examination: the auditor has no reservations |
| User entity | A user entity is a customer organization that uses a service organization's system and relies on its SOC report |
| Vendor management | Vendor management is the process of assessing and monitoring the third parties a company depends on |
| Vulnerability scan | A vulnerability scan is an automated technique that identifies hosts |
Sources
- AICPA 2017 Trust Services Criteria resource page, read 12 Nov 2026
- Schellman: What a SOC audit costs, read 12 Nov 2026
- AICPA SOC 2 reporting guide, product page, read 12 Nov 2026
- Schellman: How to read your SOC report, read 12 Nov 2026
- AICPA SOC suite of services, read 12 Nov 2026
- Schellman: Using a vendor's SOC 2 report, read 12 Nov 2026
- Schellman: Subservice organizations versus vendors, read 12 Nov 2026
- Schellman: Carve-out versus inclusive method, read 12 Nov 2026
- Google Cloud SOC 2 compliance page, read 12 Nov 2026
- Schellman: Qualified opinion in a SOC report, read 12 Nov 2026
- Schellman: Which SOC opinion do you want, read 12 Nov 2026
- Schellman: Addressing testing exceptions in SOC, read 12 Nov 2026
- NIST CSRC glossary: sampling, read 12 Nov 2026
- Schellman: What SOC reports are, read 12 Nov 2026
- NIST CSRC glossary, gap analysis, read 12 Nov 2026
- AICPA SOC 3 page, read 12 Nov 2026
- AICPA SOC 1 page, read 12 Nov 2026
- AICPA SOC for Cybersecurity page, read 12 Nov 2026
- AWS SOC compliance page, read 12 Nov 2026
- NIST SP 800-115, read 12 Nov 2026
- NIST CSRC glossary, continuous monitoring, read 12 Nov 2026
- Journal of Accountancy, AICPA guides peer reviewers to address SOC 2 risks, read 12 Nov 2026
- NIST SP 800-53 Rev. 5 control catalog (OSCAL), read 12 Nov 2026
- NIST CSRC glossary, security policy, read 12 Nov 2026
- NIST CSRC glossary, incident response plan, read 12 Nov 2026
- NIST CSRC glossary, business continuity plan, read 12 Nov 2026
Last reviewed 12 Nov 2026.