NIS2 Directive: does it apply to your company and what to check

  • Home
  • NIS2 Directive: does it apply to your company and what to check
NIS2 Directive: does it apply to your company and what to check

The NIS2 Directive directly covers organizations from specific sectors and of a specific size. And the rest? Often indirectly, because many companies are suppliers to entities covered by the rules. And here is an interesting detail: questions about NIS2 usually come from clients and business partners before a company has worked out its own status.

In practice there are two scenarios - an obligation that comes straight from the law, or requirements written into contracts. Below I go through both, along with a list of things to check in each of them.

What is the NIS2 Directive and what does it change compared with the previous rules?

NIS2 is the EU legislation on the cybersecurity of network and information systems. It replaced the earlier NIS1 directive. What changed? The scope is wider, the rules are clearer and the supervisory tools are stronger. It adds risk management measures and reporting obligations, and it does so for entities from more sectors than before. According to the European Commission information on NIS2, member states had until 17 October 2024 to transpose it into national law.

How NIS2 enters Polish law: the national cybersecurity system

The directive does not apply to companies directly. It obliges member states to pass their own legislation. In Poland it was implemented through the amendment of 23 January 2026 to the Act on the National Cybersecurity System, which entered into force on 3 April 2026. The detailed obligations, supervisory authorities and procedures follow from that act, so it is worth checking its current wording. In my opinion it makes sense to prepare on the basis of that act, and not only on the basis of the general EU framework.

Who does NIS2 apply to directly?

Two criteria decide: the sector you operate in and the size of the organization. The regulation targets entities that provide services important to the economy and society, and the list of industries is longer than in NIS1. As for NIS2 and small businesses, smaller companies usually stay outside the direct scope. Usually, because there are exceptions, and those depend on the type of services provided. You can work out your own status by comparing your business profile with the list of sectors in the legislation. Not sure? Ask a lawyer, there is no point in guessing.

NIS2 and the supply chain: why a smaller supplier gets questions too

An entity covered by the rules also has to manage risk at its suppliers. So it passes the requirements on through contracts. What does that look like in practice? Security questionnaires, new contract clauses, questions about backups, about how access is granted and about incident response. This mostly affects IT companies, software houses, hosting providers, agencies that maintain client systems and subcontractors with access to data or infrastructure.

One question quickly comes back in these conversations: who is actually responsible for security on the service provider’s side? That depends on the cooperation model. Deciding on IT outsourcing or in-house team affects how tasks are divided and what goes into the contract. And the more clearly that division is described, the easier it is to fill in a client’s questionnaire.

NIS2 obligations in brief: risk management and incident reporting

There are two pillars: cybersecurity risk management measures and incident reporting. The first means conscious decisions about what to protect and how. Not ad hoc tool purchases. NIS2 incident reporting, in turn, requires an organization to be able to detect an event, assess its severity and pass the information to the competent authority. Oh, and one more thing, management: security becomes a matter for the board, and not only for the IT department.

What to check in your company whether or not the rules cover you

Five areas. Both a regulator and a client covered by NIS2 will ask about each of them. They overlap with what good cybersecurity practices for businesses describe, so this work will not go to waste.

  1. Inventory of systems and data - a list of applications, servers, accounts and the information you keep in them.
  2. Backups with a restore test - a backup that nobody has tried to restore is only an assumption.
  3. Multi-factor authentication - logging in with an additional confirmation, especially for email, admin panels and remote access.
  4. A written incident procedure - who decides, who informs clients and what is done first.
  5. Contracts with IT suppliers - the scope of responsibility, access rules and the way problems are reported.

Where do you start with the first point? A common starting point is an IT infrastructure audit, which shows what is actually running in the organization (and not what someone thinks is running). And if a website or online store is an important part of your business, a website audit lets you review its condition and its security.

Where to start preparing for NIS2 in the coming weeks

The order matters. First establish your status, then review your client contracts, and finally fill the gaps from the checklist. This can be broken down into a few simple steps:

  • appoint a person responsible for the topic, with access to the board;
  • check your sector and whether you serve clients from regulated industries;
  • collect answers to typical security questionnaire questions in one document;
  • plan which gaps you will close first and who will take care of them.

Even if the NIS2 Directive does not cover you directly, it is actually a good excuse to put the basics in order. Tested backups, access control, a clear procedure in case of a failure. All of this is useful beyond the legal obligation too, because it shortens downtime and makes conversations with demanding business partners easier.

Frequently asked questions

Does NIS2 apply to a small company?

Usually not directly, because the rules are aimed mainly at larger organizations from selected sectors. But indirectly it often does - through the requirements of clients covered by the regulation. Exceptions to this rule depend on the industry and the type of services provided.

Is the NIS2 Directive already in force in Poland?

The transposition deadline for EU member states is 17 October 2024, as confirmed by the European Commission’s directive page. In Poland the rules are to be introduced through an amendment to the Act on the National Cybersecurity System, which is still being worked on. The specific obligations for companies will only follow from its final wording.

What to do when a client asks about NIS2 compliance?

First find out what exactly the contract or questionnaire requires. The label alone says very little. Then describe the safeguards you use and your incident handling procedure. And do not declare more than what actually works in your organization.

Book a free consultation

Provide your phone number or schedule a meeting