Bengaluru · Riyadh · Delaware | hello@nazztec.comGlobalSaudi Arabia
AI TPRM Platform

How to Review a Vendor’s SOC 2 Report

Receiving a SOC 2 report is not the same as reviewing it. Read the right sections and you will know what the vendor really assures — and what remains your job.

3 min readNAZZTEC Editorial Team
How to Review a Vendor’s SOC 2 Report — cover illustration

Key takeaways

  • Prefer Type II — it tests operating effectiveness over a period.
  • Check that the scope covers the service you buy.
  • Read every exception and management’s response.
  • Implement the complementary user entity controls.

Type I or Type II

A Type I report describes controls at a point in time. A Type II report tests whether those controls operated effectively over a period, usually six to twelve months. For critical vendors, ask for Type II.

Review checklist

SectionWhat to check
Auditor’s opinionUnqualified, qualified or adverse?
System descriptionDoes the scope include your service, locations and systems?
Trust services criteriaSecurity is always included; are Availability, Confidentiality, Processing Integrity or Privacy relevant to you?
PeriodIs it recent? Is there a gap to today?
ExceptionsWhat failed, how often, and the response
Subservice organizationsCarved out or included? Do you need their reports too?
CUECsWhich controls must you operate?

Complementary user entity controls

The report assumes customers perform certain controls — for example, managing their own user access or reviewing logs. If you do not, the assurance does not hold for you. Record each CUEC and the internal owner.

Bridge letters

When the report period ended months ago, ask for a bridge (gap) letter in which management states that no material changes occurred since. It is management’s assertion, not auditor assurance.

Recording the review

Record the review result against the vendor: period, opinion, exceptions, CUECs and follow-up actions. Track the report’s expiry so a new one is requested automatically.

Red flags

  • A qualified or adverse opinion
  • Scope that excludes the service you buy
  • Repeated exceptions in access management or change management
  • Material subservice organizations carved out with no further assurance
  • A report period that ended more than twelve months ago

Turning findings into actions

Each relevant exception should become an issue with the vendor: ask what caused it, what was fixed and when, and whether the next report will show the control operating. Track the issue to closure and link it to the vendor’s residual risk.

When there is no report

Smaller vendors often have no SOC 2 or ISO 27001 certification. Use a proportionate questionnaire with targeted evidence requests, ask for a penetration test summary and key policies, and for critical services agree audit rights in the contract. Revisit the vendor’s assurance position annually — many obtain certification as they grow.

How NAZZTEC helps

NAZZTEC AI TPRM automates this end to end — with AI assistance, segregation of duties, analytics and signed reports — and is available as SaaS, in your private cloud or on-premises. Our consultants design and run the process alongside it through our Audit & Assessment services.

Next step: request a demo of NAZZTEC AI TPRM or read more on the product page.

Frequently asked questions

Is ISO 27001 certification equivalent to SOC 2?
They differ. ISO 27001 certifies a management system; SOC 2 reports test specific controls. Many organizations accept either, depending on the risk.
What if the vendor has no SOC 2 report?
Use a questionnaire with evidence requests, and consider on-site or remote audit rights for critical vendors.
How often should we review it?
Each time a new report is issued — normally annually.
Keep reading

More insights

Talk to the team behind this briefing

Tell us what you are working on. A senior NAZZTEC consultant will come back within one business day with a practical view.

We respond to every enquiry within one business day.