Free Template · Policies

Security Awareness Training Policy Template

A ready-to-adopt policy that sets who must be trained, when, and on what: new-hire and annual training, a topic curriculum, no-blame phishing simulations, role-based training for finance and admins, completion tracking, and a training record log.

Free · No sign-up · Word & PDF · Updated September 24, 2026

Who needs this

  • Businesses whose cyber insurer asks whether employees receive security awareness training and phishing testing
  • Companies subject to HIPAA, the FTC Safeguards Rule, or client contracts that require documented staff training
  • Owners who have bought a training platform but never written down the expectations
  • Any team that handles payments, client data, or wire transfers

Why it matters

Most attacks on small businesses start with a person: a convincing email, a phone call to the front desk, or a fake invoice. Technology blocks a lot, but trained employees who pause, verify, and report are the last line of defense.

A written training policy makes the program consistent and provable. When an insurer, auditor, or client asks "do you train your staff?", you can show the policy, the schedule, and the completion records.

What’s in this template

  • Training requirements for new hires, all staff annually, and high-risk roles
  • A curriculum table covering phishing, BEC, MFA, phone pretexting, and AI voice fraud
  • Phishing simulation rules with a no-blame, coaching-first approach
  • Completion metrics, records, and a training log
  • Employee acknowledgment block
A starting point, not legal advice. This template is general guidance written for small businesses. Edit it to match how your business really operates, and review it with your attorney, insurer, and any regulator or auditor you answer to before you adopt it. Using a template does not by itself make you compliant with any law or contract.

Full template preview — text in [brackets] fills in from the form.

[Company name]

Security Awareness Training Policy

Organization[Company name]
DocumentSecurity Awareness Training Policy
Document owner[Owner name], [Owner title]
Approved by[Approver name], [Approver title]
Effective date[Effective date]
Version[Version]
Review frequencyReviewed [Review frequency] and after any significant change
ClassificationInternal use

1. Purpose

This policy establishes the security awareness training program of [Company name]. Its purpose is to make sure every person who uses company systems or handles company and client information understands the threats they are likely to face, knows the company's security rules, and knows how and when to report something suspicious.

The program supports the company's other policies, including the Acceptable Use Policy, the Password and MFA Policy, and the Incident Response Plan, and helps meet training expectations from cyber insurers, clients, and applicable regulations.

2. Scope

This policy applies to all employees, owners, managers, temporary and seasonal staff, interns, and contractors who have a company email account or access to company systems or data. Contractors provided by a vendor may meet this requirement through their employer's training if it covers equivalent topics and the vendor confirms completion in writing.

3. Roles and Responsibilities

Role Responsibilities
Program owner ([Training program owner]) Runs the program: assigns training in [Training platform], schedules phishing simulations, tracks completion, follows up with non-completers, and reports results to leadership.
[IT provider / MSP] Configures the training and simulation platform, allow-lists simulation emails, provides technical content and threat updates, and helps with coaching after risky clicks.
Managers Make time for staff to complete training, reinforce expectations, and address repeated non-completion.
[HR contact] Adds training to onboarding, stores signed acknowledgments, and handles consequences for policy violations.
All personnel Complete assigned training on time, apply it on the job, and report suspicious messages and events.

4. Training Requirements

New-hire training

  • Before receiving access, new personnel read and sign the Acceptable Use Policy and this policy.
  • On the first day, the manager or program owner covers the essentials: how to report a suspicious email, the payment verification rule, MFA setup, and where to find company policies.
  • Full baseline training in [Training platform] is completed within [Days to complete new-hire training] days of the start date. Access to sensitive systems (payments, client records) may be withheld until it is complete.

Ongoing training

  • All personnel complete refresher training [Refresher training frequency].
  • Short "micro" lessons (5 minutes or less) may be assigned throughout the year on current threats.
  • When a significant new threat appears (for example, a scam targeting our industry or a new attack seen in our own mailboxes), the program owner sends a brief alert with examples and what to do.
  • Staff who return from an extended leave complete any training assigned while they were away within 30 days of return.

5. Training Curriculum

At minimum, the program covers the following topics during baseline training and rotates them through the year:

Topic Key behaviors employees should learn Audience
Phishing and malicious links Check the sender and link destination; be wary of urgency and unusual requests; never enter credentials from an email link; use the Report button. All
Business email compromise and payment fraud Verify any new or changed payment instructions by calling a known number, never one in the email; require two-person approval for wires. All; in-depth for finance
Passwords, password manager, and MFA Use long unique passphrases stored in [Company password manager]; never approve an MFA prompt you did not start; report unexpected prompts. All
Social engineering by phone and in person Callers claiming to be IT, a bank, or a vendor may be attackers; verify identity before resetting passwords or giving information; help-desk requests are confirmed through a known channel. All; in-depth for front desk and admins
AI-generated and deepfake fraud Voice and video can be faked; a call that sounds like the owner asking for money or gift cards must be verified through a second channel or code word. All; in-depth for finance and executives
Handling sensitive data Know what data is confidential; send it only through approved secure methods; do not store company data in personal accounts or unapproved AI tools. All
Physical security Lock screens, badge or escort visitors, do not leave documents on printers, shred sensitive paper, report lost devices immediately. All
Remote and mobile work Use company-approved devices and secure Wi-Fi; avoid public computers; keep devices updated and locked. All remote and hybrid staff
Recognizing and reporting incidents What counts as an incident, and how to report to [Security reporting email] or [IT contact] right away, even if you clicked. Speed matters more than blame. All

Drafting note: Tailor examples to your business. A dental office should see fake insurance-portal emails; a law firm should see fake closing-wire changes. Real examples caught by your own filters make the best training content.

6. Phishing Simulations

The company runs simulated phishing campaigns [Phishing simulation frequency] to give employees safe practice spotting and reporting phishing. Simulations follow these rules:

  • Simulations reflect realistic threats but will not impersonate benefits, pay changes, or personal emergencies in ways that could cause real distress.
  • Results are used for coaching, not punishment. The goal is a higher report rate, not catching people out.
  • An employee who clicks receives immediate short training explaining the warning signs they missed.
  • An employee who clicks or enters credentials in three simulations within 12 months meets with their manager and the program owner for one-on-one coaching.
  • Reporting a simulation through the Report button counts as a success and is recognized.
  • Individual results are shared only with the employee, their manager, and the program owner. Aggregate results are shared with leadership.

7. Role-Based Training

People in higher-risk roles receive additional training at least annually:

Role Additional training
Finance, bookkeeping, and anyone who can pay or change vendors Payment verification procedures, invoice and vendor-change fraud, wire and ACH controls, gift card scams, deepfake voice requests.
Owners and executives Targeted spear phishing, impersonation of leadership, travel and public Wi-Fi risks, approving security exceptions, their role in incident response.
IT administrators and anyone with admin rights Protecting privileged accounts, verifying help-desk and reset requests, secure remote access, recognizing signs of compromise.
HR and payroll Direct-deposit change scams, W-2 and tax-form phishing, protecting employee records, secure onboarding and offboarding.
Front desk and customer-facing staff Phone pretexting, visitor management, verifying callers before sharing client information.

8. Reporting Suspicious Activity

Every employee is expected to report suspicious emails, calls, texts, messages, devices, or activity promptly. Reports can be made by:

  • Using the Report Phishing button in [Email / productivity platform]
  • Emailing [Security reporting email]
  • Contacting [IT contact] at [IT contact email] or [IT contact phone]

If you clicked a link, entered a password, opened an attachment, or approved an MFA prompt by mistake, report it immediately. No one will be disciplined for promptly reporting their own mistake. Delayed reporting is what turns a small mistake into a serious incident.

9. Tracking, Records, and Metrics

The program owner keeps records of training assigned and completed, simulation results, and signed acknowledgments for at least three years, or longer if required by a regulation or contract. Records are available to leadership, auditors, and insurers on request.

Metric Target Reviewed
New hires completing baseline training within [Days to complete new-hire training] days 100% Monthly
Annual training completion 100% within 30 days of assignment Quarterly
Phishing simulation click rate Trending down year over year Quarterly
Phishing simulation report rate Trending up year over year Quarterly
Median time to report a real suspicious email Under 30 minutes Quarterly
Role-based training completion 100% of designated roles Annually

10. Non-Completion and Violations

  1. Training not completed by the due date: automated reminder, then notice to the manager after 7 days.
  2. Training more than 30 days overdue: the program owner may restrict access to sensitive systems until it is completed.
  3. Repeated non-completion or willful disregard of security procedures (for example, bypassing payment verification) is handled by [HR contact] under the company's disciplinary process.

Clicking on a phishing simulation, by itself, is treated as a coaching opportunity and not as a disciplinary matter.

11. Annual Training Calendar

The program owner publishes a simple calendar at the start of each year so training is spread out and aligned with the times of year when specific scams peak. A sample calendar:

Month Training focus Activity
January Tax-season and W-2 scams; payroll direct-deposit fraud Micro-lesson; role-based session for HR and finance
February Passwords, password manager, and MFA prompts Micro-lesson; check that everyone uses [Company password manager]
March Annual refresher training Full course in [Training platform]
April Business email compromise and payment verification Finance tabletop: walk through a fake vendor bank change
May Hurricane-season scams and remote work security Micro-lesson; confirm remote access works
June Phone pretexting and help-desk impersonation Micro-lesson; review caller verification steps
July Handling sensitive data and approved AI tools Micro-lesson
August Physical security and clean desk Walk-through of the office
September AI voice and video impersonation Micro-lesson; confirm executive code-word procedure
October Cybersecurity Awareness Month: reporting and incident response Team discussion of real examples caught this year
November Holiday shopping, gift card, and shipping scams Micro-lesson
December Year-end review Program owner reviews metrics and plans next year

Drafting note: Phishing simulations run on their own schedule ([Phishing simulation frequency]) alongside this calendar. Adjust themes to match what your email filters and staff are actually seeing.

Building a reporting culture

Leaders set the tone. Owners and managers are expected to complete their own training on time, report suspicious messages themselves, follow the payment verification rule even when it is inconvenient, and thank employees who report, including when a report turns out to be harmless. A culture where people feel safe saying "I think I clicked something" is the most valuable outcome of this program.

12. Program Review

The program owner reviews this policy and the curriculum [Review frequency] with [IT provider / MSP], considering recent incidents, simulation results, new threats, changes in staff roles, and insurer or client requirements. Results and recommendations are summarized for [Approver name].

13. Training Record Log

Employee Role Training / module Date assigned Date completed Notes
    New-hire baseline      
    Annual refresher      
    Role-based: finance      
           
           

Drafting note: If your training platform keeps these records automatically, reference the platform report here instead and export a copy each year.

14. Employee Acknowledgment

I have read and understand the [Company name] Security Awareness Training Policy. I agree to complete assigned training on time, follow the practices taught, and promptly report suspicious activity and my own mistakes.

Employee name Signature Date
     

15. Revision History

Version Date Description of change Author
[Version] [Effective date] Initial adoption of this Security Awareness Training Policy [Owner name]
       
       

16. Approval

This Security Awareness Training Policy has been reviewed and approved by the undersigned and is effective as of [Effective date]. It will be reviewed [Review frequency], after any significant incident, and whenever there is a material change to our systems, staff, or legal obligations.

Signature:Name / title: [Approver name], [Approver title]Date:
Signature:Name / title: [Owner name], [Owner title]Date:

Template adapted from the free Security Awareness Training Policy template by PinellasIT (pinellasit.com/templates). Review with your legal counsel and insurer before adoption.

Frequently asked questions

How often should employees get security awareness training?

A common approach is baseline training within the first couple of weeks of hire, a full refresher at least once a year, and short monthly or quarterly lessons and phishing simulations in between. Frequent short practice tends to work better than one long annual session.

Should employees be punished for failing phishing tests?

This template takes a coaching-first approach: a click triggers immediate short training, and repeated clicks lead to one-on-one coaching. Punishing clicks tends to discourage people from reporting real mistakes, which is what matters most in an actual attack.

Do cyber insurers require security awareness training?

Many cyber insurance applications ask whether you provide regular security awareness training and phishing simulations, and some make it a condition of coverage. Check your own application and policy wording, and keep completion records you can produce if asked.

Want a second set of eyes on your plan?

We’re a local Tampa Bay IT team. We can walk through your Security Awareness Training Policy with you and check it against how your systems actually work — or just email you when we update these templates. Totally optional; the downloads above are free either way.

What would you like?

We’ll only use your details to reply to this request. Prefer email? info@pinellasit.com