SOC 2 vs ISO 27001 for AI Data Vendors: What They Actually Mean
A plain-language guide to what SOC 2 Type II and ISO 27001 certifications mean for AI data vendors, what they do and do not cover, and how to use them in procurement.

Why security certifications matter in AI data procurement
AI training data programs routinely handle proprietary model architectures, unreleased product data, consumer PII, sensitive audio and video, and in regulated industries, health records and financial documents. The AI data vendor becomes a data processor for all of this. Enterprise procurement teams increasingly require security certifications before any data moves -- and for good reason.
But certifications are not interchangeable. SOC 2 Type II and ISO 27001:2022 are the two most commonly required, and they test different things. Using them interchangeably -- or accepting one as a substitute for the other -- misses what each actually covers.
This guide explains what each certification tests, what it does not cover, and how to use both together in vendor evaluation.
What SOC 2 Type II actually tests
SOC 2 (Service Organization Control 2) is an attestation standard developed by the American Institute of CPAs (AICPA). It tests whether a service organization's controls meet the Trust Services Criteria -- a set of principles covering security, availability, processing integrity, confidentiality, and privacy. A Type II report covers a defined audit period (typically six to twelve months), not just a point-in-time snapshot.
The security principle -- Control Environment, Communication and Information, Risk Assessment, Monitoring of Controls, Control Activities -- is mandatory. The other four criteria (availability, processing integrity, confidentiality, privacy) are optional and chosen by the vendor. This means two vendors can both hold SOC 2 Type II reports with materially different scopes. One may have chosen only security; another may have included confidentiality and privacy, which is far more relevant for an AI data processor.
What SOC 2 does not test: it does not require specific technical controls, only that the controls a vendor describes are actually operating. A vendor can pass SOC 2 with relatively permissive controls if those controls are consistently applied. It is an evidence-based process test, not a technical security standard.
The SOC 2 report itself is confidential and not published. Vendors provide it under NDA. When requesting it, ask specifically: which Trust Services Criteria are covered, what is the audit period, and are there any qualified opinions (exceptions noted by the auditor).
What ISO 27001:2022 actually tests
ISO 27001 is an international standard (ISO/IEC 27001) for information security management systems (ISMS). The 2022 revision is the current version. Unlike SOC 2, ISO 27001 certification is publicly verifiable -- the vendor's certificate lists the scope, issuing body, and expiry date, and can be checked against the certifying body's registry.
ISO 27001 requires a vendor to design, implement, maintain, and continually improve a documented ISMS. The standard tests whether the management system is coherent and whether the controls in Annex A (93 controls in the 2022 version) are addressed. Certification is granted by an accredited third-party certification body and renewed on a three-year cycle with annual surveillance audits.
ISO 27001 is broader in scope than SOC 2 in some ways -- it covers physical security, supplier relationships, human resource security, and business continuity alongside technical controls. It is also more prescriptive about the management system itself. However, it does not prescribe specific technical implementations, so two ISO 27001-certified vendors can have meaningfully different actual security postures.
The scope statement on the certificate matters. A vendor may be ISO 27001-certified for a specific office location or service line, not their entire operation. Read the scope before assuming certification covers the service being procured.
Differences that matter for AI data procurement
SOC 2 Type II is US-market standard for B2B SaaS and data services. Most US enterprise procurement checklists require it. The Type II designation (vs Type I, which is point-in-time) is important: Type II proves that controls operated consistently over the audit period, not just that they existed on the day of the audit.
ISO 27001:2022 is the international equivalent and is the standard required by European enterprise procurement. For EU clients, it is typically the primary certification and may be required alongside a GDPR Data Processing Agreement rather than a SOC 2.
For AI data vendors specifically, the confidentiality and privacy Trust Services Criteria under SOC 2 -- and the equivalent data protection controls under ISO 27001 -- are the most operationally relevant. Ask: does the vendor's SOC 2 scope include confidentiality? Does their ISO 27001 scope include controls for data subject rights and cross-border transfers?
Neither certification tests AI-specific risks: model theft, training data poisoning, annotation manipulation, or inference attacks. Those are addressed by operational security practices and contractual terms, not by either certification alone.
How to use both certifications in vendor evaluation
Request both certifications for any enterprise AI data program. The combination of ISO 27001:2022 (ISMS management system) and SOC 2 Type II (process-level audit over time) provides the most complete picture available. For EU programs, also require a GDPR Data Processing Agreement with Standard Contractual Clauses (SCCs). For regulated industries, add the relevant overlay: HIPAA BAA for healthcare, CCPA service-provider addendum for California data, LGPD DPA for Brazil, POPIA DPA for South Africa.
When you receive the SOC 2 report (under NDA), look for qualified opinions -- sections where the auditor noted exceptions or deviations from stated controls. A clean report with no qualifications is meaningfully different from one with exceptions, even if both say 'Type II.' The number and nature of exceptions, and whether they were remediated during the audit period, matters.
For the ISO 27001 certificate, verify it directly with the issuing certification body before relying on it. Certificate forgery is rare but not unknown in the outsourcing market. The issuing body's registry is the authoritative source.
What certifications cannot tell you
Neither SOC 2 nor ISO 27001 tells you whether a vendor's annotators actually handle your data confidentially day to day. They tell you that a management system exists and was audited -- not that every annotator in a distributed workforce is following the procedures the management system describes. Physical endpoint controls, individual NDAs, and access logging are operational practices that certifications verify at the policy level, not the individual level.
Certifications do not cover subprocessors unless those subprocessors are explicitly included in scope. A vendor who uses a crowd-sourcing platform for some annotation tasks may be ISO 27001-certified for their internal operations while routing work through an uncertified third party. The subprocessor list is the document that closes this gap -- always request it.
Finally, certifications are backward-looking. An ISO 27001 certificate issued twelve months ago and a SOC 2 Type II report covering the period ending nine months ago are evidence of past compliance, not current posture. For high-risk programs, request the most recent penetration test executive summary and ask about significant security incidents since the last audit period.
Frequently asked questions
- Does Corpshore AI have SOC 2 Type II?
- Yes. Corpshore AI holds SOC 2 Type II certification. The full report is available under NDA to enterprise procurement teams. Contact info@corpshore.ai or request through the start-a-pilot form.
- Does Corpshore AI have ISO 27001?
- Yes. Corpshore AI holds ISO 27001:2022 certification. The certificate details scope and issuing body and can be provided to procurement teams.
- What is the difference between SOC 2 Type I and Type II?
- SOC 2 Type I is a point-in-time audit confirming that controls exist. Type II covers an audit period (typically six to twelve months) and confirms that controls operated consistently over that period. Type II is the meaningful standard for enterprise procurement.
- Is ISO 27001 or SOC 2 required for GDPR compliance?
- Neither is required by GDPR directly, but ISO 27001 and SOC 2 are commonly accepted as evidence of appropriate technical and organizational measures under GDPR Article 32. A GDPR-compliant data processor also needs a signed Data Processing Agreement and, for cross-border transfers, Standard Contractual Clauses or another approved transfer mechanism.
- What security documentation should I request from an AI data vendor?
- Request: SOC 2 Type II report (under NDA), ISO 27001:2022 certificate, GDPR DPA with SCCs, UK GDPR addendum if applicable, CCPA service-provider addendum, subprocessor list, penetration test executive summary, and security policy overview. For healthcare data, also request a HIPAA BAA.
Published by
Corpshore AI
https://corpshore.ai