How to collect audit evidence for common security controls

What counts as good evidence for access reviews, MFA, backups, onboarding and offboarding, change management, vendors and incidents, and how to keep it current.

Guide · Updated · by the Controlkeep team

In short

Good audit evidence is dated, shows who did what, and comes from the system itself (exports, screenshots with timestamps, tickets), not from a statement that it happened. Collect it on a schedule for each control, such as quarterly access reviews and backup restore tests, so it never goes stale before an audit.

Evidence is what turns "we do that" into "here is proof that we did it, and when". Auditors and customer security teams look for evidence that is specific, dated and tied to the control it supports. This guide lists practical evidence for controls most small companies have, and how to store it so it stays useful. It is general guidance, not an audit opinion; your auditor decides what is sufficient for your report.

What makes evidence good

  • Dated. It shows when the control operated, ideally within the audit period.
  • Specific. It shows the actual system or record, not a policy saying it should happen.
  • Complete enough. It covers the population (all users, all production systems), or explains the sample.
  • Attributable. It shows who performed or approved the activity.
  • Safe to share. Passwords, keys and unnecessary personal data are removed or redacted.

Evidence for common controls

Control areaGood evidenceHow often
Access reviewsAn export of users and roles from each key system, marked up with decisions and who reviewed itQuarterly
Multi-factor authenticationA screenshot or export of the identity provider's MFA enforcement setting, plus a list of exceptionsWhen changed, and yearly
OffboardingTickets for recent leavers showing accounts removed, with datesEach leaver
OnboardingPolicy acknowledgements and access requests for recent joinersEach joiner
BackupsA record of a test restore: what was restored, when, by whom, and the resultAt least yearly
Change managementPull requests or change tickets showing review and approval before deploymentOngoing, sample per period
Vendor managementA vendor list with risk notes, and the review record for important vendorsYearly
Incident responseThe incident log, and a tabletop exercise write-up if there were no incidentsYearly
Security awarenessTraining completion recordsYearly
EncryptionSettings showing encryption at rest and in transit for main data storesWhen changed, and yearly

Storing it so it stays useful

In Controlkeep:

  1. Upload or link once, map everywhere. A quarterly access review can support several controls; attach it once and tick each one it backs up.
  2. Use links for living records. A link to a ticket queue or change log is often better than a screenshot that goes stale.
  3. Set expiry dates on time-bound evidence such as certificates and annual reports; the weekly reminder email lists them 30 days ahead.
  4. Name files clearly, with the system and period: "access-review-crm-2026-Q3.pdf".
  5. Write a short note on the evidence explaining what it shows, so a colleague or auditor understands it without asking.

Files can be PDF, images, text, CSV, Word or Excel up to 10 MB, and are checked by content, not just by extension. See the evidence help article.

Common evidence mistakes

  • A policy instead of a record. "Our policy says we review access" is not evidence that a review happened.
  • Undated screenshots. Include the date and system in the screenshot or the file name.
  • One-off evidence for a recurring control. A single backup test from two years ago doesn't show the control works today.
  • Too much personal data. Redact what isn't needed; don't upload full HR records to prove onboarding.
  • Evidence nobody owns. Each control needs an owner who knows the evidence is due.

Before an audit

  1. Export the control matrix CSV and check every applicable control has current evidence.
  2. Look for controls marked implemented with no evidence; fix the evidence or the status.
  3. Check "not applicable" justifications are written clearly.
  4. Download the JSON audit bundle. It lists every evidence file with its SHA-256 hash, so it's clear what was provided.

For how a small company builds the register around this evidence, see Controlkeep for startups facing their first security review.

Try Controlkeep free

A working control register: owners, evidence, policies and reviews in one place, with exports your auditor can read. The Free plan needs no card; you can export or delete your data any time.