← Back to Insights
November 18, 2026 · 5 min read · Supplier Evidence
Supplier Evidence Checklist: What Your Clients Will Ask For
If you serve a regulated entity, they'll ask you for evidence. Not certificates — evidence. Here's the practical checklist of what to prepare, what each item proves, and how to get it ready before they ask.
What clients will ask for (and what they won't accept)
They won't accept: ISO 27001 certificate alone, SOC 2 report alone, security policy documents, "we take security seriously" statements.
They will ask for:
1. Security testing evidence
- Latest penetration test report — with findings, not "no issues found"
- Vulnerability scan results — showing critical vulnerabilities patched within SLA
- Remediation evidence — what you fixed and when
2. Detection capability evidence
- SIEM rules mapped to MITRE ATT&CK — what you detect and how
- Detection time metrics — mean time to detect, tested against simulated attacks
- Alert response evidence — what happens when an alert fires, who responds, how fast
3. Incident response evidence
- Incident response plan — tested, not just documented
- Tabletop exercise results — when you last simulated an incident
- Notification timeline — can you notify the client within the timeframe they expect
4. Access control evidence
- IAM configuration review — least privilege enforced, stale permissions removed
- Access logs — reconciled with approved access list
- Privileged access monitoring — admin actions logged and reviewable
5. Data protection evidence
- Encryption configuration — verified, not just "encrypted"
- Key management — key separation, rotation schedule, KMS configuration
- Data classification — what data you hold, where, how it's protected
6. Supply chain evidence (your own suppliers)
- Supplier security assessments — you checked your own vendors
- Dependency scanning — you know what's in your software supply chain
- Compromise response — what happens if one of your suppliers is breached
The difference between "we have security" and "here's proof it works" is the difference between keeping the contract and losing it. Regulated clients will ask. Having the evidence ready before they do is cheaper than building it under pressure.
How to prepare
- Run the tests now. If you haven't done a penetration test this year, schedule one. If your SIEM has never been tested against simulated attacks, test it.
- Document the results. Not "we passed" but "here's the report, here's the remediation, here's the retest."
- Keep it current. Evidence older than 12 months may not be accepted. Update quarterly.
- Organise it. Create an evidence file that maps each client requirement to your proof. When they ask, you send one document.
The suppliers who lose contracts aren't the ones with the worst security. They're the ones who can't prove their security works.
Questions about supplier evidence?
Get in touch. 15-minute call, no obligation.
Get in touch
Aethel Guard is a Netherlands-based security architecture firm serving EU companies of all sizes. Your architect, not your vendor.