← Back to Insights
Insight  •  Third-Party Risk

What a SOC 1 Report Does Not Tell You

The report covers the vendor’s controls. The controls on your side are still yours.

Your risk travels with your vendorsEvery service provider is another set of controls your business relies on, wherever it sits.
Third-party exposure
Your company
Service providers
0%
of breaches involved a third party
Double the 15% reported a year earlier

The vendor's report covers the vendor.

The rest is still yours.

Source: Verizon, 2025 Data Breach Investigations Report, which analyzed 22,052 security incidents including 12,195 confirmed breaches. Prior-year figure as reported by Help Net Security. Vendor locations are illustrative.
November 2026    4 min read
01

A SOC 1 report is a starting point for relying on a vendor, not a substitute for your own controls.

02

Read the scope, the period, the carve-outs, the exceptions and the user entity controls before filing it away.

03

Third parties are a growing source of risk. Verizon found them involved in 30% of breaches in its 2025 report, double the year before.

Every year the SOC 1 report arrives, someone checks that the opinion is unqualified, and it goes into a folder. Sometimes that is enough. Often it is not.

A SOC 1 report is a useful document. It tells you an independent auditor looked at a service provider's controls and what they found. What it does not do is tell you whether your own controls, the ones that depend on that provider, are working. That part was never in scope.

Report sectionScope, systems and report period

Check the Edges First

Before reading the opinion, read what the report covers. Which services? Which systems and locations? Which period? A report that covers the payroll platform but not the tax filing service, or the US data center but not the one in Ireland, may leave out exactly the piece you rely on.

Timing matters too. If the report period ends in September and your fiscal year ends in December, three months are uncovered. A bridge letter from the provider helps, but it is a statement from management, not an audit.

Then look for carve-outs. Many providers rely on their own subservice organizations, a hosting company for example, and exclude them from the report. Those controls still matter to you. They are just covered somewhere else, or not at all.

Report sectionComplementary user entity controls

The Section Most People Skip

Somewhere in most SOC 1 reports is a list of complementary user entity controls. These are the things the provider assumes you are doing. Reviewing who has access to the platform. Checking that the files you send are complete. Reconciling what comes back.

The provider's controls were designed and tested on the assumption that yours are in place. If they are not, the clean opinion does not protect you.

An illustrative example. A company used an outside payroll provider with a clean SOC 1 report every year. One of the listed user controls required the client to review a payroll change report each cycle. Nobody had been assigned to it. A former employee stayed on the payroll for two months before anyone noticed. The provider's controls had worked exactly as described. The one on the company's side had never been set up.
Report sectionTesting results and exceptions

Exceptions Are Not Footnotes

An unqualified opinion can still come with testing exceptions. They sit in the detailed results, often with a short management response. Read them. An exception in logical access or change management at the provider may mean you need to do more on your side for that period, or at least document why it does not affect you.

Downtown Houston at night
04

Why It Matters More Now

Companies rely on more outside providers every year, and those relationships are becoming a bigger source of risk. Verizon's 2025 Data Breach Investigations Report found that third parties were involved in 30% of breaches, double the 15% reported a year earlier.

That data is about security breaches, which is SOC 2 territory more than SOC 1. The direction is the same, though. More of your control environment now sits inside other companies, and the reports you receive from them only go so far.

A Short Checklist

Before it goes in the folder

  • Does the scope cover the services, systems and locations you actually use?
  • Does the period line up with your fiscal year, and is there a bridge letter for the gap?
  • Are any subservice organizations carved out, and how are they covered?
  • Is every complementary user entity control assigned to someone on your side, and is it working?
  • Were there exceptions, and have you considered what they mean for your controls?
05

What to Take Away

A SOC 1 report tells you about the vendor. Your controls around that vendor are still yours to design, perform and evidence. Reading the report carefully takes some time. Finding out later that a user control was never in place takes far longer.

Close view of a steel suspension bridge tower and cables
A bridge depends on the structure at both ends. So does every vendor relationship.
SourcesVerizon, 2025 Data Breach Investigations Report, which analyzed 22,052 security incidents including 12,195 confirmed breaches. Prior-year figure as reported by Help Net Security.

Have a Specific Problem to Work Through?

An aging finding, control issue, documentation gap, or workstream short on capacity is enough of a starting point. Tell us what is happening and what you need to be true at the end.

Tell us what is stuck, what changed, or what deadline is driving the need. We can determine whether BPS Advisory Group is the right fit and what a sensible scope would look like.