17 November 2026 • Cyber security
In brief: A security awareness training policy sets out who must be trained, on what, how often, how phishing simulations are handled, how incidents are reported and how you prove all of it. Below is a free template with eleven numbered sections you can copy and adapt. Replace the fields in square brackets, such as [Organisation name] and [Policy owner], have the policy approved by the board and review it once a year. The template is written to support ISO 27001 (clauses 7.2 and 7.3, Annex A 5.1 and 6.3), NIS2 (articles 20 and 21), DORA, NEN 7510 and BIO2. A policy only counts at audit if you can show it is followed, so the last part of this article covers rollout and evidence.
Why you need a written awareness policy
Most organisations already do some training. What auditors and supervisors ask for is the decision behind it: who decided that training is mandatory, for whom, at what frequency, and who checks it. Without a written policy, the answer depends on who you ask.
ISO 27001 requires a top-level information security policy (clause 5.2 and control 5.1) and expects topic-specific policies under it. Clause 7.3 requires that everyone working under the organisation’s control is aware of that policy, of their own contribution and of the consequences of not following it. Control 6.3 (A.7.2.2 in the 2013 version) asks for an awareness, education and training programme. NIS2 article 21(2)(g) lists basic cyber hygiene and cybersecurity training as a minimum measure, and article 20(2) obliges members of the management body to follow training themselves. Under DORA, financial entities must include ICT security awareness and digital operational resilience training as compulsory modules for all staff and senior management (article 13(6)).
None of these texts gives you a ready policy. That is what the template below is for.
The template at a glance
Use this table to see what each section does before you start filling in. The full text follows.
| Section | What goes in it | Typical owner |
|---|---|---|
| 1. Purpose | Why the policy exists and which risks it addresses | CISO or security officer |
| 2. Scope | Who it applies to: staff, temporary workers, contractors, board | CISO with HR |
| 3. Roles and responsibilities | Board, policy owner, managers, HR, employees | CISO |
| 4. Mandatory training and frequency | Onboarding, ongoing training, role-based training | CISO with HR |
| 5. Phishing simulations | Whether you run them, how often, how results are used | CISO |
| 6. Reporting incidents and suspicious messages | How and where to report, what happens next | Security team or service desk |
| 7. Measuring and reporting | Which figures are tracked and who sees them | CISO |
| 8. Exceptions | How to request an exception and who approves it | Policy owner |
| 9. Enforcement | What happens when someone does not complete training | HR with managers |
| 10. Review and version control | Review cycle, approval, change log | Policy owner |
| 11. Related documents | Information security policy, incident procedure, acceptable use | Policy owner |
Security awareness training policy template
Copy the text below into your own document. Everything in square brackets is a field to fill in. Remove options that do not apply.
[Organisation name] · Security awareness training policy · Version [1.0] · Approved by [Board / Management team] on [Date] · Policy owner: [Name, role] · Next review: [Date]
1. Purpose
Most security incidents start with a human action: a click on a link, a shared password, a payment to a fake supplier. This policy makes sure that everyone who works for [Organisation name] knows the main risks, knows how to recognise and report them, and keeps that knowledge up to date. It supports the information security policy of [Organisation name] and our obligations under [ISO 27001 / the NIS2 Directive / DORA / NEN 7510 / BIO2].
2. Scope
This policy applies to all employees, temporary workers, interns and members of the [board / management team] of [Organisation name], and to contractors and suppliers who have access to our systems or information for longer than [number] weeks. It covers all locations and all forms of work, including working from home.
3. Roles and responsibilities
- [Board / Management team] approves this policy, provides the budget and follows the training required for its own role, including training on cybersecurity risk management.
- Policy owner ([CISO / Security officer]) maintains this policy, sets the training programme, reports on progress and handles exceptions.
- HR makes sure new employees are enrolled in onboarding training and that training is part of the joining and leaving process.
- Managers give their team time to complete training and follow up when someone falls behind.
- Every employee completes the mandatory training within the set period, follows this policy and reports suspicious messages and incidents.
4. Mandatory training and frequency
- Onboarding: every new employee completes the basic security awareness training within [30] days of starting, and before receiving access to [sensitive systems].
- Ongoing training: all employees take part in short training sessions at least [weekly / monthly]. Topics include phishing, passwords and authentication, social engineering, CEO fraud, safe handling of data and reporting incidents.
- Role-based training: employees in high-risk roles ([finance, HR, IT administrators, executive assistants]) receive additional training on the threats that target their role. Board members follow training on their responsibilities for cybersecurity risk.
- Ad hoc training: after a significant incident or a new threat, the policy owner can make an extra module mandatory.
5. Phishing simulations
[Organisation name] runs phishing simulations [monthly / quarterly] to let employees practise recognising phishing in a safe way. Simulations are announced in general terms in this policy, not individually. Clicking a simulated phishing message is never grounds for disciplinary action. An employee who clicks receives immediate, short feedback or extra training. Results are reported at [department / organisation] level to management. Individual results are only visible to [the policy owner / the security team] and are used to offer extra support. Simulations never imitate [salary changes, bonuses, health matters or other topics we exclude].
6. Reporting incidents and suspicious messages
Every employee reports a suspicious email, text message, phone call or a possible incident immediately via [report button / email address / service desk number]. Reporting a mistake, such as clicking a link or entering a password, is always better than staying silent, and will not be held against the employee. The [security team / service desk] confirms receipt within [time] and decides on follow-up in line with the incident response procedure.
7. Measuring and reporting
The policy owner tracks at least: participation and completion per [department], results per topic, phishing simulation outcomes and the number of reported suspicious messages. A report goes to [the board / management team] every [quarter]. Training records are kept for [number] years as evidence for audits.
8. Exceptions
An exception to this policy, for example an alternative training form for an employee with a disability or on long-term leave, is requested from the policy owner in writing. Exceptions are recorded, have an end date and are reviewed at the annual policy review.
9. Enforcement
Completing mandatory training is part of the job. If an employee has not completed it within [period], the manager is informed and discusses it with the employee. If training is still not completed after [period], the matter is escalated to [HR]. Persistent refusal can lead to measures in line with [the disciplinary procedure / employment conditions], such as temporary restriction of access to [systems]. Clicking in a phishing simulation is explicitly excluded from these measures.
10. Review and version control
The policy owner reviews this policy at least once a year and after significant incidents, organisational changes or new legal requirements. Changes are approved by [the board / management team] and recorded in the change log below.
Change log: [Version] · [Date] · [Change] · [Approved by]
11. Related documents
[Information security policy] · [Incident response procedure] · [Acceptable use policy] · [Privacy statement for employees] · [Disciplinary procedure]

Phishing simulations: why the template punishes refusal, not clicking
Sections 5 and 9 make a deliberate distinction. It is the part of the policy people argue about most, so it helps to know the reasoning.
No law requires phishing simulations. Including them is your own choice, and a sensible one if you want to know whether training works in practice. But a simulation only gives honest results when employees are not afraid of it. If clicking leads to a warning, people stop reporting their mistakes, and a missed report in real life is far more expensive than a click in a test. Security teams call this a just culture: mistakes are learning moments, reporting is rewarded.
Refusing training is different. That is not a mistake under pressure but a choice not to do part of the job. Treating it like any other missed mandatory instruction, starting with a conversation with the manager, is proportionate and defensible. ISO 27001 control 6.4 expects a disciplinary process for policy violations, so your auditor will look for this link.
One exception many organisations make: a repeat clicker in a high-risk role, such as someone who approves payments, gets extra role-based training rather than a sanction. That keeps the focus on reducing risk.
See how 3-minute weekly challenges and phishing simulations turn sections 4 and 5 of your policy into a routine employees keep up.
How the template maps to ISO 27001, NIS2 and DORA
Auditors work from the framework, not from your document. This table shows which sections of the template answer which requirement.
| Framework | Requirement | Template sections |
|---|---|---|
| ISO 27001:2022 | Clause 7.2 (competence), 7.3 (awareness), Annex A 5.1 (policies), 6.3 (awareness, education and training), 6.4 (disciplinary process) | 3, 4, 7, 9, 10 |
| NIS2 Directive | Art. 20(2) management body training, art. 21(2)(g) cyber hygiene and cybersecurity training | 3, 4 |
| DORA | Art. 13(6) awareness and resilience training as compulsory modules for all staff and senior management | 2, 3, 4 |
| NEN 7510 and BIO2 | Both build on ISO 27001/27002:2022 and contain the same awareness control | All |
Need more detail per framework? See what ISO 27001 asks of awareness training and NIS2 training for the board.
Rolling out the policy
- Start with a baseline. Before you set frequencies and targets, measure where you stand. A baseline measurement shows which topics and departments need attention first.
- Get board approval. Present the policy to the board with the baseline and the planned reporting. Under NIS2 the management body approves the cybersecurity risk measures and is liable for them, so their signature matters.
- Involve HR and, where it exists, the works council. Training, data on individual results and enforcement all touch employment matters. In several countries employee representatives have a say before you start.
- Communicate before you launch. Explain why the policy exists, what it asks, and in plain words that clicking a test email will not get anyone in trouble. Managers should hear it first so they can answer questions.
- Start training and simulations. Begin with onboarding and the first round of ongoing training, then add simulations once people know how to report.
- Report the first quarter. The first board report is the moment the policy becomes real. Use it to adjust targets.
Common mistakes
- Copying a policy and never adapting it. An auditor will ask employees what the policy says. If the text mentions a report button you do not have, the policy works against you.
- Annual training only. A single yearly session is easy to plan and quickly forgotten. Set a frequency you can keep up, and keep sessions short.
- Leaving out the board. NIS2 and DORA both name senior management explicitly. A policy that only covers staff misses the point.
- Punishing clicks. It silences the reports you need most.
- No owner and no review date. A policy without an owner is outdated within a year.
- Measuring only completion. Completion shows people clicked through. Results per topic, simulation outcomes and the number of reports show whether behaviour changes. Our article on security awareness metrics explains which figures to choose.
Using the policy as audit evidence
A signed policy proves intent. Auditors also want proof that it is followed. Prepare four things:
- the approved policy with version number, approval date and change log;
- training records per employee: what was offered, what was completed and when;
- phishing simulation results and the follow-up given;
- the periodic reports to the board, and the decisions taken on them.
Expect the auditor to pick a few employees at random and ask what they would do with a suspicious email. Short, regular training makes that conversation easy.
Where Guardey fits
Guardey delivers security awareness training in 3-minute weekly challenges, which covers the ongoing training in section 4 without taking people out of their work. Phishing simulations support section 5. Weekly reports show participation, scores per topic and the departments or colleagues who need extra training, and give you the records auditors ask for in section 7.
Frequently asked questions about a security awareness training policy
What is a security awareness training policy?
It is a document, approved by management, that sets out who must follow security awareness training, on which topics, how often, how phishing simulations and incident reports are handled, and how compliance is measured and enforced. It is usually a topic-specific policy under the information security policy.
Does ISO 27001 require a security awareness policy?
ISO 27001 requires an information security policy and expects topic-specific policies where needed. Clause 7.3 and control 6.3 require that people are aware of the policy and receive awareness training. A separate awareness policy is the clearest way to show how you meet those requirements.
Are phishing simulations mandatory?
No. No law or standard makes phishing simulations mandatory. Many organisations choose to include them in their policy because they show whether training works in practice. If you do, state clearly how results are used.
How often should the policy be reviewed?
At least once a year, and also after a significant incident, a reorganisation or new legal requirements. Record every change with a version number and approval date.
In a personal demo we show the weekly challenges, the phishing simulations and the reports that show your policy is followed.