What each framework says about training
We summarize each text below and link the source. Where a point is our own reading, we say so.
NIS2: training for management and for staff
NIS2 (Directive (EU) 2022/2555) entered into force in January 2023. Member states had to transpose it by October 17, 2024, and national measures apply from October 18, 2024 (NIS2 Directive text, December 2022). Scope and obligations depend on the entity's sector, size and national law.
Article 21 requires essential and important entities to take appropriate and proportionate measures. Its list includes basic cyber hygiene practices and cybersecurity training (Article 21(2)(g)), and policies and procedures to assess the effectiveness of risk-management measures (Article 21(2)(f)) (NIS2 Article 21, December 2022).
Article 20(2) adds a separate duty for management. Member states must require members of management bodies to follow training, and must encourage entities to offer similar training to employees on a regular basis (NIS2 Article 20, December 2022). The stated purpose is to help managers identify risks and assess risk-management practices and their impact on services.
For some digital and managed service providers, Commission Implementing Regulation (EU) 2024/2690 of October 17, 2024 sets technical and methodological requirements. ENISA published technical implementation guidance for that regulation (ENISA, June 2025). Check whether it and any national or sector rules apply to you.
Our reading: NIS2 names training but leaves format, frequency and evidence to the entity and to national law.
DORA: compulsory training scaled to each role
DORA (Regulation (EU) 2022/2554) entered into force on January 16, 2023 and applies from January 17, 2025 (European Parliament summary of Regulation (EU) 2022/2554, December 2022). It covers nearly all financial entities. Critical ICT third-party providers fall under a separate oversight framework with Lead Overseers, not under the same obligations.
Article 13(6) tells financial entities to include ICT security awareness programmes and digital operational resilience training as compulsory modules in their staff training schemes. These apply to all employees and to senior management, at a level of complexity commensurate with the remit of their functions. Third-party ICT providers are included where appropriate (DORA Article 13, December 2022).
We read "commensurate with the remit of their functions" as a reason to differentiate content by role. A relationship manager who handles wire transfers faces different social engineering exposure than a back-office analyst, and the training should reflect that.
ISO 27001:2022: competence, awareness and Annex A 6.3
ISO/IEC 27001:2022 (October 2022) covers training in three places. Clause 7.2 asks organizations to determine the competence needed from people whose work affects information security performance, and to ensure it through education, training or experience. Where applicable, they take actions to acquire that competence, evaluate whether the actions worked, and keep documented information as evidence (High Table summary of clause 7.2).
Clause 7.3 covers awareness. Annex A control 6.3 covers information security awareness, education and training (Advisera on control 6.3).
A completion log covers the training record. It does not by itself show how the organization determined the competence it needed, or whether the training closed the gap. Clause 7.2 asks for both.
NYDFS 23 NYCRR 500: annual training that includes social engineering
The New York Department of Financial Services Cybersecurity Regulation requires periodic cybersecurity awareness training, at a minimum annual, that includes social engineering. It covers all personnel. The content must be updated to reflect risks the covered entity identified in its risk assessment (23 NYCRR 500.14(a)(3), Cornell LII, amended November 2023).
The update requirement is where a static module falls short. A course reassigned each year without changes would not show the link to the risk assessment. We recommend keeping a log of content changes and the risk findings behind them.
HIPAA: a workforce-wide program with no set frequency
The HIPAA Security Rule requires covered entities to implement a security awareness and training program for all members of the workforce, including management. Four addressable specifications follow: security reminders, protection from malicious software, log-in monitoring and password management (45 CFR 164.308(a)(5), Cornell LII, 2026).
The rule sets no frequency and does not mention simulations. We recommend documenting how often you run reminders and content updates, and why you chose that cadence.
SOC 2: CC1.4 and competent people
SOC 2 criterion CC1.4 asks an organization to show a commitment to attract, develop and retain competent individuals in line with its objectives. Its points of focus include evaluating competence and addressing shortcomings, and providing training to maintain technical competencies (AICPA Trust Services Criteria, revised points of focus 2022, as summarized by hicomply).
CC1.4 sits in the control environment and speaks about competence in general terms. We recommend keeping competence evaluations and follow-up records next to training logs.
Summary: what each framework asks for
The table compares the six texts. The last column is our recommendation, not a legal requirement.
NIS2 and HIPAA name training with little detail on format or frequency. NYDFS adds an annual minimum, social engineering content and updates based on the risk assessment.
DORA ties content to the remit of each function. ISO 27001 and SOC 2 tie training to competence and ask whether it worked.
Why a completion log may not be enough
Audits and post-incident reviews tend to ask different questions. An audit typically checks that a control exists and operates.
A review after an incident typically asks whether the control matched the risk that materialized. This is our view, not wording from the texts above.
The Verizon 2026 Data Breach Investigations Report analyzed more than 22,000 confirmed breaches (Verizon DBIR, 2026). It found the human element in 62% of breaches, up from 60% in the 2025 report. We use the figure as context for why training records matter, not as proof that any training model works.
Five records that make a training program easier to defend
These are our recommendations. No single text lists all five, and the right documentation depends on the framework and the entity.
1. A content update log
Record when you review training content and why you change it, with the risk finding or incident behind each change. NYDFS 500.14(a)(3) asks for content that reflects the risk assessment, and the log shows how you did it.
2. Role-differentiated training records
Record which content each role received and why. DORA Article 13(6) ties complexity to the remit of each function, and ISO 27001 clause 7.2 starts from the competence each role needs.
3. Simulation results over time
Review simulation results over time to guide training. Before you tie results to individuals, assess the data protection rules that apply, such as the GDPR, and decide who may see the data.
4. A remediation path for repeated exposure
Define what happens when the same risk repeats, for example targeted follow-up training or support from the security team. Document the path, so you can show that findings lead to action. ISO 27001 clause 7.2 asks organizations to evaluate whether their actions worked.
5. Management training records with topics
NIS2 Article 20(2) treats management training as its own duty. Keep a record of who attended, when, and which topics were covered, separate from staff records.
How we build programs that produce this evidence
We recommend four habits for programs that need to show more than completion.
Measure continuously. Annual training with quarterly simulations provides more evidence than annual training alone. Behavioral signals such as simulation results, reporting rates and repeat patterns show change between audit dates.
Set behavioral baselines. Record where behavior started by role and team, and track where it is now. That change over time gives you an answer when a regulator, an auditor or the board asks whether training had an effect.
Connect content to risk. Review content when risks change, and log the reason. NYDFS requires this link explicitly, and ISO 27001 clause 7.2 asks organizations to evaluate whether their actions worked.
Give management its own track. NIS2 Article 20(2) requires management bodies to follow training, so keep their records and topics apart from staff records.
The frameworks above use different words for training: compulsory modules, cyber hygiene, competence, risk-based updates. Evidence beyond a completion log makes each of them easier to support.
At Zepo, we connect real-time detection signals with simulations, adaptive training and analytics. If you want to see how that supports the records above, talk to us.