Cybersecurity

NIS2 Obligations: How to Comply – Rules, Deadlines and Penalties

What NIS2 requires in practice: risk-management measures, incident reporting, supervision and penalties, under the directive and under the Czech Cybersecurity Act.

7 min read

The European Union flag with gold stars on a blue background flies from a flagpole against a blue sky with clouds.

NIS2 has applied across the EU since 18 October 2024, and in Czechia through the Cybersecurity Act (Act No. 264/2025 Coll.) since 1 November 2025. The directive replaced the 2016 NIS Directive and requires organisations in sectors like energy, banking, manufacturing and digital services to manage their cybersecurity risks, report significant incidents and accept supervision, with an emphasis on supply chains and vulnerability handling. This article looks at the obligations, deadlines and penalties in detail. For an overview of what NIS2 is and whom it covers, start with What is the NIS2 Directive?

Which Organisations Does NIS2 Apply To?

NIS2 applies to public and private sector entities that meet the following criteria:

  • Provide a service of a type listed in one of the directive's 18 sectors
  • Qualify as medium-sized or large enterprises
  • Provide their services or carry out their activities within the EU

Some entities are subject to the rules regardless of their size, and Member States may bring other entities within scope. In Czechia, the list of regulated services and their conditions are set by decree No. 408/2025 Coll.

Supply Chain Impact

A covered entity's supply chain is affected indirectly. Supply chain security, including the relationships with direct suppliers and service providers, is one of the minimum measures of the NIS2 Directive. Under the Czech Act, a regulated provider must choose its suppliers in line with its security measures and write those requirements into its contracts.

Overview of NIS2 sectors: on the left, sectors covered by both NIS1 and NIS2 (energy, health, transport, drinking water, banking, digital infrastructure, financial market infrastructure, digital service providers); on the right, sectors added by NIS2 (food, waste water, manufacturing, waste management, postal and courier services, public administration, electronic networks or services, ICT service management).

From NIS 1 to NIS2: Major Changes

NIS2 significantly broadens the reach of cybersecurity regulation compared to its predecessor, from seven sectors to eighteen. New sectors are included based on their digital dependence, interconnectedness and importance to society and the economy, and medium-sized and large organisations in these sectors, including public ones, now fall under NIS2.

While exemptions exist, companies should carefully assess their position and any other relevant regulations. If your organisation works in one of these sectors and has 50 or more employees, or an annual turnover and balance sheet total both above EUR 10 million, it is likely to be covered. How sector and size decide between essential and important entities is explained in our overview of the NIS2 Directive.

Key Obligations under NIS2

NIS2 places significant obligations on organisations, particularly concerning cybersecurity risk management and incident notification.

Cybersecurity Risk-Management Measures

  • Essential and important entities must take appropriate and proportionate technical, operational and organisational measures to manage the risks to their network and information systems and to prevent or minimise the impact of incidents.
  • Minimum measures in Article 21 cover policies on risk analysis and information system security, incident handling, business continuity and crisis management, supply chain security, security in acquisition, development and maintenance including vulnerability handling, assessing the effectiveness of the measures, basic cyber hygiene and training, cryptography, human resources security, access control and asset management, and multi-factor authentication and secured communications.
  • Management bodies must approve these measures and oversee their implementation, and can be held liable for infringements. Their members must also follow cybersecurity training (Article 20); we run cybersecurity training for management.

Incident Notification

  • Essential and important entities must notify their CSIRT or competent authority, without undue delay, of any significant incident: one that has caused or can cause severe operational disruption or financial loss, or considerable damage to others.
  • A phased reporting model applies: an early warning within 24 hours of becoming aware of the incident, an incident notification within 72 hours, intermediate reports on request and a final report within one month of the notification.
  • Communication with service recipients is also required: where appropriate, entities inform them about significant incidents and about the measures they can take against a significant cyber threat. In some cases the authority informs the public or requires the entity to do so.
  • Potential overlap with other reporting obligations, such as GDPR, calls for one comprehensive incident notification procedure.

How It Works in Czechia

The Czech Act does not use the labels "essential" and "important". It sorts providers of regulated services into a higher and a lower obligations regime, and one organisation always has one regime: if any of its services is in the higher regime, the higher regime applies to all of them.

  • Measures: the higher regime follows decree No. 409/2025 Coll., the lower regime decree No. 410/2025 Coll. In both, top management must complete cybersecurity training.
  • Incidents: a higher-regime provider reports cybersecurity incidents to NÚKIB; a lower-regime provider reports incidents with a significant impact on its service to the National CERT. The initial report is due within 24 hours. If the incident has a significant impact, a notification follows within 72 hours and a final report within 30 days of it.
  • Deadlines: both obligations start no later than one year after the decision registering the regulated service is delivered.

Supervision and Enforcement under NIS2

NIS2 differentiates between essential and important entities in supervision and enforcement, based on their criticality and impact on society. Both must implement cybersecurity measures and report incidents, but essential entities face stricter supervision and enforcement, including proactive inspections and higher fines.

Supervision

  • Essential entities face proactive supervision, including on-site inspections, random checks, regular and targeted security audits and security scans.
  • Important entities are supervised after the fact, when there is evidence or an indication of non-compliance.

Enforcement

  • Competent authorities can impose a range of measures, including warnings, binding instructions, orders and administrative fines.
  • Maximum fines under Article 34 of the NIS2 Directive must reach at least:
    • Essential entities: EUR 10 million or 2 % of total worldwide annual turnover, whichever is higher.
    • Important entities: EUR 7 million or 1.4 % of total worldwide annual turnover, whichever is higher.
  • Additional enforcement measures for essential entities include the appointment of a monitoring officer and, if deficiencies are not remedied, a temporary ban on the chief executive or legal representative from exercising managerial functions.

Penalties in Czechia

Under Act No. 264/2025 Coll., NÚKIB can order a provider to remedy the deficiencies it finds and can impose fines of up to:

  • CZK 250 million or 2 % of net worldwide annual turnover, whichever is higher, for most offences of a higher-regime provider, and for failing to notify a regulated service at all.
  • CZK 175 million or 1.4 % for most offences of a lower-regime provider.

In the higher regime, NÚKIB can also temporarily ban a member of the statutory body from office, for at least six months, if they repeatedly or seriously breach their duties and so frustrate a decision ordering the provider to remedy deficiencies.

Actions To Take Now

NIS2 now applies through national law. If you have not yet done so, assess whether your organisation falls within its scope and, if it does, work through the obligations that apply to you. In Czechia, the one-year deadlines run from the delivery of your registration decision.

  • Determine if NIS2 Applies to Your Organisation: Assess your operations, identify exemptions, categorise your organisation, and understand NIS2 obligations and their impact. In Czechia, check your services against decree No. 408/2025 Coll. and notify NÚKIB if you have not.
  • Identify Applicable Member State Laws: Analyse NIS2 jurisdiction rules, consider where your cybersecurity decisions are made, and designate a 'Representative' if needed.
  • Evaluate Other EU Cybersecurity Laws: Integrate NIS2 into your overall strategy, understand its relationship with other laws, and plan your compliance with them together.
  • Review Incident Response Procedures: Make sure you can meet the 24-hour, 72-hour and one-month stages: verify communication channels, assign responsibilities and conduct drills.
  • Review Cybersecurity Risk Management Procedures: Regularly assess and update processes, analyse weaknesses, implement strong measures, and build a culture of awareness.
  • Review Third-Party Risk Management (TPRM) Processes: Evaluate vendor relationships, put cybersecurity requirements into contracts, and regularly update TPRM practices.
  • Review Organisational Culture and Working Practices: Understand risks to NIS2 compliance arising from your culture, prioritise behavioural change, and address management's responsibilities, including its training.

A compliance gap assessment shows where you stand against these obligations, and NIS2 implementation closes the gaps, as we did for IMA.

NIS2: Looking Ahead

The NIS Directive is repealed and NIS2 applies through national law. Its expanded scope and stricter requirements leave no room for complacency.

Cybersecurity is continuous work. Addressing the NIS2 obligations early protects your operations and shows your stakeholders that you take their protection seriously.

The time to act is now. If your registration decision was delivered around the turn of 2025 and 2026, your one-year deadline falls around the turn of 2026 and 2027. What to have in place by then is in our ZoKB checklist.

Start with one clear conversation

Tell us what you need to secure, automate, build or staff. A senior consultant will get back to you.

Aleš PoláčekCEO, Whirr Crew
info@whirrcrew.com

What happens next

  1. We replyA senior consultant reads your message and writes back to arrange a call.
  2. A first conversationWe talk through your situation, your goals and your constraints.
  3. A concrete next stepA proposal you can decide on: a scope, a team or a pilot.

Whirr Crew s.r.o., Rybná 716/24, 110 00 Praha 1

We use your details to deal with your message. More in our privacy statement.

Required