News

/ Taxes and Law in Poland

NIS2 requirements in Poland – what businesses need to know

NIS2 requirements in Poland – what businesses need to know

/
Date16 Nov 2026
/
Stay up to date Add us as a preferred source on Google
Add

In Poland, NIS2 requires essential and important entities to manage cybersecurity risks, report incidents and meet specific compliance duties.

Key results at a glance
1

Companies subject to the rules as of 3 April 2026 had until 3 October 2026 to apply for entry in the KSC Register.

2

The deadline for implementing the new requirements and connecting to the S46 system is 3 April 2027 for the entities concerned.

3

A significant incident requires an early warning within 24 hours, an incident notification within 72 hours and a final report within one month.

4

For essential entities, the general penalty cap is EUR 10 million or 2% of annual revenue, while for important entities it is EUR 7 million or 1.4%.

5

The head of an essential or important entity and the person responsible for cybersecurity duties must complete training once in each calendar year.

Key takeaways

NIS2 status requires an individual assessment

Employee numbers alone do not determine whether NIS2 applies; the sector, corporate links and specific statutory criteria also matter.

Cybersecurity is not solely an IT responsibility

Assigning tasks to an IT team or external provider does not remove the statutory responsibility of the entity’s management.

Compliance requires action, not just documentation

A company should know its assets, manage risks, test procedures and maintain the continuity of critical business processes.

Outsourcing does not remove supplier risk

Entities subject to NIS2 must consider the security of external service providers, systems and other elements of the supply chain.

The NIS2 Directive was implemented into Polish law through an amendment to the Act on the National Cybersecurity System, which has applied since 3 April 2026. The new rules cover essential and important entities operating in specified sectors, including certain manufacturing and transport companies and digital service providers. Companies that met the statutory criteria on 3 April 2026 had until 3 October 2026 to apply for entry in the KSC Register. As a general rule, the deadline for implementing the new requirements is 3 April 2027. Responsibility for cybersecurity also rests with management and not exclusively with the IT department.


What is NIS2 and what does it change for businesses in Poland?

NIS2 is an EU cybersecurity directive designed to strengthen organisations’ resilience to cyber threats and ensure continuity in the provision of important services. In Poland, its requirements were implemented through an amendment to the Act on the National Cybersecurity System.

NIS2 expands the range of entities required to apply cybersecurity measures. It also introduces requirements covering risk management, supply chain security, incident reporting and management oversight.

For businesses, this changes the way information security must be managed. Purchasing antivirus software or outsourcing IT support is not enough. Organisations need processes that allow them to identify threats, limit their impact and maintain operations during a crisis.


Which businesses are subject to NIS2 in Poland?

NIS2 does not automatically apply to every business operating in Poland. Whether the rules apply depends primarily on the sector in which the company operates, its size and specific statutory criteria.

The rules distinguish between two categories of entities:

  1. Essential entities – as a general rule, large enterprises carrying out specified activities in sectors of particular importance, as well as certain entities regardless of size.
  2. Important entities – including medium-sized enterprises from sectors covered by the legislation and certain large entities operating in sectors listed in Annex 2 to the Act.

Examples of areas covered by the legislation are shown below.

Sectors listed in Annex 1Sectors listed in Annex 2
EnergyManufacture of selected industrial products
TransportManufacture and distribution of chemicals
Banking and financial market infrastructureManufacture, processing and distribution of food
HealthcareWaste management
Digital infrastructurePostal and courier services
ICT service managementSelected digital service providers

The table provides examples and does not constitute a complete list of activities covered by the Act.

Can a small company also be subject to NIS2 in Poland?

Yes. Although one of the main criteria is often reaching at least medium-sized enterprise status, the Act provides exceptions under which microenterprises and small businesses may also be subject to the requirements.

Ownership structure also matters. When determining the size of an enterprise, relevant data concerning partner and linked enterprises must be taken into account in accordance with the applicable classification rules. This can be particularly important for Polish companies belonging to international corporate groups. A relatively small number of employees in Poland does not in itself mean that the company falls outside the scope of the legislation.

The practical conclusion is that checking only the company’s PKD activity code and headcount may not be sufficient. Classification should take account of the activities actually carried out, corporate links and any sector-specific statutory rules.


What NIS2 deadlines apply to businesses in Poland in 2026 and 2027?

For companies that met the statutory criteria on 3 April 2026, the key deadlines are as follows:

DeadlineRequirement
3 October 2026Deadline for submitting an application for entry in the KSC Register for entities required to self-register
3 April 2027Deadline for implementing the new requirements and connecting to the S46 system
3 April 2028Deadline for the first mandatory audit for essential entities subject to this requirement

These deadlines apply to the specified group of entities. Companies that meet the criteria at a later date should assess the applicable deadlines separately.

What should a company do if it missed the KSC Register deadline?

A company that was required to self-register but did not submit its application by 3 October 2026 should promptly verify its status and complete the outstanding registration requirement.

The absence of an entry in the register does not automatically mean that the company is outside the scope of the rules. The obligations arise from meeting the statutory criteria rather than only after confirmation is received from an authority.


What NIS2 requirements must a company implement in Poland?

The core requirement is to implement and maintain an information security management system incorporating organisational and technical measures appropriate to the level of risk.

In practice, a company should address the following areas:

  1. Risk management – identifying threats to systems, data and business processes and determining how those risks should be mitigated.
  2. Incident management – establishing procedures for detecting, analysing, reporting and mitigating the effects of incidents.
  3. Business continuity – preparing contingency plans, maintaining backups and testing system recovery.
  4. Supplier security – assessing risks associated with external service providers and systems.
  5. Access control – managing user permissions, using appropriate authentication methods and securing communications.
  6. Employee training – building awareness of cyber threats and preparing staff to respond appropriately.
  7. Assessment of security effectiveness – regularly checking whether the measures adopted actually reduce risk.
  8. Organisation of cybersecurity responsibilities – assigning responsibility for compliance and ensuring management oversight of how those duties are performed.

Linking technical safeguards to business processes is particularly important. A procedure that exists only on paper does not give a company the practical ability to respond effectively to an incident.


Why is NIS2 also a management, finance and accounting issue?

Cybersecurity is often treated as the responsibility of the IT department. However, the consequences of a serious incident can directly affect liquidity, contract performance and a company’s reporting obligations.

For example, an attack on an ERP system may simultaneously prevent the company from issuing invoices, processing orders, accessing accounting data and making payments. A technical problem can therefore quickly become an operational and financial problem.

From a CFO’s perspective, three questions are particularly important:

  1. How long can the company continue operating without access to critical systems?
  2. What losses would result from one day or several days of downtime?
  3. Are there tested procedures that allow accounting processes and customer or supplier servicing to continue?

This is where NIS2 connects cybersecurity with business risk management and operational processes. The effectiveness of safeguards should be assessed not only through technical parameters, but also through the organisation’s ability to maintain its most important processes.

For companies using outsourced accounting services in Poland, it is also important to determine the rules governing access to data, responsibility for systems and procedures in the event that services become unavailable.


Can management transfer responsibility for NIS2 to the IT department?

No. Assigning operational tasks to an IT department or an external provider does not release management from statutory cybersecurity obligations.

Management of entities covered by the legislation is responsible for ensuring compliance with statutory cybersecurity requirements, including decisions concerning the preparation, implementation, operation and supervision of the information security management system. The head of an essential or important entity and the person entrusted with cybersecurity responsibilities must complete training once in each calendar year, and participation should be documented.

Assigning tasks to an IT department, cybersecurity specialist or external service provider does not remove the responsibility of the head of the entity.

In practice, management should receive information not only about the number of detected threats, but also about risks to business operations, the status of remediation measures and the organisation’s readiness to handle incidents. Documenting decisions, allocating responsibilities and ensuring appropriate resources are also important.


Does outsourcing transfer NIS2 responsibility to service providers?

Using external services does not remove the obligation to manage supply chain risk. Companies subject to NIS2 must take account of the security of their relationships with direct suppliers and service providers.

This includes, among others, providers of ERP software, cloud services and production systems, as well as entities that have access to important data or infrastructure.

When assessing a provider, it is worth establishing whether it:

  • applies appropriate security measures;
  • has incident response procedures;
  • maintains backups and service recovery arrangements;
  • defines rules for notifying customers about security breaches;
  • properly regulates access to data and systems in supplier agreements – in this area, appropriate legal advisory services in Poland may also be relevant when drafting and reviewing commercial agreements.

It is particularly important to establish who is responsible for specific actions in an emergency.

For example, a company may have an ERP recovery procedure, but if access to backups depends entirely on an external provider, the actual recovery time may be longer than expected.


What are the NIS2 incident reporting deadlines in Poland?

In the event of a significant incident, entities subject to the relevant obligations must not only take remedial action but also provide the required information to the competent incident response teams.

The basic reporting schedule is:

  1. 24 hours – to submit an early warning;
  2. 72 hours – to submit an incident notification together with additional information;
  3. 1 month – to submit the final report, in accordance with the statutory rules for calculating the deadline.

Not every cybersecurity event automatically qualifies as a significant incident. An assessment must be carried out under the applicable legal criteria.

A company therefore needs a process that allows it to detect an event quickly, determine its classification and pass the relevant information to the people responsible for reporting it.


What penalties can apply for breaches of NIS2 in Poland?

The amendment to the Act on the National Cybersecurity System provides for administrative financial penalties, with maximum levels depending on the category of entity.

For essential entities, the general limit is EUR 10 million or 2% of annual revenue. For important entities, the limit is EUR 7 million or 1.4% of annual revenue. Detailed statutory rules apply to the calculation base and the amount of the penalty. The Act also provides for the possibility of imposing a penalty on the head of an entity within the limits set by law. In specific cases where a breach causes, among other things, a direct and serious cyber threat to national security, human life or health, or creates a risk of serious financial loss or major disruption to service provision, the authority may impose a penalty of up to PLN 100 million.

This does not mean that every breach automatically results in the maximum penalty. The type of infringement, its circumstances and the applicable rules governing the imposition of penalties are relevant.


What are the most common mistakes companies make when preparing for NIS2?

One of the most practical problems identified during audits is the gap between formal documentation and the way the organisation actually operates.

Common issues include:

  1. incomplete asset inventories;
  2. documentation that does not reflect actual practices;
  3. lack of systematic risk assessment;
  4. lack of business continuity plans;
  5. failure to test emergency procedures;
  6. lack of system recovery instructions;
  7. insufficient control over suppliers;
  8. formally divided roles while most practical responsibility is placed on a single person in the IT department.

A particularly problematic situation arises when a company has extensive documentation but cannot demonstrate that the procedures described in it are actually being followed.

The key conclusion for management is that NIS2 compliance requires not only documents but also evidence that the adopted measures work in practice.

Before implementing additional technical tools, it is therefore worth checking whether the organisation knows its most important assets, can identify process owners and regularly tests emergency scenarios.


How can a company prepare for NIS2 in Poland? Five practical steps

Preparation should begin with an assessment of the company’s actual position rather than with the purchase of additional IT solutions.

Step 1. Determine the company’s status. Verify the business sector, organisation size, corporate links and any specific statutory criteria.

Step 2. Identify critical processes. Determine which systems, data, devices and suppliers are necessary to maintain business operations.

Step 3. Carry out a gap analysis. Compare the company’s current safeguards, documentation and procedures with the requirements of the Act on the National Cybersecurity System.

Step 4. Assign responsibilities and establish a timetable. Identify owners of individual actions and define the implementation budget and priorities.

Step 5. Test the effectiveness of the measures. Test data recovery, incident response and the operation of business continuity plans.


NIS2 and the CRA – does a business need to understand both regulations?

NIS2 focuses on the cybersecurity of organisations, while the EU Cyber Resilience Act (CRA) concerns the security of products with digital elements.

The CRA may be relevant, among others, to manufacturers, importers and distributors of certain hardware and software.

A company manufacturing industrial equipment may therefore need to assess its obligations under both regimes separately. Compliance with NIS2 does not automatically mean that its products comply with the CRA.


Implementing NIS2 should not be limited to preparing documentation for a potential inspection. For businesses, one of the main organisational benefits is establishing clear responsibility for the security of the data, systems and processes on which business continuity depends.

Management should know which events could stop the company’s operations, who makes decisions in a crisis and how quickly the organisation can restore critical services. NIS2 does not replace business risk management. It does, however, require cybersecurity to become an integral part of it.


getsixThis article was written by the getsix® Editorial Team
getsix® provides accounting, tax advisory, HR and payroll, and business consulting services, supporting companies operating in Poland. The getsix® Editorial Team prepares practical information that makes Polish accounting, tax, and HR and payroll matters easier to understand.

If you have any questions regarding this topic or if you are in need for any additional information – please do not hesitate to contact us:

Ask a question »

CUSTOMER RELATIONSHIPS DEPARTMENT

ELŻBIETA<br/>NARON - GROCHALSKA

ELŻBIETA
NARON-GROCHALSKA

Head of Customer Relationships
Department / Senior Manager
getsix® Group
pl en de

***

This publication is non-binding information and serves for general information purposes. The information provided does not constitute legal, tax or management advice and does not replace individual advice. Despite careful processing, all information in this publication is provided without any guarantee for the accuracy, up-to-date nature or completeness of the information. The information in this publication is not suitable as the sole basis for action and cannot replace actual advice in individual cases. The liability of the authors or getsix® are excluded. We kindly ask you to contact us directly for a binding consultation if required. The content of this publication iis the intellectual property of getsix® or its partner companies and is protected by copyright. Users of this information may download, print and copy the contents of the publication exclusively for their own purposes.

Our Recommendations

Our Memberships

Our Certification

Wojskowe Centrum Normalizacji Jakości I KodyfikacjiTÜV NORDTÜV RHEINLAND

Our Partnerships

Competencies