Key takeaways
- CIS Control 14 in v8.1 has nine safeguards, and eight of them are in Implementation Group 1.
- Safeguard 14.1 calls for training at hire and, at a minimum, annually, with content reviewed every year or after significant changes.
- Safeguards 14.2 to 14.8 name the topics: social engineering, authentication, data handling, unintentional exposure, incident reporting, missing updates and insecure networks.
- NIST SP 800-50 Rev. 1 calls for tracking metrics that show whether training changes behavior, such as fewer incidents after a targeted campaign.
- Report rate and time to report show whether training works far better than completion certificates.
What does CIS Control 14 require?
CIS Control 14 requires a security awareness program that teaches the workforce to handle the firm's systems and data securely, with training at hire and at least once a year. In CIS Controls v8.1, the control has nine safeguards. The first sets up the program. The next seven name the topics every employee should be trained on. The last adds deeper training for specific roles.
Safeguard 14.1 also asks firms to review and update the training content every year, and sooner when a significant change in the business could affect it. A move to a new email platform, a shift to hybrid work or the rollout of AI tools are the kinds of changes that should trigger a content update before the next annual cycle.
The seven topic safeguards are:
- 14.2: recognizing social engineering, such as phishing, business email compromise, pretexting and tailgating.
- 14.3: authentication practices, including MFA, password composition and credential management.
- 14.4: data handling, meaning how to identify, store, transfer, archive and destroy sensitive data, plus clear screen and clear desk habits.
- 14.5: causes of unintentional data exposure, such as misdirected email, lost laptops and phones, and publishing data to the wrong audience.
- 14.6: recognizing a potential incident and knowing how to report it.
- 14.7: checking for and reporting missing security updates, and telling IT when automated tools fail.
- 14.8: the dangers of insecure networks, including how remote workers should secure their home networks.
Which Control 14 safeguards apply to a small firm?
Eight of the nine CIS Control 14 safeguards apply to a small firm. Safeguards 14.1 through 14.8 are part of Implementation Group 1, the baseline set CIS calls essential cyber hygiene. Only 14.9, role-specific training, starts at Implementation Group 2.
That matters because IG1 is the floor most small and midsize firms are measured against. If your firm is working through the 56 IG1 safeguards, Control 14 accounts for eight of them. It is also one of the few controls that depends almost entirely on people and process, so the gaps tend to show up in records rather than in system settings.
Safeguard 14.9 is still worth a look for firms below IG2. It calls for role-specific training, with examples such as secure administration courses for IT staff and advanced social engineering training for high-profile roles. At a professional services firm, the partners, the controller and anyone who can approve a wire transfer are the high-profile roles attackers study first.
Why does annual security awareness training so often fail to change behavior?
Annual security awareness training often fails to change behavior because a once-a-year course measures attendance, and attendance is not the outcome that protects the firm. A staff member can pass a 40-minute module in January and approve a fraudulent invoice change in June. The completion record looks fine to an auditor while the risk it was meant to reduce is still there.
NIST makes the same point in SP 800-50 Rev. 1, its September 2024 guidance on building a cybersecurity and privacy learning program. The publication frames the goal as behavior change and a security and privacy culture. It quotes federal policy on moving away from treating security and privacy requirements as "merely compliance exercises" and toward a continuous, risk-based program.
In practice, training fails for a few predictable reasons:
- The content is generic and never mentions the firm's own systems, vendors or approval process.
- It arrives once a year, so it is stale by the time a real attack lands.
- Nobody knows what to do after spotting something suspicious, or reporting feels slow or embarrassing.
- Success is measured by completion rates, so no one notices whether behavior changed.
What does security awareness training that changes behavior look like?
Security awareness training that changes behavior is short, frequent, specific to the firm and tied to an action employees can take in seconds. CIS sets annual training as the minimum. The firms that get results treat the annual course as the anchor and fill the year with smaller touches.
The elements that tend to matter most:
- Firm-specific scenarios. Use the vendors, platforms and approval steps your staff actually see. A phishing example that imitates your own document portal teaches more than a generic one.
- One-click reporting. Safeguard 14.6 asks that people be able to recognize and report an incident. A report button in Outlook or a single, well-known address removes the friction.
- Fast, friendly feedback. When someone reports a suspicious message, tell them what it was. People keep reporting when reports go somewhere.
- Phishing simulations used for practice. A simulation is a teaching moment. Treating failures as disciplinary events teaches people to hide mistakes, which is the opposite of what Safeguard 14.6 asks for.
- Role-specific depth. Give finance staff, executives and IT administrators training built around the attacks aimed at them, as Safeguard 14.9 describes.
- Content updated on change. Refresh modules when the firm adopts new tools or a new type of scam starts circulating, as Safeguard 14.1 asks.
Training also works best alongside technical controls. Strong authentication, such as phishing-resistant MFA, limits the damage when someone does click. Training and technology cover each other's gaps.
How should a firm measure whether training works?
A firm should measure security awareness training by tracking employee behavior over time, alongside course completion. SP 800-50 Rev. 1 calls for identifying and tracking metrics to assess the effectiveness of learning efforts. Its example is checking whether a certain type of incident decreases after a targeted awareness campaign.
Measures worth tracking each quarter:
- Report rate: the share of staff who report a simulated phish. This shows whether people act, which is what Safeguard 14.6 is after.
- Time to report: how long it takes the first person to report a simulated or real suspicious message. Faster reports shorten the window an attacker has.
- Click and credential-entry rates on simulations, trended over time and broken out by department.
- Real-world signals: suspicious messages reported by staff, invoice or payment change requests caught by callback, and incidents traced to human error.
- Coverage: new hires trained before or at the start of access, and annual training completed by everyone else.
Trend lines tell the story. A single simulation result says little. Four quarters of rising report rates and falling credential entries show a program that is changing behavior, and they make a far stronger exhibit for a regulator, an auditor or a cyber insurance underwriter than a certificate of completion.
Do any regulations require security awareness training?
Some regulations that firms follow do require security awareness training, even though the CIS Controls themselves are a voluntary framework.
For example, the FTC Safeguards Rule at 16 CFR 314.4(e) requires covered financial institutions to give personnel security awareness training updated as needed to reflect risks identified in their risk assessment. Our article on what training the FTC Safeguards Rule requires covers that rule in detail. Tax practices that keep a written information security plan face similar expectations, covered in our piece on WISP training records.
Building to Control 14 gives a firm one training program, with one set of records, that it can map to each rule it follows.
What should a firm do this quarter to improve security awareness training?
A firm can make real progress on Control 14 this quarter by checking its training evidence and improving one behavior, without rebuilding the whole program.
- Pull your training records. Confirm every current employee completed training in the last 12 months and every hire since then was trained at or near the start of access, as Safeguard 14.1 asks.
- Check your content against Safeguards 14.2 through 14.8. Note any topic your current course skips, such as home network security for remote staff or reporting missing updates.
- Make reporting one click. Deploy a report button or publish a single reporting address, and confirm someone reviews reports the same day.
- Run one phishing simulation built around a scenario your staff would actually see, then share the results and the lesson with everyone.
- Identify your high-risk roles. List who can move money, change vendor bank details or administer systems, and plan role-specific training for them.
- Pick three metrics, such as report rate, time to report and credential-entry rate, and record a baseline so next quarter has something to compare against.
How does s90 help firms with security awareness training?
If your training record is a stack of completion certificates and you are not sure it would hold up when an examiner, auditor or insurer asks whether training works, that is the gap s90's CIS Controls service is built to close. We run security awareness programs for firms across Los Angeles and Orange County: the training platform, phishing simulations built around your firm's real workflows, one-click reporting and quarterly metrics that show whether behavior is changing. We keep the records your auditors and regulators ask for, mapped to Control 14 and to the rules your firm follows. If you would like a second look at your current program, we are happy to review it with you.




