The Trust Services Criteria
Lesson 2: The Trust Services Criteria
The Trust Services Criteria (TSC) are the AICPA's control criteria β established by its Assurance Services Executive Committee, modelled on the COSO internal-control framework, and mappable to NIST SP 800-53, ISO 27001 and GDPR. They come in five categories. Only one is mandatory.
| Category | Code | The question it asks | When it's in scope |
|---|---|---|---|
| Security (Common Criteria) | CC1βCC9 | Is information and systems protected against unauthorized access, disclosure, and damage? | Always. It is the price of entry. |
| Availability | A1.1βA1.3 | Is the system available for operation and use as committed or agreed? | You sell uptime, SLAs, or your downtime hurts customers directly. |
| Processing Integrity | PI1.1βPI1.5 | Is processing complete, valid, accurate, timely and authorized? | Outputs are consumed directly: payments, payroll, billing, data transformation. |
| Confidentiality | C1.1βC1.2 | Is information designated confidential protected through its lifecycle? | You hold customer business data under contract (IP, financials, customer lists). |
| Privacy | P1βP8 | Is personal information collected, used, retained, disclosed and disposed of per policy and notice? | Rarely chosen. Adds large scope; usually satisfied via other means unless you're consumer-facing or healthcare-adjacent. |
The arithmetic that matters: the Common Criteria contain 33 criteria (CC1.1 through CC9.2, the only ones with decimal numbering that people memorise), and adding all five categories takes you to roughly 61 requirements. A Security + Availability + Confidentiality scope is around 38. That number drives your control count, your auditor's fee, and your evidence burden β which is exactly why scoping is an economic decision, not just a technical one.
The nine Common Criteria, and what an auditor actually looks at
| Series | Theme | What gets tested |
|---|---|---|
| CC1 | Control environment | Code of conduct and acknowledgements, board/independent oversight, org chart, hiring standards, background checks, performance reviews, accountability for deviations |
| CC2 | Communication & information | Policies written and communicated, internal reporting channels, agreements with external parties (DPAs, security addenda), quality of information used to run controls |
| CC3 | Risk assessment | Documented risk assessment with objectives, fraud risk considered, identification of changes (new products, vendors, acquisitions) that affect risk |
| CC4 | Monitoring activities | Ongoing evaluations, internal audit or control self-assessments, remediation tracking, communicating deficiencies to those responsible |
| CC5 | Control activities | Policies translated into actual controls, technology general controls, and the selection/development of controls that address risk |
| CC6 | Logical & physical access | The biggest series (8 criteria): provisioning, authentication, MFA, least privilege, encryption, access removal, physical access to facilities, asset disposal |
| CC7 | System operations | Vulnerability and configuration monitoring, anomaly detection, incident evaluation and response, incident logging, recovery |
| CC8 | Change management | Change authorization, design and testing before deployment, approval, segregation of duties, emergency change path |
| CC9 | Risk mitigation | Business disruption risk (BCDR), vendor and business-partner risk assessment, mitigation of identified threats |
The mental model that solves 80% of confusion
Five words get used interchangeably in conversation and mean completely different things in an audit. Learn the ladder:
A worked example, in the real language of a report:
| Layer | Example |
|---|---|
| Requirement | CC6.2 β before issuing credentials, register and authorize new users; remove credentials when access is no longer authorized. |
| Control | AC-08: when personnel leave or no longer need access, system access is removed. |
| Test | Compare each sampled termination date against the timestamp their accounts were disabled, per HR and IdP records. |
| Evidence | Offboarding tickets for terminations during the review period, showing approver, SLA target and disable timestamps. |
Two structural facts fall out of this ladder, and they should shape your whole program:
- Controls outnumber requirements, and tests outnumber controls. A realistic Security + Availability + Confidentiality control set runs 60β100 controls with 1.5β2 tests each β an illustrative set with 82 controls carried 146 tests, where 61 of the 82 served more than one requirement.
- The work is not implementing controls, it is producing evidence for the whole period. One formal risk assessment can satisfy eight different requirements; the βpolicies and proceduresβ requirement is typically supported by two dozen separate policy controls. The asymmetry means your effort belongs in making evidence generation automatic, not in adding more controls.
Why no two reports look alike
Because the criteria specify outcomes and the AICPA explicitly avoids mandating specific controls, two companies with the same architecture can produce very different reports: one may satisfy CC6.1 with a full-blown PAM deployment, another with SSO plus quarterly access reviews and scoped IAM roles. Both can be unqualified. The auditor's job is to judge suitability for your risk, not conformance to a template β which is also why βwhich controls do I need?β has no universal answer, and why copying another company's control matrix usually produces controls that don't match your system description.
π§ Knowledge Check
1. Which Trust Services Category is mandatory in every SOC 2 examination?
2. Your auditor finds that a point of focus under CC6.4 is not addressed by your controls. What is the correct conclusion?
3. Which series covers change management, including testing and approval before deployment?