Not necessarily. A SOC 2 report describes a defined system and a defined period, so an AI feature is covered only if it sits inside that description. Ask the vendor whether the AI feature, its model providers and its data flows are in scope, then read the report to confirm.
What the report is
SOC 2 reports are issued by independent CPA firms. The AICPA lists the criteria categories as security, availability, processing integrity, confidentiality and privacy. The report states which of those the examination addressed. It is an attestation by an auditor, not a certification, and it speaks only about what the vendor described.
Why AI features can fall outside
AI features are often added after the report's system description was written. A new assistant, a new model provider or a new data pipeline may not be mentioned. The control environment around it may be strong, or may not have been examined at all. The report cannot tell you which unless you read the scope.
What to ask
| Question | Why |
|---|---|
| Is the AI feature named in the system description? | If it is not, it was not described |
| Which model providers are used, and are they listed as subservice organizations? | Data may leave the vendor |
| Which criteria categories are in scope? | Confidentiality and privacy matter for prompts and outputs |
| What period does the report cover, and does it include the date the feature launched? | A feature launched after the period is not tested |
| Are there exceptions or qualifications noted? | Auditors flag problems there |
| What are the complementary user entity controls? | They are your responsibilities |
How to read it
Open the system description first. Search for the feature name and the model provider. Then read the section on subservice organizations. Finally read the list of exceptions in the testing results. Five minutes with those three sections tells you more than the cover page.
If the feature is out of scope, that is not a reason to refuse it. It is a reason to ask other questions: how data is handled, whether prompts are stored or used for training, how access is controlled, and what contractual terms apply. A short written answer from the vendor, signed off by someone accountable, can fill the gap for a low-risk use.
What to avoid saying
Do not tell your own customers that a vendor's AI feature is "SOC 2 compliant". SOC 2 is not a status a feature holds. Say what the report covers: "Our vendor's SOC 2 report for the period X to Y includes this feature in its system description." If you cannot say that truthfully, say less.
Record the decision
File the report, the scope check and the vendor's written answers with the vendor's entry in your register. Review when the report renews.
Try it yourself
Click through it at your own pace, or open it full screen.
Pick the SOC 2 mapping and see which controls map to which evidence, then compare with what your vendor can show.
Quick check
Is a SOC 2 report the same as a certification?
No. It is an attestation report from an independent auditor on a described system.
What if the report predates the AI feature?
Ask for a written control description for the feature and treat it as unexamined until a later report covers it.
Safeguard offers compliance and evidence automation to help organise this kind of review, and the free scan covers the code side.
Sources
Last reviewed: 19 October 2026.
