Yes — training completion records export cleanly for ISO 27001 audits, and the export you hand an auditor is the standard artefact for A.5.2, A.6.3 and A.8.2 evidence of security-awareness competence. Modern awareness platforms provide per-learner completion data as CSV/Excel or PDF per-campaign, and Cyber Aware's reporting covers exactly this: per-learner completion rates, campaign history and exportable evidence packs for audit and client reporting. This guide shows what ISO 27001:2022 actually asks for, what a clean export contains, and what auditors check beyond the raw data.
TL;DR
- ISO 27001:2022 controls A.6.3 and A.5.2 (and A.8.2 for phishing-resistant behaviour) need evidence that staff completed security awareness training.
- Every awareness platform we know of exports completion data; the value is in what the export shows, not just that it exists.
- Auditors check: who completed, when, what content, what version, and what happened after someone clicked in a simulation.
- Simulation results, completion timestamps and per-learner remediation are the three artefacts that make an audit go smoothly.
- An export alone is not evidence — the programme's policy, schedule and follow-up process make the export meaningful.
Why this matters
An ISO 27001:2022 audit asks one hard question about the human layer: can you show that your staff were actually trained, not just enrolled? Certification bodies increasingly ask for per-learner evidence rather than a policy PDF, and the difference between a clean audit and a minor nonconformity is often whether the completion data was exportable and current.
Can training completion records be exported for ISO 27001 audits?
Direct answer: yes. Every mainstream awareness platform supports exporting completion records — the question for your audit is not whether the export button exists, but whether the export answers the auditor's four questions: who, when, what content, and what version.
What a clean export contains:
- Per-learner rows — one line per staff member per module, with name, email, completion timestamp and score.
- Campaign-level summaries — completion rate per training wave or simulation campaign, to show the programme ran on schedule.
- Remediation records — which staff were auto-enrolled into follow-up training after clicking a simulated phishing link, and whether they completed it.
- Content version identifiers — the lesson version or campaign template used, so the export shows training matched the current curriculum.
What ISO 27001:2022 actually requires
The standard's controls touch awareness training in three places:
| Control | What it asks | Evidence the export provides |
|---|---|---|
| A.6.3 (Information security awareness, education and training) | Staff receive appropriate awareness training | Per-learner completion records with timestamps and content identifiers |
| A.5.2 (Information security roles and separation of duties) | Roles carry defined competence requirements | Completion data filtered by role or department |
| A.8.2 (Privileged access rights) | Privileged users get extra scrutiny | Simulation results and remediation for admin accounts |
The controls are written as outcomes (people are competent and aware), not as formats — so the standard does not care whether your export is CSV or PDF, only that it is truthful, current and traceable to real learners.
What auditors actually check
Auditors rarely take an export at face value. They typically:
- Sample staff. Pick three to ten employees and trace each one's completion record end to end.
- Check timestamps against the training policy. The policy says training recurs annually or quarterly; the export should show completions inside that window.
- Look at the follow-up. If someone clicked a simulated phishing link, did they complete the remediation lesson?
- Check currency. A 2024 completion for someone who joined in 2025 is a finding. Onboarding training should appear within the policy window for every joiner.
A platform with automated directory sync solves the onboarding gap automatically; manual enrolment is where currency findings usually come from.
Export formats and what works for each audit type
- CSV/Excel — the universal format; auditors can filter, sample and cross-check. Best for surveillance and recertification audits.
- PDF report per campaign — presentable, timestamped, good for stage 1 (documentation review) audits and for handing to enterprise clients who ask for evidence.
- API access — for organisations that pull the data into a GRC tool; useful for large multi-entity certifications.
Most small and mid-size Australian businesses pass audits with CSV plus one PDF per campaign — no integration required.
Common failure modes and how to avoid them
- Enrolment is manual. New joiners get missed. Fix: directory sync so joiners enter the programme automatically.
- The export exists but nobody scheduled the training. A completion report with no campaign cadence behind it looks like a one-off, not a programme. Fix: a documented schedule (quarterly is common) that the export's timestamps visibly match.
- Remediation is not tracked. Someone clicked, nothing happened. Auditors treat that as the programme having no teeth. Fix: auto-enrol clickers into a follow-up lesson and export the completion of that lesson too.
- Records held in a personal drive. Auditors want controlled, retrievable evidence. Fix: the export lives in the ISMS document store with a naming convention.
What a compliant awareness programme looks like end to end
- Policy — the ISMS documents that staff complete awareness training on a schedule.
- Schedule — training waves run quarterly or annually; simulations run monthly.
- Delivery — platform enrolls staff automatically, delivers modules, runs simulations.
- Remediation — clickers get follow-up training the same day.
- Export — per-learner records pulled per audit cycle, stored in the ISMS.
The human risk reporting layer is what turns the raw export into the risk picture management and auditors actually read.
How Cyber Aware handles audit exports
Cyber Aware's security awareness training exports per-learner completion records with timestamps and campaign identifiers, plus remediation records for simulation clickers — the exact artefacts A.6.3 audits ask for. Directory-sync enrolment keeps the data current as staff join and leave, which is the failure mode auditors find most. For non-audit use cases like HR reviews, see whether phishing results feed appraisal software.
Related questions
Does ISO 27001 require specific training content? No. The standard requires staff to be competent and aware; content is your choice. Australian businesses typically localise content (ATO, bank, delivery scams) because it measurably improves engagement.
How often should training run for audit purposes? Annually minimum, quarterly is common practice. The frequency must match what your ISMS policy documents — auditors check consistency between policy and evidence.
Can we export simulation results as well as completion data? Yes. Simulation click and report rates per campaign and per learner are exportable alongside completion records, and auditors increasingly want both.
What if a staff member refuses to complete training? The export shows it, which is exactly what the auditor wants to see — evidence that the programme surfaces gaps. The remediation path is an HR process, not an audit problem.
One last thing
The most common ISO 27001 human-layer finding is not missing training — it is missing onboarding training: staff who joined after the last wave and appear in the export with no completions at all. Automated enrolment from your directory is the single fix that removes that finding permanently.
FAQ
Can training completion records be exported for ISO 27001 audits? Yes. Platforms including Cyber Aware export per-learner completion records as CSV or PDF with timestamps, campaign identifiers and remediation history — the evidence set auditors ask for under A.6.3.
What ISO 27001 control covers security awareness training? A.6.3 in ISO 27001:2022 (awareness, education and training), with A.5.2 and A.8.2 touching role-based competence and privileged-user behaviour.
What format do auditors prefer? CSV/Excel for sampling and cross-checking, plus a PDF per campaign for the audit file. Both are standard exports from awareness platforms.
How recent does the training evidence need to be? Within the window your ISMS policy documents — annually at minimum, quarterly is common. Auditors check that export timestamps match the documented cadence.
Does an export alone satisfy the auditor? No. The export is evidence; the programme behind it — policy, schedule, remediation — is what makes it meaningful. Auditors sample staff and trace records end to end.