Poland’s KSC Cybersecurity Amendment: What Management Boards Need to Decide
The amendment to Poland’s Act on the National Cybersecurity System (the KSC Act) has been in force since April 3, 2026. It implements the NIS2 Directive and expands the estimated number of regulated entities from 397 to approximately 38,000.
No Polish authority will send your company a letter telling it that the Act applies. The company must assess its own position. If a multi-member management board does not designate a person responsible for cybersecurity, every board member may be held liable, with an individual penalty of up to 300% of their remuneration.
Three decisions require the board’s attention: determine whether the company is an essential entity, an important entity, or outside the Act’s scope; designate a responsible person by board resolution; and plan annual cybersecurity training. These are not matters the board can simply hand to IT. Nor can a company wait until 2028 to begin implementation.
Polish KSC terms at a glance
| Term | What it means |
|---|---|
| KSC Act | Poland’s Act of July 5, 2018 on the National Cybersecurity System, as amended by the Act of January 23, 2026 (Journal of Laws 2026, item 252). |
| NIS2 | The EU directive on measures for a high common level of cybersecurity, implemented in Poland through the KSC Act. |
| Essential entity | An entity operating in a sector listed in Annex 1 to the KSC Act and meeting the applicable size criteria. It faces the broadest obligations, including a security audit. |
| Important entity | An entity operating in a sector listed in Annex 2. Its obligations are similar, but penalties are lower and there is no mandatory audit. |
| Entity manager | A role defined by reference to Poland’s Accounting Act. For a Polish corporate company, this means its management board. Where the board has several members, all are responsible unless a person has been designated to take responsibility. |
| Sectoral CSIRT | The computer security incident response team responsible for a particular sector and the recipient of significant incident reports. |
| KSC Register | The electronic register of essential and important entities, available through Poland’s S46 System at wykaz-ksc.gov.pl. |
| SME criteria | EU size criteria under 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. The assessment includes linked enterprises. |
Does the KSC Act cover your company?
Your company must decide for itself whether it is an essential entity, an important entity, or outside the Act’s scope. The assessment has two stages.
1. Check what the company actually does. Compare its activities with Annex 1, covering essential sectors, and Annex 2, covering important sectors, to the KSC Act. The listed areas include energy, transport, healthcare, digital infrastructure, banking, water and wastewater management, manufacturing, food, postal and courier services, and digital services.
Use the annexes themselves rather than a general sector description or a list recalled from memory: a category can easily be missed or misclassified. It is also worth checking the company’s Polish PKD business activity codes against what it actually does. PKD codes identify registered business activities; they should not replace an assessment of the activity itself.
2. Check company size. If the activity falls within an annex, assess whether the company exceeds the SME thresholds in Commission Regulation (EU) No 651/2014. Medium-sized and large enterprises in the listed sectors fall within the Act’s scope.
Include the wider group. A Polish company cannot assess its size in isolation simply because its parent or other group companies are abroad. Include 100% of the data of linked enterprises and a proportionate share of partner enterprises’ data. A company with 90 employees, for example, may reach the wrong conclusion if it disregards a foreign owner holding a majority of voting rights.
Some entities are covered regardless of size. The SME thresholds do not determine coverage for certain activities, including DNS service providers, qualified trust service providers, top-level domain (TLD) name registries, and domain name registration service providers. A small business in one of these categories cannot rely on its size alone to exclude itself.
Record the result and a short explanation even if the conclusion is that the Act does not apply. Without a written self-assessment, the company may have nothing to show during an inspection that it considered the issue.
The deadlines: implementation comes before most penalties
The April 2028 penalty date is not an extension of the implementation deadline. Obligations and penalties operate on different timelines.
| Date or period | What happens |
|---|---|
| April 3, 2026 | The KSC amendment entered into force. |
| Six months after the entity meets the criteria—by October 3, 2026 for entities covered from entry into force | Apply for entry in the register of essential and important entities under Article 7c(1). |
| April 3, 2027—12 months after entry into force | Implement the Chapter 3 obligations, including an information security management system, incident-handling procedures, contact persons, and a connection to the S46 System. |
| Within 24 months—by April 3, 2028 for new essential entities | Complete the first security audit. |
| April 3, 2028 | Authorities may begin imposing most penalties. |
| Every calendar year | The entity manager must undergo cybersecurity training under Article 8e. |
Source for the timetable: Poland’s Ministry of Digital Affairs guidance on essential and important entities.
For a company that met the criteria when the amendment entered into force, the Chapter 3 implementation deadline is April 3, 2027. Waiting until 2028 would leave it a year late; the later start date for most penalties does not answer an allegation that the implementation obligation was breached.
What the management board must do—not just IT
Article 8c of the KSC Act places cybersecurity responsibility on the entity manager. In a company with a multi-member management board, responsibility rests with all members unless the board designates a responsible person by resolution.
Article 8d identifies four groups of management duties that cannot be transferred wholesale to IT:
- Decide on security measures. The board decides which safeguards to implement; its role is not limited to endorsing IT proposals.
- Secure funding. A cybersecurity budget is a management responsibility. Document the budget decision.
- Assign tasks. Allocate responsibilities across teams and name process owners.
- Maintain staff awareness. Ensure employees understand how to respond to threats.
Consider a technology company whose multi-member board sends “NIS2” to IT but never adopts a resolution assigning cybersecurity duties. After an incident, every board member may face individual liability, each for up to 300% of their remuneration.
The practical division should be written down:
| Management board decision | IT or operations implementation |
|---|---|
| Approve the security policy | Deploy tools and configurations |
| Allocate the cybersecurity budget | Purchase and maintain technical solutions |
| Designate the responsible person by resolution | Handle incidents day to day |
| Approve the training plan | Organize and deliver training |
| Decide the scope of an audit | Prepare documentation for the auditor |
| Designate a sectoral CSIRT contact | Test the incident-reporting procedure |
Adopt a board resolution identifying the person entrusted with cybersecurity duties. Without one, responsibility remains with all board members.
Annual cybersecurity training for the entity manager
Under Article 8e(1), the manager of an essential or important entity must undergo cybersecurity training once in every calendar year. The requirement also applies to a person entrusted with the manager’s duties.
Article 8e(2) specifies the provisions the training must cover. They concern, among other matters:
- Registration and information duties toward authorities—Articles 7b(4), 7c, and 7f(3).
- The information security management system and risk management—Article 8.
- The entity manager’s duties—Article 8d.
- Incident management and reporting—Articles 9–12b.
- Information duties toward service users—Article 8f(1) and (2).
- Audits and cooperation with authorities—Articles 14 and 15.
The Act does not specify a minimum number of training hours, require an in-person rather than online or e-learning format, mandate a certificate, or require an accredited training provider. That flexibility does not make a general awareness course sufficient if it omits the required subject matter.
Article 8e(3) requires participation to be documented, without prescribing an exhaustive list of acceptable evidence. Taken together, the records should show:
- who attended—the person’s name and role;
- when—both the date and calendar year;
- the format—in person, online, or e-learning;
- the duration in hours; and
- the topics covered, linked to Article 8e(2).
Put the training on the corporate calendar and decide in advance how to retain evidence, such as attendance records, certificates, or training-platform reports. A board that completes training but does not collect documentation has not formally fulfilled the Article 8e obligation.
First training session: The Act does not expressly set a separate transitional deadline for it. The Ministry of Digital Affairs has discussed training in the context of implementing obligations by April 3, 2027. The source’s recommended prudent approach is to schedule the first session in 2027 and document it.
If you need help planning the program and documenting board participation under Article 8e, contact us.
Penalties for the entity and its managers
Authorities may impose most penalties from April 3, 2028, but implementation deadlines run earlier.
| Who may be penalized | Maximum penalty | Calculation basis |
|---|---|---|
| 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 under the rules for annual-leave pay equivalents |
| Manager of a public entity | Up to 100% of remuneration | The manager’s remuneration, calculated under the rules for annual-leave pay equivalents |
Source: Article 73a of the KSC Act, Journal of Laws 2026, item 252.
Do not confuse the two calculation bases. The entity’s penalty is linked to company revenue; a manager’s penalty is linked to personal remuneration. They involve separate proceedings. If a multi-member board has not designated a responsible person by resolution, each member may be penalized individually.
Registering in the KSC Register
An entity must apply for its own entry in the register of essential and important entities. Applications are submitted electronically through the KSC Register application in the S46 System at wykaz-ksc.gov.pl. Self-registration launched on May 7, 2026.
The process is to:
- Log in through Poland’s Węzeł Krajowy (National Node) and select “Wpisz nowy podmiot” (“Register a new entity”).
- Provide the information required by Article 7(2)(1)–(18) of the KSC Act.
- Make the declaration concerning criminal liability under Article 233 § 6 of Poland’s Criminal Code.
- Sign the application using an accepted method: a qualified electronic signature, trusted signature, personal signature, or qualified electronic seal.
- Submit it within six months of meeting the criteria.
There is no paper application and no route outside the S46 System. Failure to register does not remove the underlying cybersecurity obligations. Do not wait for an authority to contact the company.
Significant incidents: a three-stage reporting process
The amendment replaces a single-report model with three reporting stages:
| 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 a progress report if incident handling continues | After incident handling is completed | The relevant sectoral CSIRT |
The recipient matters operationally. Reports go to the sectoral CSIRT responsible for the company’s sector, rather than to CSIRT MON, NASK, or GOV under the previous model. Designate and report a CSIRT contact person, then test the reporting route with a sample scenario.
Supply-chain risk and supplier contracts
The KSC Act requires supply-chain security for ICT products, services, and processes to be addressed as part of risk management. It does not expressly prescribe a set of mandatory contract clauses. Contractual requirements are, however, a practical way to carry out the obligation.
- If your company is an essential or important entity: review ICT supplier contracts for security requirements, incident-notification duties, and rights to verify compliance.
- If your company supplies SaaS, hosting, or other ICT services: expect customers in covered sectors to seek security commitments, incident-reporting deadlines, and audit rights. Prepare for those discussions before negotiations start.
- When assessing a supplier: consider supplier-related vulnerabilities, the quality of its products and services, and its links to other entities.
Do ISO 27001, SOC 2, DORA, or GDPR cover the same ground?
ISO 27001 certification or a SOC 2 report does not automatically establish KSC compliance. ISO 27001 may provide evidence for some information-security-management requirements, provided the certification scope covers all services and systems subject to the Act.
| Standard or regulation | Relationship to the KSC Act |
|---|---|
| ISO 27001 | May evidence some information security management system requirements if certification covers the relevant services. It does not replace KSC registration, training, or audit obligations. |
| SOC 2 | A supplier report may be useful evidence in supply-chain risk management, but it does not itself satisfy your company’s KSC obligations. |
| DORA | Addresses operational resilience for financial entities. Its scope may overlap with KSC, but the obligations are separate. |
| GDPR Article 32 | Protects a different subject matter—personal data rather than network and system security. One incident may trigger duties under both regimes. |
If ISO 27001 is already in place, conduct a gap analysis: identify what the existing program covers and what the KSC Act additionally requires.
Security audits for essential entities
Essential entities must pay for a security audit of their information system. For new essential entities—those that were not previously operators of essential services—the first audit is due within 24 months of the amendment’s entry into force, by April 3, 2028. Further audits are required at least once every three years.
The audit may be carried out by an accredited conformity assessment body or by at least two auditors meeting the requirements of the implementing regulations. Auditors must be independent: a person who performs or has performed cybersecurity tasks for the entity cannot audit it.
The outcome is a written report. An electronic copy must be sent to the competent authority.
Book audit capacity early. With an estimated 38,000 entities covered by the amended framework, finding an available auditor only three months before a deadline is an avoidable risk.
Management board checklist
| No. | Action | Priority | Indicative timing |
|---|---|---|---|
| 1 | Test the company’s activities against Annexes 1 and 2, then assess size under the EU SME criteria, including linked enterprises. | Immediate | As soon as possible |
| 2 | Record the conclusion and reasons, including a conclusion that the Act does not apply. | Immediate | Alongside the assessment |
| 3 | Adopt a board resolution designating the person responsible for cybersecurity. | Immediate | Before applying for registration |
| 4 | Apply for entry in the KSC Register through S46. | Required | Within six months of meeting the criteria |
| 5 | Schedule implementation of the Chapter 3 duties and assign task owners. | Required | Final deadline: April 3, 2027 |
| 6 | Allocate cybersecurity funding and document the budget decision. | Required | Next budget-planning cycle |
| 7 | Plan the first Article 8e board training session and document participation. | Required | Prudent approach: by the end of 2027 |
| 8 | Designate a sectoral CSIRT contact and test incident reporting. | Required | Before April 3, 2027 |
| 9 | Review ICT supplier contracts for security requirements and verification rights. | Recommended | Alongside implementation |
| 10 | Reserve an auditor, if the company is an essential entity. | Recommended | Well before the 24-month deadline |
How we can help
Determining KSC status, adopting board resolutions, allocating responsibilities, documenting training, and reviewing supplier agreements are legal and organizational tasks—not just technical ones.
We support technology companies and growing organizations with:
- Scope assessments: applying the two-stage test, reviewing ownership structures—including foreign-owned groups—and documenting the conclusion.
- Board resolutions and responsibilities: preparing a resolution designating the responsible person, dividing board and IT responsibilities, and organizing corporate records.
- Supplier and customer contracts: addressing security requirements, incident-notification clauses, and verification rights in light of the Act.
If you need to establish your company’s status, prepare board documentation, or review contracts for KSC purposes, contact us.
The three decisions to make first
The KSC amendment implements NIS2 and is estimated to affect approximately 38,000 entities in Poland. Companies must assess their own status. For entities covered from entry into force, the principal implementation deadline is April 3, 2027—not April 2028. Entity-level penalties can reach EUR 10 million or the applicable revenue percentage; an entity manager may face an individual penalty of up to 300% of remuneration.
The board should:
- Determine and document whether the company is essential, important, or outside scope.
- Designate a responsible person by resolution; otherwise, responsibility remains with all board members.
- Plan and document annual Article 8e training.
IT will play a central role in implementation, but these decisions belong to management. Acting early reduces the company’s exposure as the 2027 and 2028 deadlines approach.
Frequently asked questions
How can I tell whether a Polish company is an essential or important entity?
Check its actual activities against Annexes 1 and 2 to the KSC Act, then apply the EU SME size criteria using the required group data. Check separately whether an activity is covered regardless of size. No authority will notify the company; record the assessment and its reasons.
Can the management board leave cybersecurity entirely to IT?
No. Articles 8c–8d assign the entity manager responsibility for security-measure decisions, funding, task allocation, and staff awareness. IT can implement technical measures, but management decisions and budgets remain with the board. Without a resolution designating a responsible person, all members of a multi-member board are responsible.
Can we wait until April 2028 because most penalties start then?
No. For entities covered from entry into force, Chapter 3 obligations must be implemented by April 3, 2027. The date from which authorities may impose most penalties does not postpone that obligation.
Can an online course satisfy Article 8e?
It may. The Act specifies neither a minimum duration nor an in-person format or provider-accreditation requirement. The course must cover the required Article 8e(2) topics, and participation must be documented—including who attended, when, how, for how long, and what was covered.
Does ISO 27001 certification remove KSC obligations?
No. Certification may evidence some requirements if its scope covers the relevant services and systems, but it does not replace registration, Article 8e training, or the Article 53 audit obligation. A gap analysis will show what remains to be done.
What personal penalty could a management board member face?
An administrative penalty of up to 300% of the member’s remuneration, calculated under the rules for annual-leave pay equivalents. This is separate from an entity-level penalty. If no responsible person has been designated by board resolution, each board member may be penalized individually.