The Trust Services Principles are the criteria SOC 2 uses to evaluate a service organisation’s controls. They cover security, availability, processing integrity, confidentiality, and privacy, and each organisation must determine which principles actually apply to the services and data it handles.
What the Trust Services Principles measure
The Trust Services Principles are not a generic quality label, they are the criteria used to evaluate whether a service organisation’s controls are designed and operating to support specific assurance outcomes. In practice, they turn broad promises about security or availability into testable control expectations that can be scoped to the services and data the organisation actually handles.
Because the principles are applied in a report context, the real question is not simply whether an organisation “has security controls”, but whether those controls are relevant to the trust outcomes being claimed. That is why scope, boundaries, and carve-outs matter as much as the control set itself.
How the five principles differ
The five principles cover distinct assurance concerns: security is the baseline protection principle, availability addresses whether the service is resilient enough to be usable, processing integrity concerns whether processing is complete, valid, accurate, timely, and authorised, confidentiality protects information designated as confidential, and privacy addresses the handling of personal information according to stated commitments and applicable requirements.
These principles often overlap in implementation, but they are not interchangeable. A control that supports access restriction may help security and confidentiality, while logging and reconciliation may support both security and processing integrity. Organisations need to identify which principles are in scope for the service, rather than assuming every principle always applies.
For readers comparing assurance models, the AICPA’s SOC 2 Trust Services Criteria is the authoritative reference for the criteria themselves, while NHIMG’s SOC 2 Guide helps translate those principles into scoping and evidence expectations.
Scope, carve-outs, and what auditors test
The practical meaning of the Trust Services Principles changes with scope. A service organisation may not need every principle for every service, but once a principle is claimed, the controls, evidence, and operating effectiveness must support it consistently across the in-scope environment.
That means subservice providers, customer responsibilities, and system boundaries must be described clearly. If a service relies on external infrastructure, shared platforms, or customer-managed configuration, the report has to make clear where the organisation’s controls stop and where complementary controls begin.
NHIMG’s How to Read a SOC 2 Report Guide is useful here because it explains how scope, exceptions, bridge letters, and complementary user entity controls affect what the principles actually mean in a vendor report.
Why these principles matter to buyers and operators
For buyers, the Trust Services Principles are a way to compare vendors on the controls that matter for a particular service relationship, not a guarantee of absolute security. A report can be strong for one principle and weak or out of scope for another, so the reader should align the principles to the actual business and data risk.
For operators, the principles provide a common language for control design, evidence collection, and audit preparation. They also force a governance decision: which commitments the organisation is willing to make, which services are in scope, and which control failures would invalidate the assurance story.
When that governance needs to be translated into a readiness programme, NHIMG’s SOC 2 Readiness Checklist is a practical companion because it ties the principles to scope, control evidence, and preparation work.
Risk and Threat Considerations
The main risk is overclaiming. If an organisation scopes the wrong principles, omits material dependencies, or treats policy language as proof of operating control, the resulting report can mislead customers and create a false sense of assurance. The threat angle is that attackers, control gaps, or weak third-party dependencies are easiest to exploit where the control story is broad but the evidence is thin.
Failure mechanism: A service organisation may present a principle as covered while the underlying control is incomplete, inconsistently operated, or dependent on an unmanaged upstream provider. That gap can surface as an audit exception, a failed customer review, or a real compromise that was not visible in the assurance narrative.
Impact: The result can be loss of trust, deal friction, contract failure, and in the worst case, customer exposure through broken confidentiality, availability, processing integrity, or privacy controls.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
SOC 2 (AICPA) provides the primary governance reference for this term.
| Framework | Control / Reference | Relevance |
|---|---|---|
| SOC 2 (AICPA) | CC6.1 — Logical Access Security Software, Infrastructure, and Data | Trust Services Principles are the criteria behind SOC 2 control evaluation. |
| CC3.1 — Risk Assessment | Scoping which principles apply depends on the service, data, and risk profile. | |
| CC1.2 — Commitment to Integrity and Ethical Values | Principle claims depend on governance, accountability, and accurate assurance statements. | |
| Recommendation — Align in-scope controls to the applicable Trust Services Criteria and retain evidence that proves they operate effectively. Define scope from the actual service and data risk profile before asserting which principles apply. Assign ownership for the assurance story and require truthful, supportable control claims. | ||
Practitioner Guidance
Why practitioners should care: The Trust Services Principles should be treated as a scoping and evidence discipline, not a branding exercise. Teams should decide which principles are truly applicable before they build the report narrative, because that decision drives what controls, logs, exceptions, and customer responsibilities must be demonstrable.
Governance implication: Ownership must sit with the service team that can actually prove control operation, while legal, security, and compliance should align on the commitments being made to customers. If the organisation cannot evidence a principle, it should not be presented as in scope without careful qualification.
Related resources from NHI Mgmt Group
- Why do zero trust and secure-by-design principles matter when agencies connect many services, users, and third parties?
- How do organisations keep AI agent access aligned with Zero Trust principles?
- Why do sustained DNS anomalies matter for IAM and trust services?
- Why does third-party verification matter more than self-attestation for trust services?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 1, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org