You are currently viewing ISO 27001 From Scratch Part 4: Evidence, Documents and the Trail Auditors Follow

ISO 27001 From Scratch Part 4: Evidence, Documents and the Trail Auditors Follow

📋 Key Takeaways
  • An ISO 27001 auditor does not grade your security on vibes.
  • ISO 27001:2022 explicitly requires the following.
  • When an auditor asks for "your last access review," you have 30 seconds to produce it.
  • Control A.5.18 (access rights) requires you to demonstrate provisioning, modification, and review of access.
8 min read · 1,585 words
Educational & Ethical Use Only — This article is provided for educational and ethical cybersecurity research purposes only. The techniques described should only be used on systems you own or have explicit permission to test. Always follow responsible disclosure and the laws applicable to you. Mitigations are included so engineers can harden real systems.
Concept flowThe ISO 27001 audit evidence trail
📜PolicyApproved document saying what you intend to dorefines intent into steps →
📋ProcedureSOP detailing how the control is executedoperating the control generates proof →
🗄️EvidenceLogs, exports, screenshots proving it ranfindings trigger corrective review →
✅Review RecordDated sign-off confirming the control operatesindex every artefact by control ref →
📁Document RegisterIndexed repo with naming and versioning rules

Audits are won on evidence, not intent — trace any control to proof in minutes with policies, evidence, and naming discipline.

Governance & Compliance

🔎 Last updated · Editorial policy · Report an error

TL;DR: ISO 27001 audits are won or lost on evidence, not intent. If you maintain a short list of mandatory documents, separate policies from evidence, and use consistent naming and versioning, an auditor can trace any control to proof in minutes — and you can simulate that entire trail in your own home lab before certification ever matters.

Authorization note: everything in this article is performed on your own lab machines or VMs that you own and control. Do not run evidence-collection scripts, account dumps, or log queries against systems you do not have explicit permission to audit.

Why documentation decides your audit

An ISO 27001 auditor does not grade your security on vibes. They grade it on whether you can show, on demand, that a control exists, is documented, and is actually operating. The phrase auditors use is “objective evidence” — artefacts that independently demonstrate the control works: logs, tickets, review records, signed policies.

The good news: the standard’s mandatory documentation set is small. Everything else you generate is supporting evidence you control.

The mandatory document list

ISO 27001:2022 explicitly requires the following. Build these first, because everything else hangs off them.

  • Scope statement (4.3) — what is in and out of the ISMS, with boundaries and dependencies.
  • Information security policy (5.2) — the top-level policy, approved by management.
  • Risk assessment methodology and results (6.1.2, 8.2) — how you score risk, plus the register of identified risks.
  • Statement of Applicability (SoA, 6.1.3 d) — which Annex A controls apply, why, and their implementation status.
  • Risk treatment plan (6.1.3 e, 6.2) — who fixes what, by when.
  • Measurable objectives and monitoring evidence (6.2, 9.1) — targets and the results of tracking them.
  • Competence records (7.2) — training logs, certifications, role definitions.
  • Documented information records (7.5) — the register of all controlled documents.
  • Internal audit programme and results (9.2) — the plan and the audit reports.
  • Management review minutes (9.3) — evidence the review happened and what was decided.
  • Nonconformity and corrective action records (10.2) — what failed, what you did about it.
  • Incident and event records where relevant (A.5.24–A.5.28, A.6.8).

In a lab, keep them in a single repository so the whole trail is one folder tree:

mkdir -p isms/{01-policies,02-procedures,03-evidence,04-internal-audit,05-management-review,06-records}
tree isms -L 1

# Expected output:
# isms
# ├── 01-policies
# ├── 02-procedures
# ├── 03-evidence
# ├── 04-internal-audit
# ├── 05-management-review
# └── 06-records

Policies vs evidence: the distinction auditors care about

Beginners conflate two different things:

  • Policies and procedures say what you intend to do. “Users’ access rights are reviewed quarterly.” These are prescriptive documents with owners, approval dates, and version numbers.
  • Evidence proves what you actually did. A dated screenshot, a CSV export, a signed-off review record. Evidence is generated by operating the control, not by writing about it.

A policy with no evidence is a nonconformity waiting to happen. Evidence with no policy is uncontrolled activity. The audit trail always runs: policy → procedure → evidence → record of review. If any link is missing, the auditor writes a finding.

Naming conventions and versioning that make audits fast

When an auditor asks for “your last access review,” you have 30 seconds to produce it. That only works with a rigid convention. Use this pattern:

[TYPE]-[CONTROL-REF]-[DESCRIPTION]-[YYYYMMDD]-v[X.Y].[ext]

Examples:

POL-A.5.1-information-security-policy-20240601-v3.0.pdf
SOP-A.5.18-access-review-procedure-20240315-v1.2.pdf
EVD-A.5.18-q2-access-review-export-20240630-v1.0.csv
EVD-A.5.24-incident-log-april-20240430-v1.0.xlsx
AUD-internal-audit-report-access-controls-20240520-v1.0.pdf

Rules worth enforcing:

  • POL / SOP / EVD / AUD prefix tells the auditor instantly whether something is intent or proof.
  • Annex A control reference in the name maps the artefact to the SoA without explanation.
  • ISO dates (YYYYMMDD) sort chronologically everywhere.
  • Version bumps: major (v2.0) for changes requiring approval, minor (v1.1) for editorial fixes. Only one current version lives in the main folder; superseded versions go to an archive subfolder.

Maintain a document register that doubles as your audit index:

# document-register.md (excerpt)
| Doc ID | Name                                      | Owner  | Approved   | Next review |
|--------|-------------------------------------------|--------|------------|-------------|
| POL-001| Information security policy v3.0           | CISO   | 2024-06-01 | 2025-06-01  |
| SOP-014| Access review procedure v1.2               | IT Ops | 2024-03-15 | 2025-03-15  |
| EVD-201| Q2 access review export v1.0               | IT Ops | 2024-06-30 | n/a         |

Worked example 1: the evidence pack for access control (A.5.18)

Control A.5.18 (access rights) requires you to demonstrate provisioning, modification, and review of access. In your lab, build the pack in four steps.

Step 1 — capture the authoritative account list

On your own Linux lab host:

awk -F: '$3 >= 1000 {print $1","$3","$6","$7}' /etc/passwd > accounts-20240630.csv
cat accounts-20240630.csv

# Expected output (example):
# devuser,1001,/home/devuser,/bin/bash
# audituser,1002,/home/audituser,/bin/bash

Step 2 — capture sudo / group memberships

getent group sudo
# Expected output:
# sudo:x:27:devuser

groups devuser
# Expected output:
# devuser : devuser sudo docker

Save the output as EVD-A.5.18-group-membership-20240630-v1.0.txt.

Step 3 — run the review and record decisions

Walk through each account against the joiner/mover/leaver record. Produce a review sheet where each row has a decision and a reviewer signature (a name and date is fine in a lab):

# access-review-q2-2024.md (excerpt)
| Account   | Expected? | Decision       | Reviewer | Date       |
|-----------|-----------|----------------|----------|------------|
| devuser   | Yes       | Retain         | A. Learner | 2024-06-29 |
| audituser | Yes       | Retain         | A. Learner | 2024-06-29 |
| oldintern | No        | REMOVE (exited 2024-06-14) | A. Learner | 2024-06-29 |

Step 4 — prove the corrective action happened

The removal itself must be evidenced, not just noted:

sudo userdel -r oldintern
awk -F: '$3 >= 1000 {print $1}' /etc/passwd | grep oldintern
# Expected output: (empty — account gone)
echo "oldintern removed 2024-06-29 per Q2 access review" >> /var/log/access-review-actions.log

Your finished pack: the SOP, the raw export, the review sheet, and the removal log. Four artefacts, one control, fully traceable.

Worked example 2: the evidence pack for incident management (A.5.24)

Control A.5.24 requires a documented incident process plus evidence it operates. Trigger a controlled incident in your lab: deliberately fail three sudo attempts and capture what your logging picks up.

# As a normal user, generate the event:
sudo -k
sudo cat /etc/shadow   # enter wrong password three times

# Then, as admin, extract the evidence:
sudo grep "authentication failure" /var/log/auth.log | tail -n 3

# Expected output (example):
# Jun 30 10:14:02 labhost sudo: pam_unix(sudo:auth): authentication failure;
#   logname=devuser uid=1001 euid=0 tty=/dev/pts/0 ruser=devuser rhost=

Now log it through your incident procedure. Save the extraction as EVD-A.5.24-failed-sudo-detection-20240630-v1.0.txt, open a ticket (even a simple markdown ticket file works in a lab) with an ID, classification, and closure decision, and record the timeline:

# INC-2024-007.md
- Detected: 2024-06-30 10:15 (auth log review)
- Classified: false positive / test trigger — no escalation
- Evidence: EVD-A.5.24-failed-sudo-detection-20240630-v1.0.txt
- Closed by: A. Learner, 2024-06-30 10:22

The auditor’s chain is complete: procedure document → detection log → ticket → closure record. Even the “we decided this was nothing” decision is evidence the process runs.

The internal audit programme

Clause 9.2 requires internal audits, and they must be independent — you audit an area you weren’t responsible for. In a small team or a solo lab, that means rotating scope. Plan at least one audit per major control area per year:

Quarter Scope Controls sampled
Q1 Governance and policies A.5.1, A.5.36, SoA currency
Q2 Access control A.5.15–A.5.18
Q3 Operations and incidents A.5.24–A.5.28, A.8.15 logging
Q4 Supplier and physical A.5.19–A.5.23

Audits follow the same trail you just built: pick a control from the SoA, pull the policy, pull the most recent evidence, check dates and completeness, and write findings. Log each finding as a nonconformity with an owner and a due date — that record itself is mandatory (clause 10.2).

A lab-sized audit checklist entry looks like:

# internal-audit-q2-2024.md (excerpt)
Control: A.5.18 Access rights
- Policy exists and current? PASS (SOP-014 v1.2, reviewed 2024-03-15)
- Quarterly review performed? PASS (EVD-201, 2024-06-30)
- Leaver removed within SLA? PASS (removed 15 days after exit)
- Finding: access review uses manual CSV export; recommend automation. (Minor NC, due 2024-09-30)

Management review inputs

Clause 9.3 mandates management review, and the standard lists the required inputs. Your minutes must show each was considered:

  1. Status of actions from previous reviews.
  2. Changes in internal and external issues relevant to the ISMS.
  3. Feedback on performance, including nonconformities, corrective actions, monitoring results, audit results, and fulfilment of objectives.
  4. Risks and opportunities status.
  5. Extent objectives are met.
  6. Results of risk assessment and treatment plan status.
  7. Opportunities for improvement.

The outputs matter too: decisions on improvement, changes to the ISMS, and resource needs. In your lab, write the minutes as a structured document with one paragraph per input and explicit decisions, dated and “signed” by the accountable person:

# MGT-review-2024H1-v1.0.md (excerpt)
Input 4 (risks): Risk R-03 (single lab host, no offsite backup) unchanged.
Decision: accept for now; revisit after budget review Q3.
Input 5 (objectives): MTTD objective 30 min — met (avg 22 min, see EVD-205).
Output action: automate access review export. Owner: IT Ops. Due: 2024-09-30.

Note how the outputs feed the next audit and the next review — that closing loop is exactly what auditors check for in clause 9 and 10.

Checklist: the trail auditors follow

  • Every control in your SoA points to at least one policy/procedure and one dated evidence artefact — name them with POL/SOP/EVD-A.x.y-date-vN so the mapping is self-evident.
  • Evidence proves operation, not intention — exports, logs, review records with dates and decisions; keep only the current version front-and-centre and archive the rest.
  • Run internal audits on a rotating schedule and record findings as nonconformities with owners and due dates, even minor ones.
  • Management review minutes cover every required input and produce explicit decisions with owners and deadlines.
  • Corrective actions close the loop — the fix itself (like the userdel above) generates new evidence for the next audit.
HMMNM Security
Published by HMMNM Security

Hands-on cybersecurity tutorials, CVE breakdowns, and guided learning paths — written and lab-tested by the HMMNM Security team.

Keep going — the structured way
This post is one step. The learning paths chain the next ones for you, with progress tracking and no account needed.
Follow a learning path →

Check your understanding

1. According to the article, what does an ISO 27001 auditor actually use to grade your security?

2. What happens if you have evidence of a control but no corresponding policy?

3. Why is the Annex A control reference embedded in document filenames?

4. How should version numbering be handled for superseded policy documents?

Your answers stay in this browser only.

Prabhu Kalyan Samal

Application Security Consultant and founder of Hmmnm. Certified Red Team Operator, Burp Suite Certified Practitioner, eWPTX, CompTIA SecurityX and Azure Security Engineer. Writes hands-on labs and threat analysis on web, cloud and AI-agent security.