triox informatika

August 16, 2026 · Triox Informatika · 5 min read

The auditor doesn't ask whether you held a training session

They ask whether you can prove it. Hungary's NIS2 law and DORA both require employee security awareness—but little is said about how to demonstrate it. Training and measurement, in plain terms.

In brief

  • The vast majority of attacks don’t start at the system, but with an employee who clicks on something.
  • Hungary’s cybersecurity act and DORA, which applies to the financial sector, both require employee security awareness—but both also require that it be demonstrable.
  • No law prescribes specific software. A platform built for this—the best known is KnowBe4—is useful because it measures and documents what an annual presentation can’t.
  • The goal isn’t for employees to “pass the test.” It’s for them to stop at a suspicious email—and dare to speak up.

Annual security training typically looks like this: there’s a presentation in January, everyone signs an attendance sheet, and the binder goes back on the shelf. When an email that’s indistinguishable from the real thing arrives in March from the “supplier” with a new bank account number, nothing from that presentation helps anymore.

This isn’t the employees’ fault. A one-off talk doesn’t build a reflex—not to mention that attacks have changed a lot in the meantime. We wrote about this separately earlier: bad spelling as a warning sign is gone.

“People are the weakest link”—a cliché, but measurable

This sentence has been written so many times that it has lost its weight. Yet it has a practical consequence that is rarely discussed: if people are one of the carriers of risk, then that risk can also be measured.

Not by asking who paid attention during the training, but by looking at what people do in a realistic but harmless test situation. That’s the difference between “we held training” and “we know where we stand.”

If it isn’t measured, we don’t know whether it improved. If it isn’t documented, the auditor assumes it never happened.

What the law requires—and what it doesn’t

It’s worth being precise here, because there are a lot of misconceptions about this.

In Hungary, the NIS2 Directive was transposed by Act LXIX of 2024 (the Cybersecurity Act), which entered into force on January 1, 2025; for private businesses, the Hungarian supervisory authority is the SZTFH. In addition, the financial sector is subject to the DORA regulation—(EU) 2022/2554—which has applied since January 17, 2025.

The two regulations approach training differently:

Who it applies to What it says about training
Cybersecurity Act (NIS2) The organizations in scope—typically in critical and important sectors Cyber hygiene and training are among the required risk management measures. The implementing decree requires specific training, with a set number of hours, for senior executives and information security officers.
DORA Financial entities Article 13 explicitly requires an ICT security awareness program for all employees and senior management, with depth tailored to the role.

The training hours for executives and security officers are set out in Decree 17/2025. (VII. 24.) EM; it gives those appointed before the end of 2025 a transitional deadline. Exactly what applies to a given company depends on its sector and size—this question is worth clarifying with an expert; this article is not legal advice.

Two things are worth highlighting, though, because they hold for everyone in scope:

  • Neither regulation prescribes specific software. You can comply without an e-learning system.
  • Both, however, require that you can prove it. In an inspection, what counts isn’t intent—it’s the documentation.

What a platform adds

This is where the tool category comes in whose best-known representative is KnowBe4. It isn’t magic and it isn’t mandatory—it simply does the three things that are very hard to do by hand.

The first is regularity: short, recurring training units instead of a one-off talk, including content in Hungarian.

The second is the test situation: simulated phishing emails that are realistic but harmless. Someone who clicks doesn’t cause damage; they get feedback.

The third—and in an audit, the most important—is the trail: who completed what and when, and how the results changed. The platform’s built-in reports and log provide exactly this.

The security awareness program as a cycle: assessment, training, a simulated phishing test, then measurement. Anyone who struggles gets targeted retraining, and the cycle starts again. A by-product of the process is the documented trail that remains for the audit. 1. ASSESS Where we stand starting point 2. TRAIN Short, recurring not one talk a year 3. TEST Simulated email realistic, harmless 4. SCORE What changed who's where IF STUCK: TARGETED RETRAINING WHAT THE AUDITOR GETS who completed what and when—on record

Simulated phishing isn’t a trap

This is the most common objection, and it’s a fair one: nobody wants employees to feel they’re being set up. Experience shows that this depends on how it’s introduced.

What’s worth saying up front: the goal isn’t to shame employees, but for mistakes to surface in practice, not in a real attack. Someone who clicks should get immediate, matter-of-fact feedback—not a lecture. And results broken down by name shouldn’t end up on the bulletin board.

And the most important point: reporting should count as success, not a flawless record. If an employee is afraid of the consequences, they won’t speak up in a real attack either—and those are exactly the few hours lost during which the damage could still have been contained.

A simulation is good if, at the end, more people dare to speak up. Not if fewer people click.

How to get started

  1. Find out what applies to you. Sector, size, client base—these show whether the reason is the Cybersecurity Act, DORA, a client's vendor review or simply common sense. The answer determines how far you need to go.
  2. Measure a baseline. A first test covering everyone shows where the company stands today. Without it, there will be nothing to compare against later—and improvement is the best argument for continuing.
  3. Announce the rules in advance. That there will be tests, that their purpose is practice, and that reporting never leads to repercussions. This has to come from leadership, not from IT.
  4. Start with leadership. Not only because the stricter training requirements apply to them, but because they are also typically the target of impersonation fraud.
  5. Make it regular, and keep the reports. An audit or an insurance claim settlement asks for evidence after the fact. A report is only worth something if it still exists when nobody remembers the details anymore.

What to think through on the systems side

Technical and rollout details
  • Hungarian-language content: training only works if employees get it in their own language—the larger platforms, including KnowBe4, support this
  • Breakdown by role: finance and leadership need different scenarios than production
  • Letting simulated emails through the email system’s filters, so that the test actually arrives—this takes planning
  • Clarifying data protection: what data is generated about employees, who sees it, how long we keep it—this also goes into the internal policy and the employee privacy notice
  • A simple reporting path: a button in the email client that reports a suspicious email in one click
  • Keeping reports for as long as the audit requires, in a searchable form
  • Integration with existing protection: training complements the technical layer, it doesn’t replace it—without MFA, email authentication (SPF, DKIM, DMARC) and anti-phishing protection, it isn’t enough on its own

What not to expect from it

To be honest: an awareness program doesn’t solve everything. It won’t prevent zero-day vulnerabilities, it doesn’t replace backups, and it doesn’t replace multi-factor authentication. Anyone who hopes the click rate will drop to zero after training will be disappointed—that isn’t a realistic goal anyway.

What it does give you: a significant share of attacks stop at the employee, and for the rest, the report comes in hours sooner. With ransomware or payment fraud, those few hours decide how large the damage is.

Let’s look together at where your company stands now. At the end of the assessment you get a documented picture of the current state and a list of risks—including what an audit expects of you, and the few steps that improve things the most. Request an assessment, or read about our approach to security.

← Back to the blog