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.

CategoryCodeThe question it asksWhen it's in scope
Security (Common Criteria)CC1–CC9Is information and systems protected against unauthorized access, disclosure, and damage?Always. It is the price of entry.
AvailabilityA1.1–A1.3Is the system available for operation and use as committed or agreed?You sell uptime, SLAs, or your downtime hurts customers directly.
Processing IntegrityPI1.1–PI1.5Is processing complete, valid, accurate, timely and authorized?Outputs are consumed directly: payments, payroll, billing, data transformation.
ConfidentialityC1.1–C1.2Is information designated confidential protected through its lifecycle?You hold customer business data under contract (IP, financials, customer lists).
PrivacyP1–P8Is 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

SeriesThemeWhat gets tested
CC1Control environmentCode of conduct and acknowledgements, board/independent oversight, org chart, hiring standards, background checks, performance reviews, accountability for deviations
CC2Communication & informationPolicies written and communicated, internal reporting channels, agreements with external parties (DPAs, security addenda), quality of information used to run controls
CC3Risk assessmentDocumented risk assessment with objectives, fraud risk considered, identification of changes (new products, vendors, acquisitions) that affect risk
CC4Monitoring activitiesOngoing evaluations, internal audit or control self-assessments, remediation tracking, communicating deficiencies to those responsible
CC5Control activitiesPolicies translated into actual controls, technology general controls, and the selection/development of controls that address risk
CC6Logical & physical accessThe biggest series (8 criteria): provisioning, authentication, MFA, least privilege, encryption, access removal, physical access to facilities, asset disposal
CC7System operationsVulnerability and configuration monitoring, anomaly detection, incident evaluation and response, incident logging, recovery
CC8Change managementChange authorization, design and testing before deployment, approval, segregation of duties, emergency change path
CC9Risk mitigationBusiness disruption risk (BCDR), vendor and business-partner risk assessment, mitigation of identified threats
Roughly a third of the Common Criteria are not technical. CC1 through CC5 are governance, people, risk and communication. A company that hardens its AWS account and neglects board minutes, background checks and signed policy acknowledgements will fail on the paperwork series β€” which is the single most common surprise for engineering-led organisations.

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:

REQUIREMENT (criteria) AICPA's outcome β€” you don't choose these, only which categories apply CONTROL What you do: policy, process, or technical safeguard TEST How the auditor verifies it: inquiry, inspection, observation, reperformance EVIDENCE The artifact sampled: ticket, screenshot, log, signed policy, training record POINT OF FOCUS β€” a suggestion, never a requirement one requirement may need many controls one control may satisfy many requirements

A worked example, in the real language of a report:

LayerExample
RequirementCC6.2 β€” before issuing credentials, register and authorize new users; remove credentials when access is no longer authorized.
ControlAC-08: when personnel leave or no longer need access, system access is removed.
TestCompare each sampled termination date against the timestamp their accounts were disabled, per HR and IdP records.
EvidenceOffboarding 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.
Points of focus are not requirements β€” but they are how your auditor thinks. If a point of focus describes something you don't do, you don't automatically fail; you need an alternative control that achieves the same outcome, and you need to be able to explain it. What you cannot do is claim the requirement is met while your description silently contradicts the outcome it names.

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?

Further Reading