The amendment to the Act on the National Cybersecurity System (KSC) has been in force since 3 April 2026. It implements the NIS2 Directive and expands the scope of the regulations from the previous 397 entities to an estimated 38,000. No authority will send your company a letter informing you that it is covered by the Act. You must check this yourself — and if the management board does not designate a person responsible for cybersecurity, all of its members will be liable, each for up to 300% of their remuneration.
This article guides you through three decisions that the management board must make itself: determine the company’s status (essential entity, important entity, or not covered), appoint a person responsible for cybersecurity by resolution, and plan annual training. Along the way, we debunk two myths — that “this is an IT matter" and that “we have until 2028."
Key terms worth knowing
Before you continue, make sure you understand the terms used in the Act and in this article.
| Term | Meaning |
|---|---|
| KSC | The Act of 5 July 2018 on the National Cybersecurity System, as amended by the Act of 23 January 2026 (Journal of Laws 2026, item 252) |
| NIS2 | The EU Directive on measures for a high common level of cybersecurity — implemented into Polish law by the KSC Act |
| Essential entity | A company operating in a sector listed in Annex 1 to the KSC Act and meeting the size criteria — subject to the broadest range of obligations, including an audit |
| Important entity | A company operating in a sector listed in Annex 2 — subject to similar obligations, but lower penalties and no mandatory audit |
| Entity manager | A person defined by reference to the Accounting Act — in companies, this means the management board; where the board has multiple members, all members are liable unless a responsible person has been designated |
| Sectoral CSIRT | The computer security incident response team responsible for a given sector — the recipient of significant incident reports |
| KSC Register | An electronic register of essential and important entities, available in the S46 System at wykaz-ksc.gov.pl |
| SME criteria | EU size thresholds set out in Annex I to Commission Regulation (EU) No 651/2014 — fewer than 250 employees and turnover of up to EUR 50 million or a balance sheet total of up to EUR 43 million; calculated together with linked enterprises |
Who is covered by the KSC amendment and how to check
No one will notify you. Each company must independently determine whether it is an essential entity, an important entity, or not covered by the Act. The test has two stages.
Step 1: type of business activity. Check whether your company conducts an activity listed in Annex 1 (essential sectors) or Annex 2 (important sectors) to the KSC Act. These sectors include energy, transport, healthcare, digital infrastructure, banking, water and wastewater management, manufacturing, food, postal and courier services, and digital services.
Do not try to determine your status from memory or based on general descriptions. Refer directly to the annexes — the risk of overlooking or misclassifying a category is high. It is also worth checking your PKD codes to ensure that the registered business activity codes reflect what the company actually does.
Step 2: company size. If the type of activity matches, check whether your company exceeds the SME thresholds under Commission Regulation (EU) No 651/2014. Medium-sized and large enterprises operating in the sectors listed in the annexes fall within the scope of the Act.
Note: company size is calculated together with linked enterprises. If your company belongs to a corporate group — Polish or foreign — you must include 100% of the data of linked enterprises and a proportionate share of the data of partner enterprises. A company with 90 employees that disregards a foreign owner holding a majority of voting rights may incorrectly conclude that it does not exceed the threshold.
Exception: entities covered regardless of size. SME thresholds do not apply to certain types of business activity. This includes DNS service providers, qualified trust service providers, top-level domain (TLD) name registries, and entities providing domain name registration services. Companies in these categories cannot rely on their small scale as grounds for exclusion.
What to do with the self-assessment result
Record the result of the analysis together with a brief justification — even if you conclude that the Act does not apply to you. This is the only evidence that the analysis was conducted at all. A company that concludes “this does not apply to us" but fails to document that conclusion will have no way of demonstrating during an inspection that it examined the issue.
Key deadlines for implementing the KSC amendment
One of the most common mistakes is waiting until 3 April 2028 to implement the requirements because “that is when penalties begin." In fact, the implementation deadline expires one year earlier. Penalties and obligations follow two different timelines.
| Deadline | Event |
|---|---|
| 3 April 2026 | Entry into force of the KSC amendment |
| 6 months after meeting the criteria (for companies covered from the date of entry into force: by 3 October 2026) | Submission of an application for entry in the register of essential and important entities (Art. 7c(1)) |
| 3 April 2027 (12 months after entry into force) | Implementation of the obligations under Chapter 3 of the Act: information security management system, incident handling procedures, designation of contact persons, and connection to the S46 System |
| 24 months (by 3 April 2028 for new essential entities) | First security audit of an essential entity |
| 3 April 2028 | Date from which authorities may impose most penalties |
| Every calendar year | Annual cybersecurity training for the entity manager (Art. 8e) |
Source of deadlines: Ministry of Digital Affairs — obligations of essential and important entities
The conclusion is simple: if your company meets the criteria from the date the Act enters into force, the deadline for implementing the obligations is 3 April 2027. Waiting until 2028 means being one year late — with no defence against an allegation of non-compliance.
What the management board is responsible for — and why this is not “an IT matter"
The Act assigns responsibility for cybersecurity to the entity manager (Art. 8c of the KSC Act). Where the management board has multiple members, all of them are liable unless a responsible person has been designated by resolution.
List of the entity manager’s duties (Art. 8d)
Art. 8d of the KSC Act lists four groups of duties that cannot be fully delegated to the IT department:
- Making decisions on security measures — the management board decides which safeguards to implement rather than merely approving IT proposals
- Securing funding — the cybersecurity budget is a separate obligation of the entity manager; document the budget decision
- Assigning tasks — the management board allocates responsibilities among teams and appoints process owners
- Ensuring staff awareness — the management board is responsible for ensuring that employees know how to respond to threats
A scenario we see in technology companies: a multi-member management board hands the NIS2 matter over to the IT department without adopting a resolution assigning the duties. After an incident, all management board members are held liable — each for up to 300% of their remuneration.
How to allocate responsibility
Distinguish between management board decisions and technical implementation — and document this division.
| Management board decision | IT/operations implementation |
|---|---|
| Approval of the security policy | Implementation of tools and configurations |
| Allocation of the cybersecurity budget | Purchase and maintenance of technical solutions |
| Designation of the responsible person (by resolution) | Day-to-day incident handling |
| Approval of the training plan | Organisation and delivery of training |
| Decision on the scope of the audit | Preparation of documentation for the auditor |
| Designation of a person to liaise with the CSIRT | Testing the incident reporting procedure |
Adopt a management board resolution designating the person entrusted with cybersecurity duties. Otherwise, everyone is liable.
Mandatory cybersecurity training for the management board (Art. 8e)
Art. 8e(1) of the KSC Act requires the manager of an essential or important entity to undergo cybersecurity training once in every calendar year. The training requirement also applies to a person entrusted with the manager’s duties.
Scope of the training
Art. 8e(2) provides an exhaustive list of provisions that the training must cover. These concern, among other things:
- Registration and information obligations towards the authorities (Art. 7b(4), Art. 7c, Art. 7f(3))
- The information security management system and risk management (Art. 8)
- The entity manager’s duties (Art. 8d)
- Incident management and reporting (Arts. 9–12b)
- Information obligations towards service users (Art. 8f(1) and (2))
- Audits and cooperation with the authorities (Art. 14, Art. 15)
What the Act does not specify
The Act does not specify a minimum number of hours, the format of the training (in-person, online, or e-learning), a mandatory certificate, or a requirement for the organiser to be accredited. This provides flexibility in choosing the format — but also creates a risk that overly general training will not cover the required scope.
How to document participation
Art. 8e(3) requires participation to be documented. The Act does not provide an exhaustive list of acceptable evidence. Taken together, the documentation should demonstrate:
- Who completed the training (first name, surname, position)
- When (date, calendar year)
- In what format (in-person, online, e-learning)
- For how long (number of hours)
- What it covered (topics linked to Art. 8e(2))
Add annual management board training to the corporate calendar and decide in advance how evidence will be collected — attendance lists, certificates, and reports from the training platform. A management board that completes the training but fails to collect documentation has not formally fulfilled the obligation under Art. 8e.
Important: the deadline for the first training session is not expressly specified in the Act in a separate transitional provision. The Ministry of Digital Affairs referred to the training requirement in the context of implementing the obligations by 3 April 2027 — the safest approach is to schedule the first training session in 2027.
Contact us if you need support in planning and documenting management board training in accordance with Art. 8e.
Penalties — how much entities and management boards may face, and for what
Authorities may impose most penalties from 3 April 2028. However, the implementation deadlines begin earlier and do not depend on the date from which penalties apply.
| Who it applies to | Maximum penalty | Basis of calculation |
|---|---|---|
| Essential entity | Up to EUR 10 million or 2% of annual revenue (whichever is higher) | The entity’s annual revenue |
| Important entity | Up to EUR 7 million or 1.4% of annual revenue (whichever is higher) | The entity’s annual revenue |
| Manager of an essential or important entity | Up to 300% of remuneration | The manager’s remuneration calculated according to the rules for annual leave compensation |
| Manager of a public entity | Up to 100% of remuneration | The manager’s remuneration calculated according to the rules for annual leave compensation |
Source: Art. 73a of the KSC Act, Journal of Laws 2026, item 252
Two figures must not be confused: the penalty imposed on the entity is calculated based on the company’s annual revenue, while the penalty imposed on the manager is calculated based on their personal remuneration. These are two separate proceedings with two separate bases of calculation.
Failure to designate a responsible person by management board resolution means that liability is shared among all management board members. Each of them may be penalised individually.
Entry in the register — procedure and deadline
You must submit the application for entry in the register of essential and important entities yourself, electronically, through the “KSC Register" application available in the S46 System at wykaz-ksc.gov.pl. Self-registration was launched on 7 May 2026.
What the procedure involves
- Log in through the National Node and select the “Register a new entity" option
- Complete the information required under Art. 7(2)(1)–(18) of the KSC Act
- Submit a declaration acknowledging criminal liability under Art. 233 § 6 of the Criminal Code
- Sign the application — accepted methods: qualified electronic signature, trusted signature, personal signature, or qualified electronic seal
- Submit the application within 6 months of the date on which the criteria are met
There is no paper form, nor can the application be submitted outside the S46 System. Failure to register does not release you from your substantive obligations — do not wait for a notice from the authorities.
Incidents — the new reporting model
The amendment changed the incident reporting model from a single report to a three-stage process:
| Stage | Deadline | Recipient |
|---|---|---|
| Early warning | Within 24 hours of detection | The relevant sectoral CSIRT |
| Significant incident notification | Within 72 hours of detection | The relevant sectoral CSIRT |
| Final report (or progress report if incident handling is still ongoing) | After incident handling has been completed | The relevant sectoral CSIRT |
The change of recipient has operational significance: reports must be sent to the sectoral CSIRT responsible for your industry, rather than to CSIRT MON/NASK/GOV as under the previous model. Designate and register a person to liaise with the CSIRT, then test the reporting path using a test scenario.
Supply chain and the impact on supplier contracts
The Act requires the security of the supply chain for ICT products, services, and processes to be taken into account as part of risk management. It does not expressly prescribe mandatory contractual clauses — but contractual requirements are a means of fulfilling this obligation.
What this means for your company:
- If you are an essential or important entity — review your contracts with ICT suppliers and add security requirements, incident notification obligations, and verification rights
- If you are a SaaS, hosting, or ICT service provider — your clients in sectors covered by the Act will begin adding security requirements, incident reporting deadlines, and audit rights to their contracts; prepare for these discussions before negotiations begin
- When assessing supplier risk take into account: supplier-related vulnerabilities, the quality of products and services, and the supplier’s links to other entities
Is ISO 27001 enough to meet KSC requirements?
Short answer: not automatically.
Holding an ISO 27001 certificate or a SOC 2 report does not automatically ensure compliance with the KSC Act. ISO 27001 may provide evidence that some system-related requirements have been met — provided that the scope of certification covers all services and systems subject to the Act.
| Certification / regulation | Relationship to the KSC Act |
|---|---|
| ISO 27001 | May cover some ISMS requirements if the scope of certification includes the services concerned; it does not replace the registration, training, or audit obligations under the KSC Act |
| SOC 2 | A supplier report — it may serve as evidence as part of supply chain management, but it does not satisfy the KSC requirements applicable to your company |
| DORA | Concerns the operational resilience of financial entities; its scope may overlap with the KSC Act, but the obligations are separate |
| GDPR Art. 32 | Different subject matter of protection (personal data vs. network and system security); an incident may trigger obligations under both regulations simultaneously |
If you have implemented ISO 27001, conduct a gap analysis — determine which requirements you already meet and what needs to be added for KSC compliance.
Audit of an essential entity — what you should know
Essential entities must conduct a security audit of their information system at their own expense. For new essential entities (those that were not previously operators of essential services), the deadline for the first audit is 24 months after the Act enters into force — that is, by 3 April 2028. Subsequent audits must be carried out at least once every 3 years.
The audit may be conducted by an accredited conformity assessment body or by at least two auditors who meet the requirements of the implementing regulations. The auditor must be independent — it cannot be someone who performs or has performed cybersecurity tasks for the audited entity.
Result: a written report, an electronic copy of which must be submitted to the competent authority.
Advice: book an auditor well in advance. With 38,000 entities covered by the regulations, the audit market may become congested — looking for available capacity three months before the deadline is an avoidable risk.
Management board checklist — where to start
Below is an ordered list of the steps the management board should take now:
| No. | Action | Priority | Indicative deadline |
|---|---|---|---|
| 1 | Conduct the two-stage scope test: type of business activity (Annexes 1 and 2) + company size (SME criteria including linked enterprises) | Immediate | As soon as possible |
| 2 | Record the self-assessment result together with a justification — even if the Act does not apply to you | Immediate | Together with the test |
| 3 | Adopt a management board resolution designating the person responsible for cybersecurity | Immediate | Before submitting the registration application |
| 4 | Submit an application for entry in the KSC Register through the S46 System | Required | Within 6 months of meeting the criteria |
| 5 | Create an implementation schedule for the obligations under Chapter 3 of the Act and assign task owners | Required | Final deadline: 3 April 2027 |
| 6 | Allocate cybersecurity funds in the budget and document the decision | Required | Next budget planning cycle |
| 7 | Plan and conduct the first management board training session (Art. 8e) and document participation | Required | Safest approach: by the end of 2027 |
| 8 | Designate a person to liaise with the sectoral CSIRT and test the incident reporting procedure | Required | Before 3 April 2027 |
| 9 | Review contracts with ICT suppliers — add security requirements and verification rights | Recommended | Alongside implementation |
| 10 | Book an auditor (essential entities) | Recommended | Well in advance, before the 24-month deadline expires |
How we can help your company prepare for the KSC Act
The KSC amendment requires the management board to make decisions that go beyond the remit of the IT department. Self-assessment of whether the Act applies, corporate resolutions, allocation of responsibility, training documentation, and review of supplier contracts are legal and organisational matters, not technical ones.
We support technology companies and growing organisations in three areas:
- Self-assessment of whether the Act applies — we conduct the two-stage test, analyse the ownership structure (including groups with foreign owners), and document the result
- Management board resolutions and allocation of responsibility — we prepare a resolution designating the responsible person, divide responsibilities between the management board and IT, and organise corporate documentation
- Review of supplier and customer contracts — we add security requirements, incident notification clauses, and verification rights in accordance with the Act
If you need support in determining your company’s status, preparing corporate documentation, or bringing your contracts into line with the KSC Act — contact us.
Summary: three decisions the management board must make itself
The KSC amendment implements NIS2 and is estimated to cover approximately 38,000 entities in Poland. No authority will send you a letter — you must check for yourself. The deadline for implementing the obligations is 3 April 2027, not 2028. Penalties for an entity can reach EUR 10 million, while those for a manager can amount to up to 300% of their remuneration.
The three management board decisions on which everything else depends:
- Determine and record the company’s status — essential entity, important entity, or not covered
- Designate a person responsible for cybersecurity by resolution — otherwise, all management board members are liable
- Plan and document the annual training required under Art. 8e
Each of these decisions requires action by the management board, not the IT department. The sooner you make them, the lower the risk your company will face in 2027 and 2028.
If you want to clarify your company’s status under the KSC Act, prepare corporate documentation, or review supplier contracts — contact us.
Frequently asked questions
How do I know whether my company is an essential entity, an important entity, or not covered by the Act?
Conduct a two-stage test: check the type of business activity against Annexes 1 and 2 to the KSC Act, then check the company’s size against the EU SME criteria — including linked entities within the corporate group. No authority will notify you. Record the self-assessment result together with a justification — this is the only evidence that the analysis was conducted.
Can I hand the entire cybersecurity matter over to the IT department?
No. The Act assigns the entity manager (Arts. 8c–8d of the KSC Act) responsibility for decisions on security measures, securing funding, assigning tasks, and ensuring staff awareness. IT performs technical tasks, but decisions and budgets remain the responsibility of the management board. Without a resolution designating a responsible person, all management board members are liable.
Do I have until 2028, since penalties cannot be imposed until 3 April 2028?
No. The deadline for implementing the obligations under Chapter 3 of the Act is 3 April 2027. The date of 3 April 2028 is when authorities may begin imposing most penalties — but a failure to comply with the implementation obligation exists from the moment the implementation deadline expires, not from the date penalties begin to apply.
What kind of training satisfies the requirement under Art. 8e, and is an online course sufficient?
The Act does not specify a minimum number of hours, the format of the training, or a requirement for the organiser to be accredited. An online course may satisfy the requirement if it covers the matters listed in Art. 8e(2) (including the security management system, incident management, and the entity manager’s duties) and is documented — who completed the training, when, in what format, for how long, and what it covered.
Does holding an ISO 27001 certificate exempt me from KSC obligations?
Not automatically. ISO 27001 may provide evidence that some system-related requirements have been met if the scope of certification covers all services and systems subject to the Act. It does not replace registration obligations (entry in the register), training obligations (Art. 8e), or audit obligations (Art. 53). Conduct a gap analysis to determine which requirements you already meet.
What personal consequences could I face as a management board member?
An administrative penalty of up to 300% of your remuneration (calculated according to the rules for annual leave compensation). This is separate from proceedings concerning a penalty imposed on the entity. If the management board has not designated a person responsible for cybersecurity by resolution, each management board member may be penalised individually.