Compliance evidence mapping: match every control to its proof
Compliance evidence mapping step by step: restate each control, index the evidence, judge whether it shows the control ran, and list every gap.
Free app. Runs on your Mac with the Claude or Codex plan you already have.
What compliance evidence mapping is
Compliance evidence mapping is the work of taking a list of controls, from a framework such as SOC 2 or ISO 27001, a customer questionnaire or your own policy, and matching each control to the records that prove it. Done well, it gives you a map of what is covered, partly evidenced, out of date or missing, with the exact thing to produce for each gap. Done badly, it is a folder of policies labeled ready.
The method below is how a compliance analyst prepares for an audit or a customer review. It is a readiness check for the person responsible for compliance; the final judgement belongs to them and to the auditor. Each step says what to do and why, then how 10folds does it. The method serves any framework, because it works from the control wording you supply.
What it does for the business
- No surprises during the auditFinding the missing access review now gives you weeks to run it. Finding it during fieldwork turns it into an exception in the report. The earlier a gap is found, the more of the audit window remains to close it.
- Collect evidence once, for the right periodA map tells each control owner exactly what to export and for which dates, so nobody gathers the same screenshot three times. It also tells owners which evidence to keep producing during the year.
- Answer customer questionnaires fasterOnce controls point to evidence, a security questionnaire becomes a lookup instead of a project.
- See shared root causesWhen the same people or systems fail two controls, the map shows one problem to fix instead of two. Fixing that cause often closes several gaps at once.
Compliance evidence mapping, step by step
Restate the controls
A control you cannot restate in plain words cannot be evidenced.
What to do
- Write each control in plain words: what it requires, how often (continuous, monthly, quarterly, yearly, once) and who owns it.
- Split a control that asks for two different things into two lines.
- Fix the scope and the audit window, for example the period a SOC 2 Type II report covers.
- Name one control owner for each line.
Why
Frameworks phrase controls broadly. A plain restatement with a frequency is what lets you judge whether a record is recent enough. Scope comes first because evidence from outside the window does not count. Owners matter because evidence is produced by people. A control with no owner rarely has a record.
Index the evidence
Evidence is dated by what it shows, not by when the file was saved.
What to do
- List every evidence file and its kind: policy, record, export, screenshot, report.
- Note the date the evidence itself shows and the period it covers.
- Note the systems it concerns and summarize it in one line.
- List the files you cannot read, so nobody assumes they were checked.
- Note the scope of each file: which systems, teams or locations it covers.
Why
A screenshot saved last week may show a setting from last year. The index keeps the date question honest and makes the matching step fast. Note the kind of each file as well, since a system export and a screenshot carry different weight with an auditor.
Match and judge each control
Each control gets exactly one verdict, and the verdict cites the rows.
What to do
- For each control, read in full every file that bears on it.
- Give one verdict: covered, partly evidenced, out of date or no evidence.
- Count populations exactly (active accounts, staff, systems in scope) and name each exception.
- Check dates against the frequency. A yearly control whose latest record is more than 12 months old is out of date.
- Write the next step for every gap: the export, record or task that would close it.
Why
Auditors test whether a control operated, so a policy alone never makes it covered. Counting from the file catches an incomplete population, such as an access review that skipped five accounts. Control mapping across the whole list also shows when two failures share one cause. Write the reason as one sentence with the counted fact, for example: 3 of 45 active accounts were not reviewed. That sentence is what the control owner and the auditor will read.
Have someone else check the map
A second reader catches the claims the first one wanted to be true.
What to do
- Give a second person the map, the files and a checklist.
- Check every row against the cited file, recount the numbers and redo the date arithmetic.
- Confirm that every control has exactly one row.
- Make sure no row claims more than its evidence shows.
- Record how many rows were corrected and why.
Why
Audit readiness depends on the map being right. One wrong covered verdict hides the gap you most needed to see. Keep a short record of what the reviewer changed, so you can see which kinds of error come back.
Deliver the gaps in order of effort
Start with the controls that have nothing.
What to do
- Open with one sentence: how many controls are covered, and the worst gaps.
- List gaps from most to least work: no evidence, then out of date, then partly evidenced.
- Send each owner their gaps with the next step.
- State what was not checked.
Why
A readiness assessment is useful only if it drives collection. Ordering by effort puts the long tasks, such as a quarterly review that never happened, at the front of the queue. Saying what was not checked stops anyone from reading the map as a full audit.
Common mistakes
- Counting a policy as evidenceA policy shows intent; auditors want a record of the control running.
- Using the file dateThe date that matters is the one the evidence shows.
- Evidence from outside the audit windowA review done before the period does not count for it.
- Ignoring the populationAn access review that covers 40 of 45 accounts is partly evidenced.
- Two owners for one controlWith shared ownership, nobody collects the evidence.
What a good result looks like
- One row per control, with exactly one verdict.
- The file and rows behind every verdict.
- A one-sentence reason containing the counted fact.
- The exact next step and owner for every gap.
- A list of what was not checked.
And then what? Using the result
- Send each control owner their gaps and next steps.
- Start with controls that have no evidence. Some need a full cycle to produce a record.
- Schedule recurring evidence, such as quarterly access reviews, before the next window opens.
- Share the map with your auditor ahead of fieldwork.
- Run the map again a few weeks before the audit.
When to run it
- Before a first SOC 2 or ISO 27001 auditThe map shows how far you are from ready and what to collect. Run it early enough to collect evidence that needs a full cycle.
- Before a recurring auditIt confirms that audit evidence for the new period exists and is complete.
- When a customer sends a security questionnaireTreating the questionnaire as the control list gives you answers tied to evidence. The same map can be reused for the next questionnaire.
- After a change of systems or ownersEvidence often stops being produced when the person or the tool changes.
Questions people ask
How do you map evidence to compliance controls?
Restate each control with its frequency and owner, index every evidence file with the date it shows, read the files for each control, and give one verdict with the rows that support it. Every gap gets a next step. A second reader then checks every row against its file.
What counts as audit evidence for SOC 2?
Records that show a control operated during the period: tickets, logs, signed reviews, system exports. Policies show design, and for a Type II report auditors test operation across the whole window. Screenshots help but carry less weight than exports, and they must show a date.
What is a readiness assessment?
It is a check, before the audit, of which controls have evidence and which do not. It is not an audit opinion and does not certify anything. It tells you what to collect and fix while there is still time.
How do you find compliance gaps before an audit?
Use compliance evidence mapping: match each control to its evidence and judge it as covered, partly evidenced, out of date or no evidence. Everything that is not covered is a gap.
Is compliance evidence mapping the same as an audit?
No. The map is a readiness check prepared for the person responsible for compliance. It does not test whether controls work in practice, does not verify evidence beyond what the files show, and does not replace an auditor.
What if I have no evidence folder yet?
The job still maps every control, all marked no evidence, with the export or record each one needs. The result becomes your collection checklist.
More jobs in Cybersecurity
Map compliance evidence to controls, on your own Mac.Free app. Runs on your Mac with the Claude or Codex plan you already have. Your files stay on your computer.
Download for Mac