Security Awareness Is a Program, Not an Annual Event

As we move into CIS Control 14, Security Awareness and Skills Training, we’re shifting our attention from technology to the people who use it. Safeguard 14.1, Establish and Maintain a Security Awareness Program, provides the foundation for everything that follows. CIS requires organizations to train workforce members when they’re hired and at least annually after that. The content should also be reviewed annually and updated when significant changes affect the organization.

That gives us the minimum requirements. But checking the annual training box isn’t the same thing as building security awareness. The goal isn’t simply to prove that everyone watched a video. It’s to influence how people behave when they’re using the organization’s systems and handling its information.

 

Completion isn’t the same as awareness

 

Years ago, when I worked as the CISO for a national clothing chain, I handled security awareness training differently between two offices. For our financial office, we watched 3rd party training videos together. Afterwards, we talked through the material, discussed why it mattered, and related it to the things employees actually did every day.  Including activities outside of work and how this could impact their personal accounts.

For our merchandising office, I did nothing.  We didn’t have the time or the budget at the time. Later, we conducted phishing testing for both groups. The merchandising office had roughly a 60 percent failure rate. The financial office did better, but not much better, at around 50 percent.

What was interesting was what happened before people failed. Significantly more people from the financial office contacted me because something didn’t feel right. Some even asked whether the message was part of a test. And then some of them responded anyway.

That experience stuck with me because it reinforced something I’ve seen repeatedly since then. People can understand security concepts and still make mistakes when they’re placed in a real situation. Training matters. But one training session, even a good one, doesn’t automatically change behavior. That’s why awareness needs to be a program rather than an event.

 

Annual training is the floor

 

Most organizations understand the annual training requirement. An employee receives a notification, logs into a learning platform, completes the required course, and the organization records the completion. There’s nothing inherently wrong with that. Annual training provides a useful baseline, and CIS specifically requires it.

The problem is when that’s the entire program. If the only time employees hear about security is during a thirty-minute course once a year, we’re asking them to remember that information months later when they encounter something unusual.

Think about most other skills we expect people to maintain. We don’t typically assume that exposure to a topic once every twelve months creates lasting proficiency. Security awareness isn’t any different.

 

Awareness works better when it’s reinforced

 

I worked with a higher-education client where our team took a different approach. We developed short security awareness content that could be displayed on flat screens throughout campus. The material was simple. PowerPoint-style slides with narration and short messages that could be rotated through displays people encountered during their normal day.

It wasn’t intended to replace formal training. It was reinforcement. Instead of security disappearing for eleven months after annual training, employees and students continued to encounter reminders as part of the environment around them.

That kind of reinforcement can take many forms. Short internal messages, intranet content, staff meeting reminders, digital signage, newsletters, or brief awareness campaigns can all keep security visible without requiring another hour-long training course. The delivery mechanism matters less than the consistency. If you want people to think about security regularly, security has to show up regularly.

 

Engagement matters too

 

Another higher-education client took that idea considerably further. We used an escape-room-style security awareness exercise. Instead of sitting through slides or watching another training video, participants worked through scenarios and solved problems as a group. It turned security awareness into something interactive.

The response was overwhelmingly positive. People wanted to participate. They talked about the experience afterward. They engaged with the material in a way that’s difficult to achieve when everyone is simply waiting for the training video to reach 100 percent completion.

I’m not suggesting every organization needs to build a cybersecurity escape room. That’s obviously not practical for everyone. The lesson is that delivery matters. If employees view security awareness as an annual obligation they have to get through as quickly as possible, they may satisfy the compliance requirement without absorbing much of the message. A good program looks for ways to make security relevant enough that people pay attention.

 

Make the program fit the organization

 

Awareness content also needs to reflect the environment in which people actually work. A small manufacturing company, a university, a healthcare organization, and a financial institution don’t operate the same way. Their employees use different systems, handle different information, and encounter different risks.

That doesn’t mean every organization needs completely custom training material. Third-party training platforms can be extremely useful. But canned content should be supplemented with context. What does this mean here? Why does our organization care about this? What would we expect an employee to do?

Those conversations turn generic security concepts into something people can apply to their own jobs. That’s also why CIS requires organizations to review and update the program. Businesses change. New technologies are introduced. Companies acquire other companies. Employees begin working remotely. New threats emerge. A training program that made sense three years ago may no longer reflect how the organization operates today.

 

Security awareness isn’t an IT problem

 

There’s another mistake organizations make when building these programs: treating security awareness as something IT does to everyone else. IT or security may administer the program, but security behavior belongs to the entire organization.

Leadership support matters. Managers need to reinforce expectations. HR is often involved in making sure training happens during onboarding. Communications teams may help deliver ongoing messages. Employees need to understand that security is part of their responsibility when they interact with company systems and information. The most effective programs make security part of normal business behavior rather than something employees associate exclusively with the IT department.

 

Measure more than completion

 

Completion records are useful. They tell you whether people took the required training. They don’t tell you whether anyone learned anything.

My experience at Harold’s is a good example. Everyone had received training. The financial office had even received more interactive, instructor-led training. Yet when we tested what happened afterward, the results showed there was still considerable work to do.

That doesn’t mean the training failed. It means the program wasn’t finished. Security awareness should create feedback. Organizations should look at how employees respond, where confusion continues to exist, what questions people ask, and where additional reinforcement may be needed. The goal isn’t to catch people doing something wrong. It’s to identify where the organization needs to do a better job helping people make the right decision.

 

A place to start

 

If your organization currently treats security awareness as an annual training assignment, don’t throw away what you already have. Build on it. Make sure new employees receive training when they join. Continue the annual training requirement. Review the content regularly to make sure it still reflects the organization and the way people work.

Then look for opportunities to reinforce the message throughout the year. Those efforts don’t have to be elaborate. A short message that employees actually read may accomplish more than another thirty-minute video they click through while answering email.

The safeguards that follow will address the specific security topics workforce members need to understand. Safeguard 14.1 comes first because those individual lessons work better when they’re part of an intentional, ongoing program.

Security awareness isn’t about proving that everyone completed training. It’s about helping people remember what they learned when it actually matters.

Tim Marley

Tim Marley

Let's Connect. Make Better Technology Decisions with Forthright.

Understand your current environment and get a clear path forward. Let's connect.

who we support

Built for organizations that prioritize security, uptime, and compliance.

Z

Teams that want executive-level technology guidance and strategy for growth

Z

Operations that cannot afford disruption from unreliable or reactive IT

Z

Organizations ready to modernize operations with AI, automation, and data-driven insights

Z

Organizations handling sensitive data that need to stay secure and compliant without slowing down operations

Z

Organizations seeking outsourced IT support that strengthens their internal team or provides complete coverage when no internal team is in place

Forthright is the technology partner you should be working with

2024_CRN_MSP_500
Certified minority business
comptia-cybersecurity-trustmark