Most breaches at small businesses don't start with a clever exploit. They start with an employee clicking a link, reusing a password, or wiring money to a fraudster who sounded convincing. Verizon's 2024 Data Breach Investigations Report found that 68% of breaches involved a non-malicious human element, such as a mistake or a victim of social engineering. The same report found that in phishing engagements the median time for a user to click was 21 seconds after opening the email, and only 28 more seconds to enter data. Technical controls like firewalls and endpoint protection matter, but they can't stop a trusted user from handing over credentials. The most reliable way to ensure employees are trained in cybersecurity is a structured, ongoing program that follows the approach in NIST SP 800-50 (Building a Cybersecurity and Privacy Learning Program): assess your risks, set clear policies, teach people to spot common threats, reinforce with simulations and short refreshers, and measure results. The sections below walk through each step with a worked example for a fictional 25-person accounting firm, Harbor Ridge Accounting.
Identify the Threats and Data Your Business Needs to Protect
Training works best when it targets your real risks instead of generic advice. Start with a one-page inventory of what you hold and how it could be lost. Harbor Ridge, for example, stores client tax returns (Social Security numbers, bank details), payroll data, and login credentials for the IRS e-Services portal. Its most likely threats are phishing emails impersonating clients, business email compromise (BEC) targeting the office manager who approves payments, and stolen laptops. BEC deserves the weight: the FBI's 2023 Internet Crime Complaint Center report recorded more than 21,000 BEC complaints with adjusted losses of roughly $2.9 billion.
Build a simple risk table and use it to decide which topics get the most training time.
Asset | Likely threat | Who is exposed | Training priority
-------------------------|--------------------------------|-----------------------|------------------
Client tax files | Phishing, malware attachments | All preparers | High
Bank / payroll access | Business email compromise | Office manager, owner | High
IRS e-Services login | Credential theft, weak password| Owner, 2 senior staff | High
Laptops | Theft, loss | All staff | Medium
Guest Wi-Fi | Unsecured network sharing | Reception | Low
Write Simple, Clear Security Policies Employees Can Follow
A 40-page policy document won't be read. Aim for a short acceptable use and security policy, ideally two pages, written in plain language with specific rules. Vague guidance like "use strong passwords" gives people nothing to act on. Concrete rules do.
Your industry may also make training a legal duty. Tax preparers like Harbor Ridge are treated as financial institutions under the FTC Safeguards Rule (16 CFR Part 314), which requires security awareness training for personnel and a written information security plan. The IRS publishes a template for this in Publication 5708 (Creating a Written Information Security Plan for Your Tax & Accounting Practice). Check which rules apply to you, such as HIPAA for healthcare or PCI DSS for card payments, and reference them in the policy.
- Passwords: use a company-approved password manager; generate passwords of at least 16 characters; never reuse a password across systems. This follows NIST SP 800-63B, which favors length over complexity rules and advises against forced periodic changes.
- Multi-factor authentication: required on email, banking, payroll, and the file-sharing platform.
- Payments: any request to change bank details or send a wire over $1,000 must be confirmed by calling the requester at a known phone number.
- Devices: laptops must use full-disk encryption and lock after 5 minutes of inactivity.
- Reporting: report anything suspicious to security@harborridge.example within the same business day, with no penalty for honest mistakes.
- Software: install only apps from the approved list; ask the IT contact before installing anything else.
Have every employee sign the policy at hire and again each year. Keep the signed copies; many cyber insurance applications and client contracts ask for evidence.
Choose a Training Format That Fits Your Team and Budget
You don't need an enterprise budget. The right format depends on team size, how distributed people are, and how much time you can spare. Most small businesses do well with a blend.
- Managed security awareness platforms (such as KnowBe4, Proofpoint Security Awareness, or Huntress SAT): typically priced per user per month, often in the low single-digit dollars for small teams (confirm current vendor quotes), with video lessons, quizzes, and built-in phishing simulations. Best if you want automation and reporting.
- Live sessions: a 45-minute all-hands each quarter using real examples from your industry. Free, and good for discussion, but harder to track and repeat.
- Free resources: CISA's Cyber Essentials and Secure Our World campaign materials, and the FTC's Cybersecurity for Small Business guidance, cover the basics at no cost.
- Microlearning: 5 to 10 minute lessons delivered monthly. Short, frequent sessions are easier to schedule around client deadlines than one long course.
Harbor Ridge chose a hybrid: a 45-minute kickoff session held in the slow month of July rather than during filing season, then a platform at roughly $3 per user per month, which comes to about $900 per year for 25 people. That covers monthly 8-minute lessons and automated phishing tests.
Teach Staff to Recognize Phishing and Social Engineering
Phishing remains one of the most common entry points, so spend the most time here. Teach employees to pause on any message that creates urgency, asks for credentials, requests money or gift cards, or arrives from an unexpected sender. Show real examples rather than describing them in the abstract.
A useful exercise is to display a suspicious email and have staff mark the red flags. Here is a sample you can use:
From: "Microsoft 365 Support" <support@micr0soft-security.example>
To: dana@harborridge.example
Subject: URGENT: Your mailbox will be deleted in 24 hours
Dear User,
We detected unusual activity. Verify your account now or lose access:
https://harborridge-m365-verify.example/login
Microsoft Security Team
- Sender domain uses a zero in place of the letter "o" (micr0soft).
- Generic greeting ("Dear User") instead of the recipient's name.
- Artificial urgency and a threat of losing access.
- Link domain doesn't match Microsoft; hovering over it reveals the real destination.
- Request to log in through an emailed link rather than going to the site directly.
Also cover social engineering beyond email: phone calls from a fake "IT helpdesk" asking for a password, text messages (smishing) with package-delivery links, and visitors who tailgate through a locked door. For a tax practice, add the scenario the IRS warns about repeatedly: a "new client" email with a link or attachment supposedly containing their prior-year return. Teach one habit for all of them: verify through a separate, trusted channel before acting.
Train Employees on Password Hygiene and Multi-Factor Authentication
Stolen and reused passwords are a leading cause of account takeovers; stolen credentials appear among the top initial access methods in Verizon's DBIR year after year. Teach staff why reuse is dangerous: when one site is breached, attackers try the same email and password combination on banking, email, and cloud services (credential stuffing). A password manager removes the burden of remembering dozens of unique passwords.
Show employees how to check whether their address has appeared in a known breach using Have I Been Pwned (haveibeenpwned.com), and walk them through enabling multi-factor authentication (MFA). Microsoft's analysis of account compromises has reported that MFA blocks over 99% of automated account-takeover attempts, which is why it belongs in every policy. Prefer an authenticator app or FIDO2 hardware security key over SMS codes: NIST SP 800-63B classifies SMS as a restricted authenticator because codes can be intercepted, including through SIM swapping. Explain MFA fatigue attacks too: if a user receives repeated unexpected approval prompts, they should deny them and report it, never approve to make them stop.
If you use Microsoft 365, an administrator can confirm who still lacks MFA with the Microsoft Graph PowerShell module:
Connect-MgGraph -Scopes "UserAuthenticationMethod.Read.All","User.Read.All"
Get-MgUser -All | ForEach-Object {
$methods = Get-MgUserAuthenticationMethod -UserId $_.Id
[PSCustomObject]@{
User = $_.UserPrincipalName
MethodCount = $methods.Count
}
} | Where-Object { $_.MethodCount -le 1 } | Format-Table
Users showing only one method (typically just a password) have no second factor registered. Follow up with each of them personally rather than sending a blanket email.
Cover Safe Habits for Devices, Wi-Fi, and Remote Work
Remote and hybrid work extends your attack surface to home routers, coffee shops, and personal phones. Keep this section practical and checklist-driven.
- Install operating system and browser updates within 7 days; enable automatic updates where possible.
- Use a company VPN or a zero-trust access tool when connecting from public Wi-Fi, and avoid accessing client data on open networks.
- Change the default admin password on home routers and enable WPA3 or WPA2 encryption.
- Lock screens whenever stepping away, including at home and in shared spaces.
- Never plug in unknown USB drives, including ones "found" in the parking lot.
- Keep work and personal use separate: no client files on personal cloud storage or personal email.
- Report a lost or stolen device immediately so IT can remotely wipe it.
For Windows laptops, verify that BitLocker encryption is on with a quick check in an elevated command prompt:
C:\> manage-bde -status C:
Volume C: [OS]
Conversion Status: Fully Encrypted
Percentage Encrypted: 100.0%
Protection Status: Protection On
Lock Status: Unlocked
On a Mac, the equivalent check is `fdesetup status`, which should return "FileVault is On."
Establish a Clear Process for Reporting Incidents and Mistakes
The speed of a report often determines whether an incident is a nuisance or a breach. An employee who clicks a bad link and tells IT within five minutes gives you time to reset the password and isolate the machine. One who stays quiet out of embarrassment can let an attacker sit in your mailbox for weeks. Reporting is not yet a habit for most people: the 2024 DBIR found that only about 20% of users reported phishing in simulation engagements, and just 11% of those who clicked also reported it.
Make reporting easy and safe. Set up a dedicated address or a one-click "Report Phish" button in the email client, and state plainly in policy and in training that reporting a mistake in good faith will never lead to discipline. Praise the people who report. Harbor Ridge's owner opens each monthly meeting by thanking whoever reported the most suspicious emails that month.
Give employees a short, printed response checklist so they know what to do under stress:
IF YOU THINK YOU CLICKED SOMETHING BAD
1. Disconnect from Wi-Fi or unplug the network cable. Do not shut down.
2. Call IT at 555-0142 (or text if you cannot talk). Do not wait until later.
3. Do not delete the email. IT may need it.
4. Write down what you clicked, entered, or downloaded, and when.
5. Change your password from a different, trusted device once IT says to.
For tax practices, add a line to the checklist about data theft: the IRS asks preparers to report client data theft to their IRS Stakeholder Liaison and to contact the FTC and state authorities, so IT should know who makes those calls.
Run Phishing Simulations to Test and Reinforce Learning
Simulated phishing emails give employees safe practice and give you data on real-world susceptibility. Send them on an irregular schedule, vary the themes (package delivery, HR announcement, invoice, shared document), and use scenarios relevant to each role. An accountant should see fake client document requests, not just generic lottery scams.
Handle results carefully. Do not publicly shame people who click. Instead, show an immediate teaching page explaining the red flags they missed, and offer a short follow-up lesson to repeat clickers. Track two numbers: click rate and report rate. For context, KnowBe4's 2024 Phishing by Industry Benchmarking Report (vendor data across millions of users) measured a baseline phish-prone percentage of about 34%, falling to about 19% after 90 days of training and about 5% after 12 months. Harbor Ridge's illustrative results follow a similar curve:
Simulation 1 (baseline, fake "shared client folder" email)
Emails sent: 25
Clicked link: 9 (36%)
Entered creds: 4 (16%)
Reported: 3 (12%)
Simulation 4 (six months later, fake "payroll update")
Emails sent: 25
Clicked link: 3 (12%)
Entered creds: 1 (4%)
Reported: 14 (56%)
Notice that the report rate matters as much as the click rate. A rising report rate shows that employees are becoming active defenders, not just avoiding mistakes.
Schedule Regular Refreshers and Onboard New Hires Promptly
Attackers change tactics, and the benchmark data above shows susceptibility drops with sustained training rather than a one-off session. A single annual training is not enough. Combine a few touchpoints across the year so security stays in people's minds.
- Day one or week one for new hires: policy review, password manager setup, and MFA enrollment before they get access to client data.
- Within 30 days: a full awareness course and a first phishing simulation.
- Monthly: a 5 to 10 minute microlesson or a short tip in the team chat.
- Quarterly: a phishing simulation and a 15-minute team discussion of a recent real-world scam.
- Annually: a full refresher, policy re-signature, and updated content covering new threats such as AI-generated voice and video impersonation.
- On demand: a quick alert when a campaign targeting your industry or region is in the wild, such as the IRS's seasonal phishing alerts before filing season.
Tailor content by role. Finance staff need deeper coverage of payment fraud, executives need training on whaling and impersonation, and IT administrators need guidance on privileged account handling. Contractors and temporary workers with system access should complete the same onboarding.
Measure Results and Update Your Training Program
What gets measured gets improved. Pick a handful of metrics, review them quarterly, and adjust the program based on what you see. Avoid vanity metrics such as course completion alone, which says little about behavior.
- Phishing click rate and credential-entry rate: aim for a steady downward trend; under 5% is a strong target for small teams, in line with the 12-month vendor benchmark cited above.
- Report rate: aim to climb above 50% of simulated phishing emails reported, well above the roughly 20% seen in the DBIR's simulation data.
- Time to report: median minutes between a suspicious email arriving and the first report.
- MFA coverage: 100% of accounts on email, banking, and file storage.
- Training completion: 95% or higher within the assigned window.
- Real incidents caused by human error: track count and severity year over year.
After each quarter, hold a 30-minute review. Ask which lessons correlate with improved results, which teams still struggle, and which real incidents or near misses should become new training examples. If the accounting team keeps falling for invoice lures, add a dedicated module on invoice verification. Update policies whenever your tools or threats change, and document each revision.
Employee training is not a project with an end date. It is a recurring practice, like backups or patching. Start small: write the two-page policy, run a baseline phishing test, and schedule your first monthly lesson this week.
Sources and Further Reading
- Verizon, 2024 Data Breach Investigations Report (verizon.com/business/resources/reports/dbir)
- FBI Internet Crime Complaint Center, 2023 Internet Crime Report (ic3.gov)
- NIST SP 800-50, Building a Cybersecurity and Privacy Learning Program, and SP 800-63B, Digital Identity Guidelines (csrc.nist.gov)
- FTC Safeguards Rule, 16 CFR Part 314, and FTC Cybersecurity for Small Business (ftc.gov)
- IRS Publication 5708 (Creating a Written Information Security Plan) and Publication 4557 (Safeguarding Taxpayer Data) (irs.gov)
- CISA Cyber Essentials and Secure Our World (cisa.gov)
- KnowBe4, 2024 Phishing by Industry Benchmarking Report (knowbe4.com)