Essentials

Employee Training 101: Creating a Human Firewall

You can have the best locks in the world, but if your employee opens the door for the pizza guy (who is actually a hacker), you are compromised.

By SecureBusinessHub Editorial, International cybersecurity desk — · 5 min read

You can have the best locks in the world, but if your employee opens the door for the pizza guy (who is actually a hacker), you are compromised.

Around 90% of breaches start with human error, and traditional security training is both boring and ignored — which makes that figure make sense. The human element is the weakest link precisely because attackers target people, not machines: phishing, weak passwords, and social engineering all aim at the person, not the firewall.

The psychology behind the click

Attackers exploit urgency, fear, and the authority of seemingly senior figures. When a "CEO" emails asking for an urgent wire transfer, most employees default to wanting to help rather than questioning the request. Effective training is really about interrupting that reflex — giving people permission to slow down and check, even when the message claims to come from the top.

Don't lecture. Simulate.

A PDF policy document does nothing. Use phishing simulations instead. Send fake phishing emails to your team and see who clicks. Reward those who report it, and quietly work with those who click. Better still, make it engaging: gamified simulators, short interactive puzzles, and leaderboard rewards turn awareness into something people actually participate in rather than a compliance box they tick.

The "slow down" rule

Teach staff that urgency is a red flag. If an email screams "URGENT ARREST WARRANT" or "PAYMENT OVERDUE IMMEDIATELY," the right move is to stop, breathe, and call the sender on a number you already have. The core habits to drill are simple: spotting spoofed email addresses, verifying any request for sensitive information through a second channel, and using a password manager for every account — the rules worth writing into your acceptable use policy so they are expected, not optional.

Limit the damage a single account can do

Not all human risk is accidental. A disgruntled former employee or a malicious insider already has the keys to the system. The defense is the principle of least privilege: people should have access only to the data their current role needs, and that access should be revoked the moment they leave. Pair that with a strong password and MFA policy so that even a stolen or shared credential doesn't hand an attacker the run of the business.

Create a safe culture

If an employee clicks something bad, they should feel safe telling you immediately. If they're afraid of being fired, they'll hide it, and the ransomware will spread. Build a "see something, say something" environment where reporting a mistake is rewarded, not punished — the single cheapest security control most small businesses never switch on.

Micro-learning: the 5-minute approach

Long annual seminars are ineffective for busy teams. Send a 90-second video or a single quiz question to your Slack or Teams channel weekly. Short, regular doses stick better than a full day of content once a year. Good topics: how to read a URL, and the danger of LinkedIn connection requests from strangers.

Measuring your human firewall

Track report rates, not just click rates. An employee who clicks a simulation but reports it is doing the right thing. The real metric is whether your team is flagging suspicious emails before anything happens — so celebrate those catches, and treat a rising report rate as the clearest sign your training is actually working.

NIS2 requirements: the second regime to know about

Data protection law is not the only European regime a business gets asked about. The NIS2 directive sets baseline cybersecurity and incident-reporting obligations for organisations in a defined list of sectors, and it is the source of most of the security questions that now arrive attached to contracts. The two regimes cover different ground: data protection law governs personal data and what people can ask you to do with it, while the NIS2 requirements govern the security and resilience of network and information systems, whether or not personal data is involved. A single incident can engage both, on separate clocks, to separate authorities.

The directive applies to organisations in its listed sectors that are at least medium-sized, meaning broadly fifty or more employees or turnover and balance sheet above ten million euros. That size rule puts most small businesses outside its direct scope, and the honest answer for a ten-person company is usually that the directive does not regulate it. What the size rule does not do is keep the requirements away, because one of them is supply chain security: organisations inside scope are expected to consider the security practices of their direct suppliers, and the way that expectation shows up in the world is as a questionnaire in your inbox.

The measures the directive names are a reasonable checklist for any business, which is why they are worth knowing even when they do not apply to you directly. They cover risk analysis and written security policies, incident handling, business continuity and backups, supply chain security, secure development and vulnerability handling, basic cyber hygiene and training including for management, encryption and access control policies, and multi-factor authentication. Reporting is staged and fast for the organisations it covers: an early warning within twenty-four hours of becoming aware of a significant incident, a fuller notification within seventy-two hours, and a final report within one month.

Because the directive is national law in each member state rather than a single rulebook, the details of scope, thresholds and reporting differ by country. For a fuller explanation of the instrument itself, see our guide to what the NIS2 directive is, and for the supplier side of the supply chain obligation, our walkthrough of vendor risk assessment. The reporting clocks that run alongside data protection deadlines are covered in data breach notification requirements.

Frequently asked questions

Does NIS2 apply to a small business?

NIS2 generally applies to organisations in its listed sectors that are at least medium-sized, meaning broadly fifty or more employees or turnover and balance sheet total above ten million euros. Most smaller businesses fall outside its direct scope, unless a member state has specifically designated them or they sit in one of the size-independent categories such as DNS service providers or trust service providers. Being outside scope does not stop the directive reaching you through customers who are inside it.

What is the difference between GDPR and NIS2?

GDPR governs personal data: what you may collect, why you may hold it, and what rights people have over it. NIS2 governs the security and resilience of network and information systems in specific sectors, whether or not personal data is involved. One incident can engage both regimes at once, on separate reporting clocks and to separate authorities.

How long do you have to report a data breach?

Under the European model, a personal data breach is reported to the supervisory authority without undue delay and, where feasible, within seventy-two hours of becoming aware of it, and affected individuals are told without undue delay where the risk to them is high. Organisations in scope of NIS2 carry a separate obligation: an early warning within twenty-four hours, a fuller notification within seventy-two hours, and a final report within one month.

Does a small business need a data protection officer?

Under GDPR a data protection officer is required where the organisation is a public authority, where its core activities involve regular and systematic monitoring of people on a large scale, or where its core activities involve large-scale processing of special category or criminal offence data. Most small businesses meet none of those tests and are not required to appoint one, though naming someone internally as the contact for privacy questions is worth doing regardless.

What should a small business do when a client's security questionnaire asks about NIS2?

Answer what you actually do rather than what you think the client wants to hear. The questions usually cover written security policies, incident handling and how fast you would notify them, multi-factor authentication, access control when staff join and leave, backup and recovery arrangements, and which of your own subprocessors touch their data. Gaps are common, and disclosing one with a date for closing it lands far better than an answer that does not survive the follow-up question.

Do these rules reach a business based outside the EU?

They can. GDPR reaches organisations outside the EU that offer goods or services to people in the EU or monitor their behaviour, and other regions have their own regimes with their own triggers. NIS2 obligations follow the sectors and the member states that transpose it, but its supply chain expectations travel through contracts, which is how they reach suppliers anywhere in the world.

Related reading