Let’s talk
Wondering how this plays out in your organisation? Get in touch — I answer personally.
Short answer
Training under Article 8e of the Polish KSC Act is completed by the head of the entity. In a collective body each of its members is the head of the entity (Article 2(8a)), so the training covers the whole board, not only its president. In my assessment, designating a responsible person under Article 8c(2) does not change this. Beyond the board, Article 8e(1) names one more role. It is the person entrusted with the head’s duties in the area of cybersecurity. Entrustment adds that person to the circle of those trained and leaves the board members in it.
For everyone else the obligation is built differently. The head of the entity ensures that the entity’s staff are aware of cybersecurity duties and know the entity’s internal rules in that area (Article 8d(4)). This baseline covers all staff. Articles 8 and 8d do not specify positions or frequency. Broader preparation is worth providing to the people who perform the tasks under Articles 8 and 11, to the people designated for contact (Article 9) and to the owners of system elements such as HR and procurement. Annex 4 for an important entity that is a public entity (point 17) and Regulation 2024/2690 for the entities under Article 8b(1) (point 8.2.1) describe the circle of those trained more specifically.
Why the question comes up at all
Two training obligations in the same Act are built in completely different ways. The first has an addressee, a cycle and a proof. The head of an essential or important entity completes training once each calendar year, and participation in it is documented (Article 8e). The second obligation has neither a cycle, nor a list of people, nor a separate provision on documenting participation. Cybersecurity education for the entity’s staff is one of the elements of the information security management system (Article 8(1)(2)(i)), alongside basic cyber hygiene practices (point (j)). According to the Minister of Digital Affairs, staff education should be ongoing and take into account staff duties within the system (Q&A 3.8). The exceptions are an important entity that is a public entity (Annex 4) and the entities under Article 8b(1) (Regulation 2024/2690), for which the circle of those trained is described more specifically, and the Regulation also requires regular training.
The second source of doubt lies in reading Article 20(2) of Directive (EU) 2022/2555 on its own. Under it, Member States “shall ensure that the members of the management bodies of essential and important entities are required to follow training”. As regards employees, the provision says only that Member States “shall encourage essential and important entities to offer similar training to their employees on a regular basis”. Anyone who stops at that paragraph may treat training beyond the board as voluntary. Article 21(2)(g) of the directive, however, includes “basic cyber hygiene practices and cybersecurity training” among the measures that essential and important entities have to implement. The KSC Act writes staff education into the catalogue in Article 8(1)(2)(i) and adds the head’s duty under Article 8d(4). Training beyond the board is therefore voluntary neither under the directive nor under the Act.
The third reason is organisational. The question about the circle of people usually comes up once training for the head of the entity is already in the calendar. That is when it turns out there is no ready list for the rest of the organisation.
Remember
The organisational chart will not replace a list of the roles to be trained, because duties under the Act are distributed differently than positions.
What to establish before deciding
Who besides the head of the entity is named in the Act
Article 8e(1) names two roles. They are the head of an essential or important entity and the person entrusted with the head’s duties in the area of cybersecurity. Both are subject to the same annual cycle and the same scope set out in paragraph 2. Both must have documented participation in training.
The second role is often overlooked, because in many organisations it exists in fact rather than formally. Someone runs the subject day to day and prepares materials for the board, but the entrustment has never been recorded. Entrustment requires that person’s consent and does not relieve the head of the entity of responsibility (Article 8c(3)). The practical conclusion is simple. If the entrustment exists, the entrusted person joins the circle of those trained and the board members remain in it. If it does not, the first thing to settle is whether it should.
The head of the entity is the head of the unit within the meaning of the Accounting Act (Article 2(8a) of the KSC Act). In a collective body all of its members are the head of the entity (Article 3(1)(6) of the Accounting Act). Training under Article 8e is therefore completed by every board member, not only by the president of the board. In my assessment, designating a responsible person under Article 8c(2) does not change this, because that provision concerns responsibility and the circle of those trained is set by Article 8e(1). In a public finance sector unit the head of the entity is the head of that unit (Article 2(8a)).
The scope of training for these two roles is set out in What should NIS2 training for the board cover?. That scope covers the performance of the obligations for which the head of the entity bears responsibility (Article 8e(2)). It is not a programme for specialists.
Who performs the tasks under Articles 8 and 11
Involvement in the tasks under Articles 8 and 11 is the most useful criterion for selecting groups. The Act uses this criterion for a different purpose, namely the criminal record check. Before starting those tasks, the person who is to perform them presents to the entity information from the National Criminal Register confirming no conviction for offences against the protection of information (Article 8f(1)). The head of the entity admits that person to the tasks after receiving that information. The requirements of paragraphs 1 and 2 are deemed met where the person holds a valid security clearance granting access to classified information at the “confidential” level or higher (Article 8f(3)). The provision does not require a list, but meeting it is easiest on the basis of a list of named individuals.
That same list is the natural starting point for a training plan. It covers the people who perform the tasks of the information security management system and those involved in handling and reporting incidents. In a medium-sized organisation these are usually people from several different departments, not a single team.
Two things are worth checking at this point. Whether the list covers the people who actually perform the activities, not only the formal owners of areas. And whether it covers deputies as well, because incident duties run regardless of holidays and staff turnover.
The people designated for contact with the national cybersecurity system
An essential or important entity designates at least two people responsible for maintaining contact with the entities of the national cybersecurity system (Article 9(1)(1)). An entity that is a micro or small enterprise and an important entity that is a public entity designate at least one person (Article 9(2) and (3)). Article 73a(1)(6), however, does not exempt from a fine the head of an important entity that is a public entity who has not designated two people. Such an entity is therefore safer designating two people. Once entered in the register, the entity begins using the ICT system through which it submits its reports (Article 9(1)(4)).
The Act does not provide a separate training obligation for these people. The task itself, however, determines the scope of preparation. It is about operating the reporting system and about the deadlines counted from detection of a significant incident. This is a practical assessment, not the content of a provision. It is an assessment that is easy to defend, though, because a contact person without that knowledge will not perform the task they were designated for.
Which roles follow from the catalogue of measures itself
The Act lists the elements of the information security management system in Article 8(1)(2). Each of them has an owner in the organisation, and a substantial part of them sits outside the IT department. The table assigns the elements to roles and indicates what the preparation of those people covers. It is a practical assessment based on the typical structure of a medium-sized and large organisation, not a catalogue that follows from the provision.
| Element of the system (Article 8(1)(2)) | Who usually decides | What the preparation covers |
|---|---|---|
| Human resources security (point (d)) | HR department and line managers | Hiring, change of role and departure of an employee; the criminal record check (Article 8f) before the head of the entity admits a person to tasks under Article 8 or Article 11 |
| Security and continuity of the ICT supply chain (point (e)) | Procurement and contract owners | Supplier assessment criteria under Article 8(2) and security clauses in contracts |
| Security in the acquisition, development, maintenance and operation of the system (point (b)) | Development and maintenance teams, project leads | Security requirements in the project and testing of the system before go-live |
| Asset management and access control policies (points (m) and (n)) | Access administrators, managers approving requests | Least privilege, access reviews, revoking rights after a change of role |
| Business continuity and recovery plans (point (f)) | Process owners | The role of the process in providing the service, the conditions for invoking the plan, taking part in tests |
| Staff education and cyber hygiene (points (i) and (j)) | The head of the entity (Article 8d(4)); the audience is all of the entity’s staff | Recognising events, the internal reporting path, the rules in force |
The table shows why a list of groups built from the organisational chart is usually incomplete. The first three rows concern departments that are not the first to come up in a conversation about cybersecurity, yet they are responsible for decisions that are hard to reverse after the fact.
Where the boundary of “all staff” runs
The information security management system is implemented in the information system used in processes that affect the provision of the service (Article 8(1)). That narrows the scope of the management system itself. The head’s duty under Article 8d(4) is framed more broadly and speaks of the entity’s staff.
The boundary of the system therefore does not mark the boundary of the awareness duty. The Minister of Digital Affairs indicates in the Q&A on the amendment that the entity should take care that its staff understand cyber threats regardless of their role in the organisation (question 3.3(i)). The boundary of the system may affect the depth of a person’s preparation. It does not decide whether a member of staff is covered by the awareness duty.
The Act speaks of the entity’s “staff”, not of employees. People working on a basis other than an employment contract use the same systems and make the same mistakes. The dividing criterion is the scope of tasks and access, not the type of contract.
An important entity that is a public entity has a different point of reference
An important entity that is a public entity does not apply Article 8(1); it applies the requirements of Annex 4 to the Act (Article 8(3)). The same provision covers the part of important entities from the higher education and science system indicated in it that are not research organisations. This applies to public tasks carried out using information systems. On training, the annex is more specific than the general provisions.
Part I of the annex lists training for people involved in the processing of information as a measure that minimises the occurrence of incidents (point 17). It also names the topics that the training is to cover in particular. These are the types of cyber threats, basic cyber hygiene practices, responding to an incident and awareness of the consequences of breaching information security rules. A separate point requires cyber hygiene practices to be applied by employees who use information systems, including by the head of the entity (point 14). The system is reviewed at least once a year or without delay in the situations listed in Part III of the annex.
For this group of entities the answer is therefore closest to being ready-made. The circle is marked out by involvement in the processing of information, and the core topics are written out in the annex.
Entities under Article 8b apply Regulation 2024/2690
The entities listed in Article 8b(1) (among others DNS service providers, cloud computing service providers and managed service providers) apply within their system the measures set out in Commission Implementing Regulation (EU) 2024/2690. According to the Minister of Digital Affairs, they apply them only to the activity covered by the Regulation (Q&A 3.47). The awareness raising programme covers employees, including members of management bodies, and where appropriate also direct suppliers and service providers (Annex, points 8.1.1 and 8.1.2). The programme is to be scheduled over time so that activities are repeated and cover new employees (point 8.1.2(a)). The entity also identifies employees whose roles require security-relevant skills and expertise and ensures that they are regularly trained (point 8.2.1). It also trains employees moving to such positions or roles (point 8.2.4).
What to do about the provider’s staff
An entity performs its tasks through its own structures responsible for cybersecurity or under a contract with a managed cybersecurity services provider (Article 14). The Minister of Digital Affairs indicates in the Q&A on the amendment that the conjunction “or” allows the entity to combine both models and outsource only part of the tasks (question 3.19). The choice of model does not change the addressee of the obligations towards its own staff. The head of the entity ensures the awareness of that staff (Article 8d(4)). According to the Minister of Digital Affairs, the criminal record check under Article 8f does not cover the provider’s staff, and their security should be ensured through supply chain risk management and contractual provisions (Q&A 3.48).
What remains to be settled is the interface between the two sides. Someone on the entity’s side receives information from the provider, assesses it and triggers the decision to report. That person needs preparation regardless of the provider’s competence, because the addressee of the reporting obligation remains the essential or important entity.
When the list has to be ready
Entities that met the qualification criteria on 3 April 2026 have twelve months to meet the obligations set out in the chapter on essential and important entities, that is until 3 April 2027 (Article 33(1) of the amending act of 23 January 2026). An entity that meets the criteria later has twelve months from that moment (Article 16(1) of the KSC Act). An entity recognised as essential or important by a decision counts twelve months from its delivery (Article 7l(7)(1) and Article 7m(6)(1)). Staff education belongs to the same chapter as the other elements of the system. According to the Minister of Digital Affairs, the first training of the head of an entity that met the criteria on 3 April 2026 must take place in 2027 at the latest (Q&A 3.46).
The list of groups, however, comes into being earlier and almost as a by-product. It is the by-product of two other pieces of work. The first is establishing the scope of the information security management system, the second is identifying the people who perform the tasks under Articles 8 and 11. An organisation that is still establishing the scope of its obligations and its state of readiness will not build a credible list of groups before that is settled.
Most common mistakes
- One course for everyone treated as the whole obligation. A module on passwords and phishing covers cyber hygiene, not the tasks of the people who perform Articles 8 and 11.
- A list of groups built from the organisational chart. The starting point is the scope of the system and the division of tasks, not the structure of departments.
- Leaving out the person entrusted with the head’s duties. The Act names them alongside the head of the entity in Article 8e(1).
- Excluding procurement and HR because “they are not technical roles”. Supplier assessment and the criminal record check are activities set out in the Act.
- Assuming that a contract with a provider removes the obligation towards your own staff. What changes is the model for performing the tasks, not the addressee of the obligations.
- Training the people under Articles 8 and 11 without a list of names first. The criminal record check requires establishing who performs those tasks anyway. It is therefore worth building one list for both purposes.
- Repeating the content of the head’s training in training for staff. The scope under Article 8e(2) covers the performance of the entity’s obligations listed in that provision, not an employee’s day-to-day activities.
Conclusions and next steps
Every board member completes training under Article 8e, and beyond the board so does the person entrusted with the head’s duties in the area of cybersecurity. Awareness of duties and knowledge of internal rules has to cover all of the entity’s staff (Article 8d(4)). The organisation decides on broader preparation itself — by the scope of its system, the division of tasks and involvement in handling incidents. An important entity that is a public entity and the entities under Article 8b(1) also have specific requirements — in Annex 4 and in Regulation 2024/2690 respectively. The result of that work is both a training plan and evidence that the result required by Article 8d(4) has been planned deliberately.
The circle of those trained is easiest to establish in seven steps.
- Check whether anyone has been entrusted with the head’s duties in the area of cybersecurity and whether there is a record of it. That person is subject to the training obligation together with every board member.
- List by name the people who perform the tasks under Articles 8 and 11, together with their deputies. The same list organises the criminal record check.
- Add the people designated for contact with the entities of the national cybersecurity system.
- Go through the catalogue of measures in Article 8(1)(2) and assign to each element the role that actually decides about it.
- Differentiate the scope and depth of training by tasks and access, not by the type of contract.
- In an important entity that is a public entity, set the result against points 14 and 17 of Annex 4.
- Write down how you will know that the result under Article 8d(4) has been achieved — otherwise a year later all that will be left is an attendance list.
Related materials
- What should NIS2 training for the board cover? — the scope of the mandatory training for the head of the entity and for the person entrusted with their duties.
- How do you know that training produced a real effect? — how to check the result required by Article 8d(4).
- What to do after detecting an incident? — the sequence of the first day, that is the material for the people handling incidents and the people designated for contact.
- How to document training so that it serves as evidence for the authority? — how to record the training of the head of the entity and other staff so that it can be demonstrated to the authority.
- Who must be checked in the National Criminal Register for NIS2, and when? — the criminal record check of the same circle of persons performing tasks under Articles 8 and 11.
Sources
- Act of 5 July 2018 on the National Cybersecurity System, Article 2(8a), Article 7l(7), Article 7m(6), Article 8, Article 8b(1), Articles 8c–8f, Article 9, Article 14, Article 16(1), Article 73a(1)(6) and Annex 4, consolidated text — Chancellery of the Sejm, ISAP: isap.sejm.gov.pl (in Polish)
- Accounting Act of 29 September 1994, Article 3(1)(6), consolidated text — Chancellery of the Sejm, ISAP: isap.sejm.gov.pl (in Polish)
- Act of 23 January 2026 amending the Act on the National Cybersecurity System and certain other acts (Journal of Laws 2026, item 252), Article 33 — Journal of Laws: dziennikustaw.gov.pl (in Polish)
- Directive (EU) 2022/2555 of the European Parliament and of the Council (NIS 2), Article 20(2) and Article 21(2)(g) — EUR-Lex: eur-lex.europa.eu
- Commission Implementing Regulation (EU) 2024/2690 of 17 October 2024, Annex, points 8.1.1, 8.1.2, 8.2.1 and 8.2.4 — EUR-Lex: eur-lex.europa.eu
- Amendment of the KSC Act — questions and answers (update of October 2026), questions 3.3(i), 3.8, 3.19, 3.46, 3.47 and 3.48 — Ministry of Digital Affairs: cyber.gov.pl (in Polish)
- Amendment of the KSC Act — obligations of essential and important entities — Ministry of Digital Affairs: gov.pl (in Polish)
Let us match the training to the roles in your organisation
If the list of groups does not exist yet, it is worth starting by setting the tasks under Articles 8 and 11 against the people who actually perform them. That comparison defines the programme for each group separately. Training and workshops are built on it.
This material is general and educational in nature. It is not an individual legal opinion or a recommendation for any specific organisation. The scope of the obligations should be assessed against the situation of the organisation concerned.
Legal status: November 2026.