LOADING…
Platform  /  Blog  /  Third-party risk

Your supplier passed the assessment. Do you actually know the risk?

Questionnaires and certifications are valuable evidence. The gap starts when organisations treat them as the assurance decision rather than inputs into a live understanding of supplier risk.

A glowing green passed-assessment tick connected to a cyan supplier dependency graph

A supplier can answer every security question correctly, hold a recognised certification and still represent one of your organisation's most consequential supplier risks.

That is not a failure of questionnaires. It is not a failure of certification either. Both can provide important assurance evidence.

The failure is treating the evidence as if it carries the same meaning in every supplier relationship.

Consider two suppliers with similar assessment results. One provides a low-impact marketing service and processes no sensitive data. The other supports an operationally critical service, has privileged connectivity into your environment and would take months to replace. The same answer, certificate or security score does not create the same risk decision.

Supplier assurance is not about collecting the most evidence. It is about knowing what the evidence means for the relationship you actually depend on.

That principle is already present in current guidance. The UK National Cyber Security Centre (NCSC) says organisations should understand their supply chain, determine the relative criticality of suppliers, tailor assurance to the relationship, decide what evidence is needed to support supplier responses, and keep that evidence current as the underlying risk changes. NIST SP 1305, the Cybersecurity Framework 2.0 C-SCRM Quick-Start Guide, takes a similar lifecycle approach: establish and operate a cyber supply-chain risk capability, define supplier requirements, and make the robustness of those requirements correspond to supplier criticality.

Questionnaires are not the problem

A well-designed questionnaire does something important: it creates a structured conversation about governance, access control, incident response, data protection, resilience, subcontractors and other areas that are difficult to infer from the outside.

The NCSC publishes supplier-assurance questions for exactly that reason. It also makes an equally important point: the questions are not a box-ticking checklist. The depth of supporting evidence should depend on supplier criticality and the risk the relationship creates for your organisation.

The useful distinctionA questionnaire is an assessment mechanism. A certification is an assurance artefact. An external security signal is another evidence source. None of them, in isolation, is the complete supplier-risk decision.
E2ERisk framework

Evidence is an input. Risk is the decision.

The same evidence can support different decisions in different supplier relationships.

Evidence

  • Questionnaire responses
  • Certification and audit
  • Testing evidence
  • External monitoring signals
→

Relationship context

  • Business-service criticality
  • Sensitive data
  • System and privileged access
  • Replacement difficulty
  • Concentration and subprocessors
→

Risk decision

  • Accept
  • Remediate
  • Monitor
  • Escalate
  • Restrict or exit

This is where supplier-assurance programmes often become inefficient. Teams focus on getting an assessment completed, then the completed assessment becomes the record of risk. Twelve months later the supplier, the service, the evidence and the threat picture may all have changed - but the "approved" status remains.

Current NCSC guidance explicitly warns that supplier responses and evidence represent a point in time and need to be revisited when the risk profile changes. NIST's C-SCRM guidance similarly treats supplier risk management as a lifecycle capability rather than an onboarding event.

Five questions are more useful than one supplier score

A supplier score can help with prioritisation. The decision becomes defensible when the score sits inside context. Five questions expose whether that context exists.

1

What do we depend on this supplier for?

Link the supplier to the business service, system or data it supports. Without that relationship context, "high risk" and "low risk" are abstract labels.

2

How critical is the relationship?

Consider service importance, sensitive data, system access, concentration risk and how difficult the supplier would be to replace. NIST specifically recommends supplier criticality criteria based on business importance, data sensitivity and access.

3

What does the evidence actually prove?

A certificate, test report or policy may be strong evidence for the scope it covers. Record the scope, date and conclusion it supports rather than converting every artefact into a generic green tick.

4

What has changed?

Evidence expires. Services expand. Subprocessors change. Access increases. New vulnerabilities appear. Assurance needs a trigger for review when the relationship or its security posture materially changes.

5

What are we doing about the gaps?

A finding without an owner, target date, remediation evidence and closure decision is simply an observed problem. Assurance becomes useful when it drives action and records the decision afterwards.

Certification answers an important question - not every question

Certifications and independent assessments matter. The NCSC's supply-chain principles explicitly recognise assurance mechanisms such as Cyber Essentials Plus, penetration testing, external audit and formal security certification where justified.

But the certificate is evidence about a defined scope. Your risk decision has to answer a different question: what does this supplier mean to us?

An ISO 27001 certificate, for example, can provide useful confidence in an organisation's information-security management system within its certified scope. It does not tell you, by itself, whether the particular service you consume is a single point of failure, whether a new subprocessor has been introduced, whether the evidence you relied on six months ago is still current, or whether an open finding has actually been remediated.

An assessment can pass while the assurance decision should still change

A critical managed-service supplier holds a recognised certification and receives a strong questionnaire score. But the certificate excludes part of the service environment, recovery-testing evidence is eighteen months old, a new hosting subprocessor has been introduced and two material findings remain overdue.

The assessment result may still be strong. The assurance decision should not ignore the changed context.

The same is true of externally observable security ratings and threat-monitoring signals. They can reveal changes that a periodic assessment may miss. They are valuable signals - but they cannot see every internal control, contractual dependency or service-specific condition. Good supplier assurance combines sources instead of asking one source to do every job.

The real problem is disconnected assurance

The common failure is not "too many questionnaires". It is a broken chain between the information teams collect and the decisions they need to make.

Supplier details sit in a procurement system. Assessment responses sit in a spreadsheet or questionnaire platform. Certifications are stored in email or document repositories. External ratings live in another tool. Findings are tracked somewhere else. The risk register contains a summary. When a senior stakeholder asks, "Which critical suppliers have evidence that is out of date, unresolved high-risk findings or important fourth-party dependencies?", the answer becomes a manual reconciliation exercise.

Disconnected assurance is costly as well as riskyAnalysts spend time reconstructing supplier records, evidence, findings and risk decisions instead of examining the relationships capable of causing the greatest disruption. Onboarding and risk decisions slow down. Audit, incident and board questions trigger another reconstruction exercise. A defensible decision trail exists only if somebody can rebuild it.

That is exactly the gap current NCSC and NIST guidance points towards: understand the supply chain, prioritise by criticality, require proportionate evidence, manage the relationship over time, include suppliers in incident planning and monitor whether the controls and assurance arrangements still work.

E2ERisk framework

Continuous supplier assurance is a decision loop

It does not mean continuously issuing questionnaires. It means revisiting the decision when evidence, dependencies or risk conditions change.

1. ContextService, data, access and criticality
2. AssessQuestions, evidence and independent signals
3. DecideRisk, confidence and treatment
4. ActFindings, owners and remediation
5. ReassessExpiry, verification and change
Evidence expiresService scope changesAccess increasesNew subprocessorVulnerability or incidentRemediation overdueCriticality changes

This is a more useful definition of continuous supplier assurance. It does not mean continuously sending questionnaires. It means keeping the relationship between context, evidence, risk and action alive for as long as the supplier matters to the organisation.

What this looks like in E2ERisk

E2ERisk Supplier Assurance is designed around that connected lifecycle rather than treating the completed assessment as the end state.

From supplier record to assurance decision

The commercial outcome is not another score. It is being able to see which important suppliers have stale evidence, unresolved findings, changing dependencies or remediation that still needs a decision - without reconciling several systems first.

  • Know the supplier and the relationship. Maintain a supplier register with ownership and criticality, then use applicability rules to make assessment scope relevant to the supplier profile.
  • Collect structured answers and supporting evidence. The Supplier Assurance Questionnaire provides a consistent assessment model, while evidence is held alongside the responses rather than separated into email and shared drives.
  • Prioritise the risks that matter. Domain-weighted scoring, question criticality and analyst criticality override help distinguish the supplier's assessment result from its operational importance to your organisation.
  • Keep evidence from silently ageing. Evidence expiry tracking surfaces upcoming expiry points so an assessment does not remain "current" simply because nobody reviewed it.
  • Turn gaps into managed work. Findings and structured remediation plans carry ownership, deadlines, milestones and evidence of closure, with analyst verification before closure.
  • See beyond the immediate supplier. Subprocessor information can be captured and related to the supplier relationship, helping teams reason about dependencies beyond the first tier.

E2ERisk includes the Threat Centre as part of Supplier Assurance, where other vendors charge for outside-in monitoring separately. Continuous external scanning and supplier security scoring add an independent signal alongside supplier-provided assessment evidence: an additional input to the decision, not a replacement for the questionnaire, the evidence or analyst judgement.

The operating principleQuestionnaire answers tell you what the supplier says. Evidence helps you decide how much confidence to place in it. Criticality tells you how much the answer matters. Monitoring tells you when to look again. Remediation tells you whether anything changed because of what you learned.

The question for security leaders

The maturity test for supplier assurance is not how many suppliers completed an assessment this year.

It is whether, for the suppliers that matter, you can answer a harder set of questions without starting a spreadsheet exercise: What service do we depend on them for? What evidence supports the decision? Is that evidence still current? What changed? What is unresolved? Who owns the action? What sits behind the supplier?

If those answers are connected, questionnaires and certifications become more valuable because they sit inside the context needed to interpret them.

If they are not connected, more evidence can simply create more places to look.

That is the difference between collecting supplier assurance and actually managing supplier risk.

This article is informational and does not constitute legal advice.
Share
Keep reading

Related articles.

More from the E2ERisk team on turning supplier assessments into a live, defensible picture of third-party risk.

Next step

Where to next.

Stay sharp

The E2ERisk briefing

Occasional, practical notes on UK public-sector cyber risk and compliance. No spam, unsubscribe anytime.

Talk to us

See it on your suppliers

A 30-minute walkthrough on your own suppliers - the live platform, no slides. Or send us a question and we will get back to you.

Get in touch