Security Awareness

Run a Short Security Awareness Session

Use free resources to discuss a situation your staff could face. Agree how to check a suspicious request and where to report it.

Content review: 2026-09-22 · Estimated effort: Low

Priority and effort are suggestions, not risk scores or deadlines. Check business impact, vendor instructions, licenses and obligations before making changes. Test before wider rollout.

Before you start

Before starting: provide a clear, non-punitive reporting route and name someone to respond. Do not use real credentials or personal information in training examples.

Put it into practice

  1. Use free CISA material to discuss suspicious messages, MFA, updates, and password managers at onboarding and in short refreshers.
  2. Demonstrate how to report suspicious messages or lost devices, including what to do after clicking a link or sharing information.
  3. Teach finance staff to verify changed payment details through a known separate channel. Tailor administrator and manager guidance to their decisions.
  4. Practice with clearly identified examples. If using simulations later, obtain authorization, protect privacy, and coach rather than shame. Click rates alone do not measure security.
  5. Verify: ask staff to locate the reporting route and explain how they would verify an unexpected payment request. Check that reports receive a useful response.

Use what you have

Tools and templates

“Included” tools require an eligible product or subscription. Options reviewed 2026-09-22; check current vendor terms.

Start without another software subscription

Use free CISA materials and the discussion worksheet with the team’s real reporting route.

What to account for: A paid training platform is optional. Free materials do not provide managed campaigns or prove safe behavior; someone must maintain the content and respond to reports.

Allow for equipment, storage and staff time. Eligibility details are linked below.

CISA Secure Our World materials

Free public education resources

Choose a tip sheet about phishing, MFA, passwords or updates. Use the worksheet to run a short discussion and practice your actual reporting route.

Limits: Some linked campaign material is archived; check dates and adapt examples. These resources are not a managed training platform or proof of staff competence.

Your information: Read or download public resources without uploading staff records. Keep attendance and training notes limited to what your organization needs.

Official instructions: CISA Secure Our World materials ↗

Download a working template

Open the Excel or Word file using your existing Microsoft Office license. Replace fictional entries, fill in the blanks and save your own copy. These manual worksheets have no macros, scoring or automatic verification.

  • Security awareness session worksheet (Word (.docx)) ↓

    Use the short facilitator agenda and clearly fictional payment-change example. Fill in your reporting route before the session.

    Fictional worksheet preview

    Fictional example: changed supplier bank details

    A message claims a regular supplier has changed bank accounts and requests payment today. It includes a new phone number for confirmation.

    • Which details would you verify before payment?
    • Where would you find a previously verified supplier contact, independent of this message?
    • Who can approve payment changes in your organization?

    Excerpt from a discussion exercise. The full worksheet includes the remaining prompt, suggested response, reporting routes and facilitator agenda. Do not send surprise messages or collect credentials.

Fictional worked example

Use these invented entries as a guide when filling in your worksheet. They are not a customer story or lab result. Record what you observe in your own checks.

A facilitator discusses a fictional supplier email requesting a change of payment details.

Use the Security awareness session worksheet template.

What to enter before testing

Facilitator / backup
Fill in the session leader and alternate
Where staff report suspicious messages or lost devices
Fill in the team’s approved reporting contact
Question or gap (Record useful follow-up table)
Confirm how to verify supplier changes using a trusted existing contact

How to verify

Tell participants the message is fictional. Ask them to describe the reporting route and independently verify a payment-change request using a known contact, not contact details supplied in the message. Check that the designated responder knows what happens next.

If the result is unexpected

If staff cannot find the route or the responder is unclear, fix those details and repeat the discussion. Do not shame participants, collect passwords or run surprise phishing. Attendance and a correct answer do not demonstrate behavior during a real attack.

Keep completed worksheets private. Leave out passwords, recovery keys and confidential messages. This site does not receive your edits, but a cloud editor or synced folder may send them to its provider.

Sources and review approach

These guides use selected NIST CSF 2.0 alignments. They are not official crosswalks or complete framework implementations. We have not tested these steps in your environment.

  • NIST CSF 2.0: PR.AT-01, PR.AT-02: general and role-specific learning
How this guidance is prepared