Security awareness training proof: what auditors ask
Got a suspicious email? Check it free Paste it into our free phishing checker and get a verdict with the red flags. No sign-up. Then run a free phishing test for your team. Check an email free → “We trained everyone” is not evidence. Whether you are ready for an ISO 27001 audit, a SOC 2 review, a PCI DSS assessment or an NDPC inquiry, auditors tend to ask for the same small set of proofs of security awareness training. Here is what to have ready.
What does an auditor look for in security awareness training?
They look for a defined program, a defined audience, a schedule, and records that show it ran. Advisera notes that for ISO 27001 auditors look at clauses 7.2 and 7.3 along with control A.6.3. They want to see that needed skills are set for each job role, that the right people were trained, and that they know why security matters. Missing evidence can count as a nonconformity.
Advisera also says the control sets no fixed frequency. You define how often, and you measure how well it works.
1. A per-employee completion record
Show, by name or employee ID, which lessons each person finished and when. A sign-in sheet from one meeting is weak. If someone joined mid-year, the record should show they finished onboarding training in a set window, not “eventually.”
2. The actual training content, not just a title
Be ready to show what each lesson covers. “Security Awareness Training” tells an auditor nothing. Write specific learning goals per lesson, such as “spot a fake invoice” or “report a lost laptop.”
3. Evidence the training is current
Show when each lesson was last updated, and why. Old training on fast-moving topics like AI tools or deepfake fraud is a weak signal. A short change log is enough.
4. Phishing test results, where they apply
If your framework or risk assessment calls for phishing tests, keep the data: how many ran, the click and report rates, and the trend. One test two years ago reads very differently from a running program. See how to train employees to spot phishing.
5. A named owner and a set schedule
Say who owns the program and how often it is reviewed. “Whenever someone remembers” is a finding waiting to happen. For PCI DSS, SecurityMetrics explains that the awareness program must be documented and updated at least once every 12 months, and that training must cover threats such as phishing if they matter in your setting. Check the standard text for the exact requirement numbers.
6. What happens when someone does not finish
Auditors may ask what you do when a person misses a deadline. A simple step works: a reminder, then a note to the manager. It shows the rule has teeth.
How do you set up an audit evidence folder?
Make one folder and keep it current. This takes an afternoon.
- Put the training plan in it: owner, audience, schedule.
- Export the completion records each quarter, with dates.
- Save the lesson outlines and learning goals.
- Save phishing test reports and the follow-up on repeat clickers.
- Add a short note each time a lesson is updated.
- Add the quarterly review, signed and dated.
If you can open the folder in five minutes during an audit, you are ahead of most teams.
Which framework needs what?
Each framework asks in its own words. The table below is a simple guide. Always confirm the exact clause with your auditor.
| Framework | What it points to | What to show |
|---|---|---|
| ISO 27001 | Annex A 6.3, clauses 7.2 and 7.3 | Role-based goals, trained people, awareness |
| PCI DSS 4.0 | Requirement 12.6 | A documented program, reviewed every 12 months |
| SOC 2 | Sources cite CC1.4 and CC2.2 | A program that runs over the audit period |
| NDPA (Nigeria) | Duty to use suitable measures | Dated records and breach steps. See the NDPA checklist |
For SOC 2, the sources we found map training to several criteria and do not agree, so check the current AICPA wording with your auditor.
Compliance mapping helps, but do not overstate it
Showing how your training maps to a framework is fine. Just be exact about what is confirmed and what your own compliance team still has to sign off. Overstating a mapping is its own audit finding. Our courses pages show the compliance mapping per module, including where we flag a clause as needing independent checks, so you are not caught citing something you cannot back up.
Common mistakes
- Keeping attendance, but no per-person record.
- Training titles with no content.
- No follow-up for people who miss it or click.
- No owner or date for the next review.
- Saying “compliant” when you mean “supports”.
Need the records without the spreadsheet?
Our platform tracks who finished what and when, and runs safe phishing tests. See pricing or book a free demo. Starting from zero? Use the security awareness checklist.
Questions people ask
What proof of training do auditors want?
Usually a staff list, dates of completion, the course content and some result data. Ask your auditor for their exact list.
What evidence does ISO 27001 Annex A 6.3 need?
Advisera says auditors look at whether needed skills are defined per job role, whether the right people were trained, and whether they understand why security matters. Missing evidence can be a nonconformity.
Do phishing tests count as evidence?
They show real behaviour, so many teams keep the reports alongside completion records.
How often must we train for PCI DSS?
PCI DSS 4.0 asks for a security awareness program that is reviewed and updated at least every 12 months. Check the standard text and your assessor for the exact wording.
How long should we keep records?
Ask your compliance adviser. Different rules set different periods.