Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
A supplier security assessment examines how a specific supplier protects the data and access you are about to give them, combining questionnaires, evidence review, and technical checks.

What Is a Supplier Security Assessment?
A supplier security assessment is the examination you perform on one supplier, usually before signing and periodically afterwards, to decide whether the data and access you are about to hand over will be adequately protected. It is the operational activity inside a wider third-party risk management programme.
Done properly it answers one question: if this supplier were compromised tomorrow, what would happen to us, and have they done enough to make that unlikely. Done badly it produces a completed spreadsheet and a false sense of having checked.
The depth of an assessment should follow what the supplier actually gets, not their size or how much you pay them. Four scoping questions settle it:
A marketing agency with a mailing list of 200,000 customers deserves more scrutiny than a consultancy billing ten times as much for advice delivered in meetings.
Questionnaires establish a baseline. Industry sets such as the Shared Assessments SIG, the Cloud Security Alliance CAIQ, or a trimmed internal set reduce the burden on suppliers who answer dozens of these a year. Keep yours short and specific; a 400-question form returns 400 answers nobody verifies.
Evidence is where answers become credible. The artefacts worth asking for are:
| Artefact | What to check |
|---|---|
| ISO 27001 certificate | Scope statement and accreditation body; a certificate covering one office proves little about the platform |
| SOC 2 Type 2 report | Criteria in scope, exceptions, carve-outs, and the user entity controls assumed of you |
| Penetration test summary | Date, scope, tester independence, and whether findings were retested |
| Cyber Essentials or Cyber Essentials Plus | Current certification and the scope it covers |
| Incident history | Past incidents, response, and what changed afterwards |
Technical validation is the layer most assessments skip and the one that most often contradicts the paperwork. External checks cost little: TLS configuration and certificate hygiene on their public services, exposed administrative interfaces, DNS and email authentication records, credentials from their domain appearing in breach corpora, and whether internet-facing software is patched. A supplier claiming mature vulnerability management while running an unsupported edge device has told you something the questionnaire did not.
For UK suppliers, Cyber Essentials is a proportionate baseline. Central government requires it for contracts involving the handling of certain personal information or the provision of IT services, and many large UK organisations now mirror that requirement for smaller suppliers who would never obtain ISO 27001. Cyber Essentials Plus adds independent technical verification, which is a meaningful step up from self-assessment.
It covers five technical control areas and nothing about governance, so it is a floor rather than a conclusion. For a supplier holding large volumes of personal data, UK GDPR Article 28 expects sufficient guarantees of appropriate technical and organisational measures, and a basic certificate alone will not demonstrate that if the ICO asks.
An assessment that ends in a risk rating and no contractual change has achieved nothing. Gaps should become either a condition precedent, a time-bound remediation commitment with evidence, or a documented accepted risk with an owner. The contract is also where notification timelines, audit rights, subprocessor approval, data location, and exit terms get fixed, and those clauses are far easier to agree before signature than at renewal.
A point-in-time assessment decays. Critical suppliers deserve annual review, with event-driven reassessment when they are breached, acquired, move hosting, or change their subprocessor list. Between reviews, lightweight monitoring of certification expiry and public breach disclosures catches most material change.
The other half of staying current is reducing what you need to assess. Removing standing access, scoping data sharing down to what the supplier genuinely needs, and retiring unused integrations shrinks the problem faster than any questionnaire improves it.
If you want supplier claims verified rather than collected, our continuous vulnerability scanning services can monitor the external exposure of the suppliers you depend on.
For a low-risk supplier, under an hour: confirm the data and access involved, check basic certification, and record the decision. For a critical supplier holding personal data, expect one to three weeks including evidence review, technical checks, and follow-up questions. Build that time into procurement schedules, because assessments compressed into the final week before signature find nothing useful.
On its own, no. Questionnaires are self-reported and tend to describe intention rather than practice. They are useful for establishing a baseline and for identifying which claims to verify. Pair them with independent evidence such as a certificate, audit report, or penetration test summary, and with external technical checks you can perform without the supplier’s involvement.
Large providers often decline bespoke questionnaires and instead publish standard artefacts such as a SOC 2 report, ISO 27001 certificate, or completed CAIQ. That is usually acceptable, provided the documents cover the service you are buying. A smaller supplier refusing to answer any questions, or unable to produce evidence of basic controls, is itself a finding to record and escalate.
Critical suppliers annually, important ones every 18 to 24 months, and low-risk ones at contract renewal. Add event-driven triggers that bring a reassessment forward: a publicly disclosed breach, an acquisition, a change of hosting location, a lapsed certification, or a significant change in the data or access they hold.
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.