NIS2 for Czech companies: what your IT must handle

17. 11. 2026
Červený štít s fajfkou v okně aplikace, kolem něj ikony zálohy, aktualizací, přístupového klíče a hlášení incidentů. Symbolizuje kontrolní seznam NIS2 pro IT.

Status as of 13 November 2026. A practical overview for directors and IT, not a legal interpretation.

Important note

This article is a practical overview and checklist from an IT point of view. It is not a legal interpretation or legal advice. Whether and how the Czech Cybersecurity Act applies to you, and what obligations follow from it, is for NÚKIB or a cybersecurity or legal specialist to assess. Working through the checklist does not mean you comply with the Act.

For many Czech companies, NIS2 means very concrete work for IT: backups, updates, event logs, access, suppliers and incident readiness. These areas are worth getting right even if the Act does not apply to you directly.

The NIS2 Directive (also written NIS 2) is an EU directive on cybersecurity. In Czechia it is implemented by Act No. 264/2025 Coll., on Cybersecurity, in force since 1 November 2025 and usually called the Czech Cybersecurity Act.

All legal texts referred to are in Czech.

Quick overview (as of 13 November 2026)

  • NIS2 is an EU directive; in Czechia it is implemented by Act No. 264/2025 Coll., on Cybersecurity, in force since 1 November 2025
  • The Act distinguishes two regimes: a higher obligations regime and a lower obligations regime
  • NÚKIB decides whether a service falls under the Act and into which regime
  • The Act expects incidents to be reported within deadlines of around 24 and 72 hours
  • Your specific obligations depend on your regime; check them with NÚKIB

NIS2 and the Czech Cybersecurity Act: what applies in Czechia

An EU directive does not apply to companies directly. Each member state transposes it into its own law. A company in Czechia therefore does not comply with the text of the directive, but with the Czech Cybersecurity Act and its implementing decrees.

The Act sets the basic framework. The implementing decrees cover the details, for example which services fall under the Act and which security measures are expected in each regime. The current versions of the Act and the decrees are available in e-Sbírka, the official Czech collection of laws.

NÚKIB (the Czech National Cyber and Information Security Agency) is the authority that decides which services fall under the Act and into which regime. It publishes information and materials on the Act on its website.

Does NIS2 apply to your company?

The Czech Cybersecurity Act does not apply to every company. The obligations fall on providers of a so-called regulated service. The Act works with 15 sectors: public administration; energy; manufacturing; food industry; chemical industry; water management; waste management; transport; digital infrastructure and services; financial market; healthcare; science, research and education; postal and courier services; defence industry; space industry.

Doing business in one of these sectors does not by itself mean the Act applies to you. The type of service you provide, the size of your company and other criteria set by the Act and its implementing decrees all play a role. NÚKIB decides on classification, not this article.

Regulated services are divided into two regimes: the higher obligations regime and the lower obligations regime. The scope of security measures and the incident reporting procedure differ between them. Always check your specific obligations with NÚKIB.

A company that does not provide a regulated service itself can still be affected indirectly. Typically this happens when it supplies a company that the Act does apply to, and that customer asks for security requirements in the contract. More on this in the section on suppliers.

NIS2 checklist for directors and IT

The six areas below are good practice for running websites, applications and servers. The Act and its implementing decrees deal with them too, but the scope differs by regime and service. The questions for IT and suppliers are recommendations from our practice, not legal interpretation. The checklist helps you find gaps, but it does not guarantee NIS2 compliance.

Backups and service recovery

When an outage or an attack happens, backups decide how quickly the service is back up and running. They only help if you can actually restore the service from them. It is therefore worth backing up not just data but also configurations and settings, and testing restores regularly. We explain how to set up backups that survive ransomware in Ransomware recovery: backups that really work.

Questions for IT:

  1. Do we back up server and application configurations, not just the database?
  2. Are backups stored separately, so an attacker cannot delete them together with the data?
  3. When did we last restore the whole service, not just a single file?

Updates and system maintenance

In our experience, a website or application without regular maintenance is often where an attack gets in. Critical flaws in PHP and its libraries keep appearing; see our articles on PHP2Shell and Broccoli2Shell for examples.

Good practice is to apply security updates without undue delay, keep track of systems and libraries that are no longer supported, and scan for vulnerabilities regularly.

Questions for IT:

  1. Do we know which versions of PHP, framework, CMS and libraries each application runs?
  2. Who deploys a security fix, and how quickly?
  3. Do we know which applications and libraries are no longer supported, and what we will do about them?

Logging and event detection

Logging means that a system keeps records of who did what and when. Without these records it is often impossible to tell when an incident started and what it affected. That makes it harder both to deal with the incident and to report it quickly. We look at audit trails in CRM systems and AI integrations in CRM and AI integration security.

Questions for IT:

  1. Does the application record logins, permission changes and sensitive operations?
  2. Where are the records stored, and who can access them?
  3. Will anyone find out in time that something unusual is happening in the system?

Access and identity management

The fewer people have access they do not need, the less damage is done when an account ends up in the wrong hands. We cover the practical side, meaning roles, two-factor authentication and removing access when people leave, in Business access management.

Questions for IT:

  1. Do we know, for every application, who has which access and why?
  2. Do we use two-factor authentication, at least for admin accounts?

Suppliers and contracts

Much of a company's IT now runs with suppliers, so the security of your service depends on them too. This is NIS2 supply chain security in practice: the Act takes the supply chain into account, and what that means for you depends on your regime.

Suppliers include hosting, the application developer, the server administrator and cloud services. They also include AI tools you send company data to; see Secure AI on company data. What a support contract should contain is summarised in Application support SLA.

Questions for IT and management:

  1. Which parts of the service does a supplier run for us?
  2. Does the contract say what the supplier covers, how quickly it responds and how it informs us about an incident?
  3. What happens if the supplier stops working with us? See Application handover: switching vendors.

Incident reporting: 24 hours and 72 hours

The Act expects selected incidents to be reported quickly, within deadlines of around 24 and 72 hours of detection. Which incidents must be reported, to whom and how depends on the regime and is set by the Act and its implementing rules. NÚKIB publishes the details.

There is no time to work out who does what in such a short window. The procedure needs to be ready before an incident happens.

Questions for IT and management:

  1. Who in the company decides that something is an incident, and who reports it?
  2. Do we know where and how to report an incident, and can a deputy do it when the main person is unavailable?
  3. Does our supplier know it must tell us about an incident straight away, not just fix it?

Websites and applications: where NIS2 touches your software

If a regulated service runs through a web application, a customer portal or an API, expect the security measures to apply to them too.

The weakest point we see most often is the period after a project is handed over: the supplier contract ends and nobody keeps an eye on dependencies or security fixes any more. Agree who is responsible for the application after launch and how quickly they respond. If maintaining an old application no longer makes sense, read When to rewrite an application and when to refactor it.

How to start: 5 steps for the next 30 days

  1. Check whether the Act applies to you. Go through the information on the NÚKIB website. If you are unsure, contact NÚKIB directly or a cybersecurity or legal specialist.
  2. List the systems your service runs on. Websites, applications, servers and cloud services, and who manages each one.
  3. List your suppliers and review the contracts. Look for response times, incident notification and backups.
  4. Go through the checklist above with IT. Write down the gaps and, for each one, who will deal with it and by when.
  5. Decide who reports an incident and how. Before one happens.

How 1. Web IT can help

1. Web IT develops custom web applications and systems and looks after how they run. We are not a law firm: we do not assess whether the Act applies to you, and we do not promise compliance with the law. We help with the technical work:

  • As part of server and infrastructure management, we set up regular backups, watch your servers 24/7 and handle updates and incidents.
  • As part of application support, we take care of maintenance and further development. With basic support, we respond within 4 hours of a request being reported.
  • If your supplier has stopped working with you or cannot keep up, we take over the application and look after its operation.

    Want to review where your websites and applications stand? Get in touch and we will look at what your service runs on, who looks after it and where the gaps are in backups, maintenance and support. We reply within 1 working day and offer a free 30-minute introductory call.

Frequently asked questions

What is NIS2 and does it apply directly in Czechia?

NIS2 is an EU directive on cybersecurity. In Czechia it is implemented by Act No. 264/2025 Coll., on Cybersecurity, in force since 1 November 2025. Companies therefore comply with the Czech Act and its implementing decrees, not with the text of the directive itself.

Does NIS2 apply to smaller companies too?

The Act applies to providers of regulated services in 15 sectors. The type of service, the size of the company and other criteria set by the Act and its implementing decrees all play a role. NÚKIB decides on classification. A smaller company can also be affected indirectly when it supplies a company that the Act applies to.

What is the difference between the higher and lower obligations regimes?

The Act divides regulated services into two regimes. The scope of security measures and the incident reporting procedure differ between them. NÚKIB decides which regime a service belongs to.

Where can I check which obligations apply to my company?

Specific obligations and deadlines depend on whether your service falls under the Act and in which regime. Reliable sources are NÚKIB and the text of the Act and decrees in e-Sbírka. If anything is unclear, a cybersecurity or legal specialist can help.

How quickly must a cybersecurity incident be reported?

The Act expects selected incidents to be reported within deadlines of around 24 and 72 hours of detection. Which incidents must be reported, to whom and how depends on the regime. NÚKIB publishes the details.

What does NIS2 have to do with websites and applications?

If a regulated service runs through a website or application, the security measures apply to them too: backups, updates, event logs, access control and working with suppliers. A checklist helps you find gaps, but on its own it does not guarantee compliance with the law.

More articles