Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
An assurance report is an independent practitioner’s opinion on a supplier’s controls. Reading one well means checking the scope, the period, the exceptions, and the controls you are expected to run yourself.

How Do You Read an Assurance Report?
An assurance report is an independent practitioner’s opinion on whether an organisation has described its controls fairly and, in most cases, whether those controls operated effectively across a defined period. When a supplier emails you a 90-page SOC 2 report, they are asking you to rely on someone else’s audit instead of running your own. Reading that document properly is a procurement skill, not an accounting one.
Four parts decide whether a report is worth anything to you: what it covers, what the opinion actually says, which exceptions the auditor found, and which controls the supplier quietly expects you to operate at your end.
The names overlap and suppliers use them loosely. The practical distinctions:
| Report | Covers | Who sees it |
|---|---|---|
| SOC 1 / ISAE 3402 | Controls relevant to clients’ financial reporting | Clients and their auditors |
| SOC 2 | Trust Services Criteria: security, availability, processing integrity, confidentiality, privacy | Clients, under NDA |
| SOC 3 | Same subject matter as SOC 2, summary only | Anyone; published freely |
| ISAE 3000 | Any non-financial subject matter, including privacy and resilience | Varies by engagement |
A Type I report tests the design of controls at a single date. A Type II report tests whether they actually worked over a period, usually six or twelve months. Only a Type II tells you anything about operating reality, so treat a Type I as a progress update rather than evidence. An ISO 27001 certificate is a different animal again: it confirms a management system was certified, without the control-by-control test results an assurance report gives you.
Section 3 of a typical report contains management’s description of the system. This is where scope is set, and where most disappointments start. Check which products, platforms, and locations are named; a report for the supplier’s flagship service does not cover the legacy portal your data actually sits in. Check the period and the gap between its end date and today. A report covering 1 January to 31 December 2025 tells you little about a supplier in late 2026 unless they issue a bridge letter, a short management statement confirming no material changes since the period end.
Then look for subservice organisations. Under the carve-out method, the auditor excludes the supplier’s own cloud provider or payment processor and leaves you to obtain assurance separately. Under the inclusive method, those controls are tested too. Carve-out is normal; not noticing it is not.
The practitioner’s opinion sits in section 1 and comes in four flavours: unqualified, qualified, adverse, and a disclaimer of opinion. Qualified means the auditor found something significant enough to name. Many readers stop here, which is a mistake, because the detail lives in section 4, where every control objective is listed alongside the tests performed and the results.
Hunt for the phrase “deviations noted” or “exceptions noted”, read the management response, and judge severity yourself. Three failed access reviews in twelve months is a different problem from one missed backup restore test. Equally, a report with 70 controls and zero exceptions across a full year deserves a raised eyebrow: real operations produce findings, and an auditor who never finds any may have tested very little.
Buried near the end is a list of complementary user entity controls, or CUECs. These are the assumptions the auditor made about you: that you enforce multi-factor authentication on your tenant, review administrator accounts quarterly, configure encryption settings correctly, and remove leavers promptly. If you do none of these, the supplier’s clean opinion protects you from nothing. Extract the CUEC list into your own control register and assign each item an owner.
Under UK GDPR Article 28, a processor must make information available to demonstrate compliance and allow audits; most suppliers satisfy this with an assurance report rather than letting every client inspect their data centre. The NCSC supply chain security guidance expects you to set a proportionate assurance requirement and then check that what arrives matches it. Financial entities face sharper expectations: PRA and FCA outsourcing rules, and DORA for EU-authorised firms, require documented oversight of critical suppliers rather than a filed PDF.
Build a one-page review sheet: report type, period, scope coverage, opinion, number and nature of exceptions, carved-out subservice providers, CUECs assigned. Store it with the contract. Next year you will be able to see whether the supplier improved or simply changed auditors. If you want a second pair of eyes on supplier assurance evidence, our regulation and compliance services cover exactly this review.
They answer different questions. ISO 27001 confirms that a management system meets an international standard and was certified by an accredited body. A SOC 2 Type II gives you the auditor’s actual test results, control by control, over a period. Many buyers ask for both: the certificate for governance maturity, the report for operating evidence you can read.
A bridge letter, sometimes called a gap letter, is a short statement from the supplier’s management confirming that no material changes to controls occurred between the end of the report period and the current date. Ask for one whenever the gap exceeds about three months. It is not audited, so treat it as a representation rather than assurance.
Not automatically. Exceptions show the auditor tested something. What matters is the nature, the count, and the response: whether the control failure touched your data, whether it recurred, and whether management fixed the root cause or described it as isolated. A pattern of repeated deviations in access management or change control is the signal worth escalating.
Only lightly. SOC 3 covers the same subject matter as SOC 2 but omits the system description and the detailed test results, which is why it can be published openly. It is useful as a public signal that a Type II engagement exists. For anything material, request the full SOC 2 report under a non-disclosure agreement.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.