SOC 2 Evidence Collection: What Auditors Actually Want to See
A practical guide to collecting, organizing, and presenting evidence for your SOC 2 audit — from continuous screenshots to manual attestations.
The Evidence Problem
Many companies build excellent controls but fail their first SOC 2 because they can't produce evidence. Controls were running, but the evidence wasn't collected. Auditors find statements like "yes, we did access reviews" unconvincing without documentation.
Evidence is retrospective by nature: you collect it during the observation period, not at audit time. The key insight is that evidence collection must be continuous, not a sprint at the end.
Types of Evidence
System-generated evidence Logs, API exports, configuration snapshots. This is the most defensible evidence because it's generated automatically and is hard to fabricate. Examples: CloudTrail logs, GitHub audit logs, Okta sign-in logs.
Tool-generated reports Reports generated by your GRC tool showing control status over time. SecureSpect's scan history is an example — it shows that automated checks ran continuously throughout the observation period.
Manual attestations Documented human actions: access review sign-offs, change approval records, training completion certificates. These need to show who did what and when.
Screenshots Sometimes the only available evidence is a screenshot of a configuration. This is acceptable but lower quality than system-generated evidence. Time-stamp screenshots and annotate what they're showing.
Evidence Quality Hierarchy
What Auditors Ask For (Common Requests)
| Control | Evidence type |
| MFA enforcement | Okta/Entra sign-in log showing MFA challenges |
| Access reviews | Review completion report with dates and decisions |
| Quarterly access review (Q3) | The Q3 campaign record with user list and actions |
| Branch protection | GitHub repo settings screenshot + audit log of merges |
| Backup testing | DR test execution record with date and result |
| Pen test | Executive summary from tester + remediation tracking |
| Incident response | Incident log entries (including zero-incident attestation) |
| Vendor reviews | Vendor assessment records with review dates |
Organizing the Evidence Package
Structure your evidence by control family:
Evidence Package/
CC6 - Logical Access/
CC6.1 - Asset inventory (2026-Q3).pdf
CC6.3 - Q1 access review.pdf
CC6.3 - Q2 access review.pdf
CC6.3 - Q3 access review.pdf
CC7 - System Operations/
CC7.2 - CloudTrail config export.json
CC7.3 - Incident log (Jan-Sep 2026).pdf
CC8 - Change Management/
CC8.1 - GitHub branch protection settings.png
CC8.1 - PR audit log (Jan-Sep 2026).csv
SecureSpect organizes evidence by control automatically and generates a structured evidence package for each audit cycle — no manual file organization required.
The Zero-Incident Attestation
If your observation period included months with no security incidents, your auditor still needs evidence of that. Don't say "we had no incidents" — produce the incident log showing no entries, or a signed attestation from the security lead: "For the period [date] to [date], no security incidents meeting the classification criteria defined in our Incident Response Policy were observed."