The topics worth teaching every employee are phishing and social engineering (including invoice and payment fraud), passwords and multifactor authentication, device and remote working habits, malware and ransomware, data protection, and how to report a problem fast. Everything else is a refinement of those six. What separates a program that changes behavior from one that ticks a box is how you tailor the topics to each role, how often you deliver them, and whether people feel safe reporting mistakes.
This guide sets out each topic, what to actually teach under it, and how to fit the program to a UK organization, using guidance from the NCSC, the ICO and sector bodies.
TL;DR
- Start with six core topics: phishing and social engineering, passwords and MFA, devices and remote work, malware and ransomware, data protection, and incident reporting.
- Deliver in small, frequent sessions tied to people’s real jobs, not one long annual video.
- Make reporting safe. The NCSC says blame discourages people from speaking up, and many incidents are only ever spotted by staff.
- Finance, helpdesk, IT admins and executives need extra, role-specific modules.
- Measure completion and behavior, then feed what you learn into your wider security program.
Table of Contents
- The six core topics, and what to teach under each
- Phishing and social engineering
- Passwords, credentials and multifactor authentication
- Devices, remote work and Wi-Fi
- Malware, ransomware and suspicious links
- Data protection and insider risk
- Incident reporting: the topic that makes the rest work
- Tailoring topics to roles and sectors
- How to deliver it so it sticks
- Where training fits with the rest of your defenses
- Our perspective
- How Zero Through can help
- FAQ
- Sources
The six core topics, and what to teach under each
Published lists differ in length, from nine topics in NIST SP 800-50 (as summarized by a security training vendor) to a dozen in vendor blogs. They overlap heavily. The NCSC’s free Top Tips for Staff package, which takes under 30 minutes, boils the essentials down to four areas: strong passwords, securing devices, defending against phishing, and reporting incidents. Add malware and data protection, which UK regulators expect, and you have a sound core curriculum.
| Topic | What employees should be able to do afterward |
|---|---|
| Phishing and social engineering | Spot a suspicious message or call, and report it without delay |
| Passwords and MFA | Use unique credentials, a password manager and phishing-resistant sign-in |
| Devices, remote work and Wi-Fi | Lock, update and protect devices wherever they work |
| Malware and ransomware | Handle links, attachments and downloads safely |
| Data protection | Handle personal and sensitive data correctly and recognize a breach |
| Incident reporting | Know exactly who to tell, how, and that it is safe to do so |
Phishing and social engineering
This is the topic every ranking list leads with, and with good reason. It is also the one where content goes stale fastest, so refresh examples often.
What to teach
- How phishing arrives by email, text, phone call, QR code and collaboration tools, and how attackers use urgency, authority and curiosity.
- Pretexting by phone: someone posing as a colleague, supplier or IT helpdesk.
- AI-generated messages and voice cloning, which remove many of the old tell-tale spelling mistakes. Teach people to verify through a second channel rather than judge by how polished a message looks.
- A simple habit: pause, check the sender and the request, verify out of band, report.
The NCSC’s phishing guidance says training should reassure users they will not get in trouble for reporting a phishing incident, and that this message needs buy-in from HR, support and senior management. It also notes that some organizations have participants write their own phishing emails, which gives a much richer view of the influence techniques attackers use. If you want a deeper look at how these attacks play out across borders and time zones, our piece on phishing tactics for international business teams covers it.
Business email compromise and invoice fraud
Finance staff, PAs and anyone who approves payments need a dedicated module. The Australian Cyber Security Centre’s personnel security guidelines list the warning signs worth teaching: an unexpected request to change banking details, an urgent payment request or threats if payment is not made, an unexpected payment request from someone senior, and a sender address that does not match the organization’s name. These signs apply in any country.
Turn them into a rule: no change to bank details is actioned without a call-back to a number you already hold. For worked examples of how fake invoices look and how teams stop them, see this guide to invoice phishing scams.
Passwords, credentials and multifactor authentication
Passwords remain a prime target, especially for accounts that reach sensitive information, handle money or administer systems. The NCSC phishing guidance advises reviewing password policies to reduce reuse between home and work accounts, and recommends MFA, password managers that recognize real websites and do not autofill on fake ones, single sign-on, and alternatives such as biometrics or smartcards.
What to teach
- One unique password per account, stored in an approved password manager.
- Why MFA matters, and why a prompt you did not trigger is a warning, not an annoyance.
- Never sharing codes with anyone, including someone claiming to be IT.
- What happens at your organization when someone forgets a password or loses a phone.
The last point matters most for helpdesk teams. After the 2025 M&S and Co-op incidents, the Retail Employers’ Confederation advised a call-back to a pre-registered phone number for every password or MFA reset, a short shared secret for privileged users, scripted questioning so agents stay consistent under pressure, and a move from SMS or voice codes to app-based or FIDO2 hardware keys. That is a training topic as much as a technical control. If you are deciding what to roll out next, read our comparison of passkeys vs passwords.
Devices, remote work and Wi-Fi
Hybrid work moves the office perimeter into kitchens, trains and airports. Your training should translate that into a few concrete habits.
What to teach
- Keep devices locked and updated, and accept update prompts promptly.
- Physical care. The NCSC’s advice for end users says not to leave a device unattended in an insecure place, and to lock it away or keep it on you where possible.
- Network choices. The NCSC’s connecting securely exercise notes that using public Wi-Fi or insecure networks on mobile devices can let attackers on the same network intercept or modify data. Teach staff to use the organization’s approved remote access method and to avoid signing in to sensitive systems over open networks.
- Reporting a lost or stolen device immediately, at any hour, to a number they can find without logging in.
- Keeping work data on approved devices and apps only, if you run a personal device policy.
Our guides to remote work security and endpoint security for a global remote workforce go into the technical controls that sit behind these habits.
Malware, ransomware and suspicious links
Staff do not need to understand malware families. They need to know what behaviors invite them: opening unexpected attachments, plugging in unknown USB drives, installing software outside the approved list, and ignoring security warnings.

The ICO’s ransomware guidance says relevant staff should have baseline awareness of attacks such as phishing, and that organizations should consider additional, specific training for staff responsible for IT infrastructure and security services. It also advises tailoring the NCSC’s phishing guidance to your organization’s context.
Two practical additions:
- Teach what a ransomware incident looks like on screen (renamed files, a ransom note, a machine that suddenly slows), and the first step: disconnect and call the incident number, do not try to fix it.
- Teach IT staff more: patching, backup testing and privileged account hygiene.
Data protection and insider risk
For UK organizations this is not optional. The ICO’s training and awareness toolkit warns that without a training program supported and overseen by senior management, staff may not understand how data protection applies to their role, which risks breaching articles 5(1) and 5(2) of the UK GDPR. It expects induction training for all staff before they access personal information and within one month of starting, with refresher training at appropriate intervals. It applies regardless of contract status or grade, and it suggests monitoring completion and removing access for people who miss refreshers.
What to teach
- What counts as personal data and special category data in your business.
- Sending data securely, and double-checking recipients before sending.
- Clear desk and screen habits, and the risk of conversations overheard in public.
- What a personal data breach looks like (a misdirected email counts), and that it must be reported internally straight away so the organization can assess it.
- Insider risk, framed as care and reporting rather than suspicion: leavers, excessive access and unusual requests.
Physical security belongs here too. Tailgating, visitor badges and who may enter server rooms are real topics for offices and retail sites. If your team manages premises, this overview of access control types helps match physical measures to NCSC and NPSA guidance.
Incident reporting: the topic that makes the rest work
Every other topic fails if people do not tell you when something goes wrong. The NCSC’s 10 Steps guidance states that many incidents are only ever detected by people, and that people who trust the organization are more likely to report suspicions, which makes early detection possible. It advises not stigmatizing mistakes or singling out individuals or teams for blame, because that makes people less willing to report in future.
What to put in place
- One obvious reporting route (a button, a mailbox, a phone number) that appears in every training module.
- A route that works if a device is compromised. The NCSC phishing guidance notes users may be unable to use normal communication channels, so they need to know alternatives in advance.
- A thank-you for every report, including false alarms.
- Leaders who follow the rules themselves. The NCSC warns that if senior people visibly ignore the messages, the campaign’s effectiveness is quickly undermined.
Tailoring topics to roles and sectors
A single course for everyone is a starting point, not a program. The NCSC’s Cyber Assessment Framework principle B6 asks for training that gives each job role appropriate skills, based on how people really work with systems, with ongoing reminders and top-up training. Its “achieved” criteria include training paths for everyone from the most senior to the most junior, tracking and refreshing each person’s training, and routinely evaluating whether the activity is reaching people and working.
| Audience | Add these topics |
|---|---|
| Finance and accounts payable | Invoice fraud, payment verification, bank detail changes |
| Helpdesk and IT admins | Identity verification for resets, privileged access, social engineering by phone |
| Executives and PAs | Targeted impersonation, deepfake voice and video, travel security |
| HR and recruitment | Malicious CVs and attachments, handling candidate data |
| Retail and front-line staff | Till and device security, handling suspicious calls, shared logins |
| Healthcare staff | Patient data handling, role-based information governance |
| Legal teams | Client confidentiality, wire fraud around completions, secure file sharing |
| Charities and volunteers | Basic hygiene for volunteers using personal devices, donation fraud |
NHS England’s Data Security and Protection Toolkit guidance gives a useful method for any sector: run a training needs analysis. It means deciding what level of understanding each staff group needs and what training achieves it. The guidance says the analysis should cover all staff roles, be endorsed and resourced by senior leadership, and be reviewed as requirements, feedback or the organization change. It also notes that using a range of approaches usually improves participation and comprehension.
How to deliver it so it sticks
The NCSC recommends small, frequent chunks rather than an hour once a year, and warns against reusing the same video year after year, which signals that the organization does not care much. It also says trainers should know the subject and relate it to the trainees’ everyday work, and that messages should be relevant, achievable and positive. Fear and threat-based messaging, it says, does not work well and can backfire.
A workable annual rhythm:
- Induction: the core six topics in under an hour, completed before access to personal data and in any case within a month, in line with the ICO’s expectation.
- Monthly or quarterly micro-lessons: five minutes on one live threat, using a real, recent example.
- Phishing simulations: the BCS awareness programme article suggests they can show how susceptible the business is and highlight repeat clickers and high-risk departments. Use the results to offer help, not to name and shame.
- Role modules: the table above, delivered when someone joins a team or changes role.
- Events and communications: the BCS also suggests roadshows, lunch and learns, newsletters, posters and intranet pages. Awareness, it argues, is about focusing attention, so keep content short and memorable.
Measure completion, reporting rates, time to report and simulation trends, and review the program against your wider risk picture. Our cyber security risk guide shows how to connect training to the risks you actually carry.
Where training fits with the rest of your defenses
Training reduces the number of incidents that start with a person. It does not remove them. Someone will eventually click, so you also need to detect and contain what follows. That means monitoring, logging and a tested response plan. Our article on cyber threat detection for UK businesses explains what that looks like, and the NCSC phishing guidance itself recommends a security logging system to catch incidents users are not aware of.
If you must evidence your controls to customers or regulators, see how Cyber Essentials, ISO 27001 and SOC 2 treat staff awareness.
Our perspective
Most awareness programs we see fail the same way: they are built from a generic topic list and never connected to how the business actually operates. A finance team in London, a clinic network and a retailer with fifty sites do not share the same risks, and a one-size course tells all of them the same thing.
Our approach is to start with the findings. A security audit or a penetration test shows which real weaknesses exist, such as a helpdesk reset process that can be talked around, or users who reuse credentials. We then explain those findings in plain terms and turn them into an actionable roadmap, so the training topics are chosen because they close a gap you have, not because a list says so.
Training also works best when something is watching behind it. Staff will report suspicious activity, and a managed SOC, SIEM or MDR service means those reports and the signals nobody noticed are acted on quickly. That is why we pair awareness with detection and response, and why we scale support across locations as your organization grows.
Shirish
How Zero Through can help
If you want training topics grounded in your real exposure, we can start with a IT security audit to identify what your people and processes are most likely to get wrong, then support you with phishing simulation, user awareness training and ongoing monitoring across your sites. Our Global IT Support is built for multi-location businesses in regulated sectors such as financial services, healthcare, retail and law.

We publish no fixed prices, because scope depends on your size and sectors. Contact us through our site to discuss your needs.
FAQ
What is the most important security awareness topic?
Phishing and social engineering, because they are the route into most incidents and the one topic every employee faces daily. Pair it with a clear way to report suspicious messages, since the NCSC notes that reassurance about not getting into trouble for reporting is central to training.
How long should security awareness training take?
The NCSC’s free Top Tips for Staff takes under 30 minutes and covers passwords, devices, phishing and reporting. For ongoing training, the NCSC advises small, frequent chunks rather than a single long annual session.
How often should employees be retrained?
UK data protection guidance expects induction training before staff access personal data and refresher training at appropriate intervals. In practice, combine an annual refresher with short lessons through the year and extra modules when someone’s role changes.
Should training be different for different roles?
Yes. The NCSC’s Cyber Assessment Framework asks for training suited to each job role, and NHS England’s guidance recommends a training needs analysis covering all roles. Finance, helpdesk, IT and executive teams usually need extra topics beyond the core six.
Sources
- NCSC: Top Tips for Staff
- NCSC: Phishing attacks, defending your organisation
- NCSC: 10 Steps to Cyber Security, engagement and training
- NCSC: Cyber Assessment Framework, principle B6
- NCSC: Advice for end users
- NCSC: Connecting securely micro exercise
- ICO: Ransomware and data protection compliance
- ICO: Training and awareness
- NHS England: Training needs analysis and delivery
- Retail Employers’ Confederation: Retail cyber storm guidance
- BCS: How to build a successful information security awareness programme
- Australian Cyber Security Centre: Guidelines for Personnel Security
- Invoice phishing scams
- Access control types


