Home / Glossary / Vendor management
Glossary, read 12 Nov 2026
Vendor management in a SOC 2 examination, defined with a sourced example
The definition of Vendor management
In a SOC 2 file the evidence is a vendor list, a risk tier for each vendor, and proof you looked at the critical ones. For a cloud provider that proof is often the provider's own SOC 2 report: you read it, note the exceptions and the user-entity controls it expects you to run, and record that you did.
The mistake is collecting reports and never reading them. Auditors ask what you concluded. They also ask whether the report period still covers your use, which is why bridge letters matter. NIST's guidance on SA-9 says the organization has no direct control over how an external provider implements controls, so the monitoring has to be your own act.
Keep the list complete, since a vendor that handles customer data and is missing from the list is a finding. Record the contract date, data types shared, the review date and the next review date, and where a vendor does not issue a report, note what you used instead. Review the list at least as often as your policy states, and note who approved each decision.
A sourced example
AWS says its SOC reports exist to "help you and your auditors understand the AWS controls established to support operations and compliance". It publishes the SOC 2 through AWS Artifact, covering 12 months ending March 31 and September 30, and a monthly Continued Operations Letter covers the gap since the last report. AWS SOC compliance page, read 12 Nov 2026.
Related terms
Sources
- AWS SOC compliance page, read 12 Nov 2026
- NIST SP 800-53 Rev. 5 control catalog (OSCAL), read 12 Nov 2026
- Google Cloud SOC 2 page, read 12 Nov 2026
Last reviewed 12 Nov 2026.