ESSENTIAL GUIDANCE · PARTNER GUIDANCE · 5 min read
Part of Expose insights →Vendor security assessment: third-party assurance guide
A vendor security assessment helps you understand what a supplier can access, how a disruption would affect your organisation and which security controls you need to check. Use this guide and the vendor security assessment checklist to plan the work and record your decisions.
Need an acronym translated? Open the cyber glossary →
What does a vendor security assessment cover?
A third-party security assessment looks at the service you buy, the risks that come with it and the evidence the supplier can provide. A questionnaire can help you gather information. For higher-risk services, you may also need to review supporting evidence or arrange authorised technical testing. The customer or its partner manages the assessment. Pentesys supports specific technical checks through Expose and Validate.
Start with what the supplier does
List the systems and business processes that rely on the supplier. Record what data it handles and whether it has administrator access. Ask what would happen if the service were breached or went offline. Note any contract or regulatory requirements, key subcontractors and how easily you could switch providers.
Group suppliers by risk
Group suppliers by the impact they could have on your organisation. For a critical supplier, review the evidence in detail and agree how you will monitor risk. For an important supplier, use targeted questions and schedule a review. For a lower-risk supplier, basic checks may be enough. Revisit the category when the service, access or subcontractors change.
Ask for evidence that matches the risk
Use a questionnaire to identify which claims need evidence. Depending on the risk, ask for current Cyber Essentials evidence, a recent test summary, incident and recovery plans, or details of how the supplier controls administrator access. Check that each document covers the service you buy. Record any gaps, who will address them and by when.
Use external visibility carefully
Public information about domains, certificates and internet-facing services can help you ask more specific questions. Where the customer has approved passive discovery within the agreed scope, Pentesys Expose can help identify changes in a supplier’s public-facing assets. Treat observations as points to discuss with the supplier. Get separate written permission from the relevant system owner before any active testing.
Technical testing requires the system owner's permission
Pentesys Validate can support technical assurance once the relevant system owner has authorised testing in writing. Agree the scope, rules of engagement, timing, permitted methods, contacts and reporting before work begins. If permission is missing, raise the concern with the supplier through your usual review process.
How an MSP or consultancy can coordinate the process
An MSP, MSSP or consultancy can run the supplier assurance review with the customer. Agree which suppliers to assess, collect evidence and track actions. Keep ownership of risk decisions clear. Bring in Pentesys for agreed passive discovery or authorised technical testing where it answers a specific question.
Avoid common assurance mistakes
Tailor the questions to the supplier. Check whether certificates are current and cover the service in scope. Find out which subcontractors have access to your data. Give each gap an owner and a due date. Record who can accept any remaining risk.
Review suppliers when the risk changes
Set the next review date and agree which evidence to refresh. Review sooner if the supplier has a serious incident, takes on new data or access, or changes a key subcontractor. Agree who should hear about major findings and who can decide what happens next.
Download the vendor security assessment checklist
Use the vendor security assessment checklist to record the supplier’s role, risk level, evidence, open actions and next review date. Start with the questions that matter most for the service you buy.
Q&A
Why start with the supplier’s role?
It tells you which questions matter. A supplier that can access customer data or production systems needs different checks from one with limited access.
How much evidence should we ask for?
Ask for enough evidence to make a decision about the risk. For a critical supplier, check the scope and date of each document and follow up on gaps that could affect the service.
What can public internet exposure tell us?
Public information can show which assets are visible and where something has changed. Ask the supplier to confirm what the assets do and which controls apply.
When can we test a supplier’s systems?
Get written permission from the relevant system owner and agree the testing rules before work starts. Check any provider policy that applies to the systems in scope.
What can an MSP, MSSP or consultancy do?
A partner can organise the review, chase evidence and track outstanding actions. Agree with the customer who owns each decision about supplier risk.
About this guide
Published by the Pentesys Editorial Team.
About this guide
Published by the Pentesys Editorial Team. Business review lead: Mathew Colley, Sales Director and Chartered Manager. Meet Mathew and explore his commercial and management experience on our Company page.





