Analysis

NIS2 penalties in Poland: up to EUR 10 million for companies, fines for board members and deadlines

This article is for the management boards of companies that are essential or important entities under the Polish National Cybersecurity System Act (KSC Act). We explain how large a penalty can be for the company and for a board member, when the authorities can impose it and what reduces it. At the end you will find a list of actions the management board should have documented before the first inspection.

Author: Kacper Włodarczyk, CEO of ALGORCOMPPublished: June 04, 2026Reading time: 11 min readCybersecurity and complianceFor: Mid-sized company
NIS2 penalties in Poland: up to EUR 10 million for companies, fines for board members and deadlines

The maximum penalty for essential and important entities

The Act distinguishes two groups of companies subject to obligations: essential entities and important entities. Typically, an essential entity is a large enterprise in a sector listed in Annex 1 to the Act. An important entity is a medium-sized enterprise from Annex 1, or a medium-sized or large one from Annex 2. Both groups have the same risk management obligations, but they differ in the level of penalties and the way they are supervised.

The euro amount is converted into zloty at the average National Bank of Poland (NBP) exchange rate of 31 December of the year preceding the decision. The percentage is calculated from the company’s business revenue in the previous financial year. We have summarised the main differences in the table below.

Financial penalties for companies under Article 73 of the Polish National Cybersecurity System Act
IssueEssential entityImportant entity
Maximum penaltyEUR 10 million or 2% of revenue – whichever is higherEUR 7 million or 1.4% of revenue
Minimum penaltyPLN 20,000PLN 15,000
Infringement causing a serious cyber threat, e.g. to human life and healthUp to PLN 100 millionUp to PLN 100 million
Type of supervisionEx ante and ex post – inspections possible without suspicion of an infringementEx post – usually after an incident or a report of an infringement
Ban on a board member holding officePossibleNot applicable

How the penalty is calculated in practice: an example of a company with revenue of PLN 100 million

The formula “a fixed amount or a percentage of revenue” is often misleading. Take a hypothetical manufacturing company with revenue of PLN 100 million that is an essential entity. 2% of its revenue is PLN 2 million, while EUR 10 million is about PLN 42 million at an assumed exchange rate of PLN 4.20. The upper limit of the penalty is therefore the higher amount, i.e. EUR 10 million.

The percentage of revenue only becomes decisive with revenue above EUR 500 million – for both essential and important entities. For a typical mid-sized company, the maximum is therefore the fixed amount, not the percentage of revenue.

The maximum is, however, a ceiling, not a standard rate. The authority sets the amount of the penalty according to the criteria in Article 53(12) and takes the company’s financial capacity into account. We list the most important criteria below.

  • The seriousness of the infringement – the Act treats as serious, among other things, repeated infringements, failure to report a major incident and failure to comply with the authority’s orders.
  • The duration of the infringement and any previous serious infringements by the same company.
  • The damage caused by the infringement, including the number of users affected by the incident.
  • Whether the infringement was intentional or unintentional.
  • The steps the company took to limit the damage, and its cooperation with the authority.
  • If the infringement is negligible, the authority may waive the penalty altogether, provided the company has stopped infringing the rules or has remedied the damage (Article 76a(9)).
NIS2 penalties in Poland: up to EUR 10 million for companies, fines for board members and deadlines

Fines for board members: who they apply to and how large they can be

The Act expressly provides for a financial penalty for the head of an essential or important entity. The head is the head of the entity within the meaning of the Accounting Act – in a limited liability or joint-stock company, this is the management board. The fine can be up to 300% of the penalised person’s remuneration, calculated in the same way as pay in lieu of unused holiday. In public entities, the limit is 100%.

The authority can impose it when the management board fails to fulfil its obligations under the Act and the duration, scope or nature of the infringement justify it. A fine for a board member can be imposed independently of the penalty for the company.

The rule in Article 8c is important. If the management board has several members and has not appointed a person responsible for cybersecurity, all its members are liable. Delegating tasks to the IT director or an external firm does not relieve the management board of liability. Fines may be imposed for, among other things, the failures listed below.

  • No decision to prepare, implement and review an information security management system (ISMS) – a written set of rules, roles and safeguards.
  • No financial resources set aside for cybersecurity obligations.
  • No annual, documented training for the head of the entity.
  • Failure to report major incidents and to fulfil other incident-related obligations.
  • Failure to carry out the required security audit.
  • Allowing a person to perform security tasks who has not provided a certificate from the National Criminal Register (KRK) showing no convictions for offences against the protection of information.

Other sanctions the supervisory authority can apply

A financial penalty is only one of the tools available. The authority competent for cybersecurity is usually the minister responsible for the sector concerned. For manufacturing it is the minister responsible for the economy, for food – the minister responsible for agriculture, and for electronic communications and postal services – the President of the Office of Electronic Communications (UKE).

Some of the measures below may hurt a company more than the penalty itself, because they damage its reputation or day-to-day operations. The last three apply only to essential entities.

  • A warning letter setting out what the company must improve and by when.
  • An order to stop the infringements, implement audit recommendations or inform customers of a serious cyber threat.
  • An order to make public information about the infringement or about a major incident.
  • A periodic penalty payment of PLN 500 to PLN 100,000 for each day of delay in complying with the authority’s decision.
  • Appointment, for up to one month, of an official to oversee the fulfilment of obligations in the company.
  • Suspension of a licence, permit or business activity, in whole or in part, until the shortcomings are remedied.
  • A ban on holding office on the management board until the shortcomings are remedied, provided this does not paralyse the company’s operations.
Company management board discussing a cybersecurity status report during a board meeting

The Act does not penalise you for being attacked. It penalises the management board for failing to take the decisions that were its responsibility.

When penalties become a risk: key dates

The amendment was published on 2 March 2026 and has applied since 3 April 2026. The transition period applies only to financial penalties. The authority can issue warnings, orders and carry out inspections right away, and the obligations must be met by the deadlines in the table below.

If your company has not yet applied for entry in the register, do so without delay. Failing to apply on time is an infringement of the Act. The authority can already demand that it be remedied, and from 3 April 2028 it can also impose a financial penalty for it.

Timetable of obligations and penalties under the amended Polish National Cybersecurity System Act
DateWhat happens
3 April 2026The amendment comes into force
3 October 2026Deadline for applying for entry in the register of essential and important entities
3 April 2027Deadline for implementing the information security management system and the other obligations
3 April 2028Deadline for the first audit of essential entities; from this date, financial penalties can be imposed on companies and board members

What the management board should have documented before the first inspection

The authority will assess not declarations but evidence: resolutions, plans, training records and reports. That is why the list below distinguishes between requirements that follow directly from the Act and good practices that make it easier to demonstrate compliance.

Take a hypothetical distribution company with 180 employees that is an important entity. Its management board adopts a resolution appointing a board member responsible for cybersecurity and plans a budget. From then on, it receives a short quarterly report on the state of security and on incidents. During an inspection after an incident, the company can show that the management board took decisions rather than merely signing a policy.

  • Statutory requirement: management board decisions on implementing and reviewing the information security management system, and the resources planned for it (Article 8d).
  • Statutory requirement: training for the head of the entity and the person to whom they have delegated obligations, once every calendar year, with proof of attendance (Article 8e).
  • Statutory requirement: a certificate from the National Criminal Register from people performing security tasks, before they are allowed to start work (Article 8f).
  • Statutory requirement: a procedure for reporting major incidents – an early warning within 24 hours, a notification within 72 hours and a final report within one month.
  • Good practice: a resolution appointing one board member responsible for cybersecurity.
  • Good practice: a quarterly security status report for the management board, with decisions recorded in the minutes.

Related topics in the knowledge base

Read next

FAQ

NIS2 penalties – frequently asked questions

Questions management boards usually ask after their first reading of the penalty provisions.

Can a single infringement lead to penalties under both the KSC Act and the GDPR?
As a rule, no. Suppose the President of the Polish data protection authority (UODO) has issued a final penalty against the company for the same event. The cybersecurity supervisory authority then does not open proceedings and limits itself to an instruction (Article 76c). It can, however, still issue orders and apply other supervisory measures.
Can liability be transferred to the IT director or an external firm?
Tasks yes, liability no. The Act states expressly that the head of the entity remains liable even after delegating obligations to another person with that person’s consent. An external specialist can prepare documents and run security on a day-to-day basis, but decisions and oversight remain with the management board.
Our company is neither an essential nor an important entity. Do these penalties apply to us?
The penalties under Articles 73 and 73a do not. However, if you supply services or systems to companies covered by the Act, you can expect security requirements in contracts and questionnaires from customers. In that case, the pressure will come from them, not from the supervisory authority.
Will a company always pay at least PLN 20,000 if the authority finds an infringement?
No. The minimum applies when the authority decides to impose a penalty. If the infringement is negligible, it may waive the penalty, provided the company has stopped infringing the rules or has remedied the damage.
Who carries out the audit whose absence is subject to a penalty?
An authorised, independent auditor with the required qualifications. The auditor cannot be someone who has performed security tasks for the entity in the past year. Essential entities must complete their first audit by 3 April 2028.

About this page

About the author

Kacper Włodarczyk — CEO of ALGORCOMP

Kacper Włodarczyk

CEO of ALGORCOMP

Kacper specializes in implementing Microsoft 365 Copilot, Copilot Studio, Power Platform (Power Automate, Power Apps, SharePoint) and AI agents for mid-sized B2B companies in Poland. He leads dozens of projects covering AI strategy, Power Platform governance, document workflow automation and sales processes. In his writing he focuses on the practical side of AI adoption in organizations — from the first proof of concept to company-wide rollout — with particular attention to data security, compliance (GDPR, NIS2, the AI Act) and return on investment.

Meet the team

Want to check whether your management board has everything the supervisory authority expects?

We will review your company’s resolutions, procedures and documents against the Polish National Cybersecurity System Act and show you what needs to be completed before 3 April 2027.

Featured

Related articles