Skip to content
Disruptive Lab

Guide European rules

NIS2 in Ireland and what an auditor asks

NIS2 applies to medium and large companies in listed sectors, and an auditor will ask your systems to show who has access, what is recorded and how incidents are reported.

Published
Updated
Reading time
8 min read
Editor
David Lahuta

In short

NIS2 applies to medium and large companies in 18 listed sectors, from energy and health to manufacturing, food and digital services, and to a few others regardless of size.13 If it applies, your management must approve the security measures and can be held liable for them.1 Your systems must be able to show who has access to what, what happened and when, and that an incident can be reported within 24 hours.1 Your suppliers are part of it. The directive asks you to weigh their security practices, including how they develop software.1 Each country has its own law, authority and registration, so check the national rules as well.

Does NIS2 apply to us?

Two questions decide it, your sector and your size.

The sector comes first. The directive lists 18 sectors in two annexes.1 Annex I holds the sectors of high criticality, such as energy, transport, banking, health, drinking water, digital infrastructure, business-to-business IT service management, public administration and space.1 Annex II holds other critical sectors, such as postal services, waste management, chemicals, food, manufacturing, digital providers and research.1 Manufacturing here means specific branches, among them medical devices, computer and electronic products, electrical equipment, machinery, motor vehicles and other transport equipment.1

Then size. The directive applies to entities in those sectors that are medium sized or larger under the EU definition of small and medium enterprises.1 Under that definition a small enterprise has fewer than 50 people and an annual turnover or balance sheet total of no more than EUR 10 million.2 A medium enterprise has fewer than 250 people and a turnover of no more than EUR 50 million or a balance sheet total of no more than EUR 43 million.2 So, by our reading, a company in a listed sector with 50 or more people, or with both turnover and balance sheet above EUR 10 million, is usually in. Small and micro companies usually are not. Partner and linked companies count towards the size, so a small company in a larger group should check.2

Some entities are in regardless of size. Examples are providers of public electronic communications, trust service providers, domain name registries, and a sole provider of a service essential to society in a member state.1

Those in scope fall into two groups. Essential entities are, in the main, the large ones in Annex I sectors.1 Important entities are the others in scope.1 The duties are the same, the supervision differs.

What do the rules ask of your systems, in plain words?

The core is Article 21. Companies in scope must take appropriate and proportionate technical, operational and organisational measures to manage risks to the systems they run their business on.1 Proportionate means the effort depends on the company's exposure to risk, its size and the likely severity of incidents.1 The article then names at least ten areas.1 The table puts them in plain words, next to what a system must be able to show.

Duty in Article 21 What your systems must be able to show
Risk analysis and security policies A written policy, approved by management, and a list of the risks you found
Incident handling That an incident is noticed, its time recorded and its handling written down
Business continuity, backups, disaster recovery Backups that exist, and a restore that has been tested
Supply chain security A list of suppliers and what each one's contract says about security
Secure acquisition, development and maintenance, with vulnerability handling How security flaws are found, fixed and recorded, and who approved each change
Checking that the measures work Results of tests, reviews and audits
Basic cyber hygiene and training Who was trained, and when
Cryptography and, where appropriate, encryption Which data is encrypted, and how keys are kept
Staff security, access control, asset management Who has access to what, who granted it, and a list of systems and data
Multi-factor authentication and secured communications Which sign-ins need a second step, such as a code from a phone

Two more duties sit around the table. First, the management body must approve these measures, oversee them and can be held liable for breaches.1 Its members must also follow training.1 The Commission describes this as accountability of top management.3

Second, a significant incident must be reported in stages to the national incident response team (CSIRT) or the competent authority.1 An early warning goes within 24 hours of becoming aware of it, an incident notification within 72 hours and a final report no later than one month after the notification.1 An incident is significant if it caused or can cause severe disruption or financial loss, or considerable damage to others.1 In practice the 24 hour clock only works if your systems record when something unusual happened and who noticed it.

A useful way to order this work is the NIST Cybersecurity Framework 2.0, guidance from the United States National Institute of Standards and Technology that any organisation can use, regardless of its size or sector.5 It groups security outcomes into six functions, govern, identify, protect, detect, respond and recover.5 It does not replace the directive, but its six functions cover the same ground as the table above.

What should you ask a software supplier?

The directive treats suppliers as part of your own security. Supply chain security covers your relations with direct suppliers and service providers.1 When you choose the measures, you must take into account each supplier's vulnerabilities and the quality of its products and security practices, including its secure development procedures.1

ENISA, the EU cybersecurity agency, has published technical guidance that shows how this looks in practice.4 It is written for the entities of Commission Implementing Regulation (EU) 2024/2690, such as cloud, data centre, managed service and online marketplace providers.4 For them, contracts with suppliers must cover, where appropriate, the items below.4 Other companies are not bound by that list, but it makes a sound set of questions for any supplier of a system you depend on.

  • What security requirements does the supplier commit to in the contract?4
  • Will the supplier tell you without undue delay about an incident that puts your systems at risk?4
  • Do you have the right to audit the supplier, or to receive its audit reports?4
  • Will the supplier handle the vulnerabilities that put your systems at risk?4
  • May the supplier use subcontractors, and under the same security requirements?4
  • What happens to your data when the contract ends?4

Add a few questions of your own about the software itself. Can it show who has access to what, and who changed it? Does it keep a record of who did what, which nobody can quietly alter? How quickly is a known security flaw fixed, and who confirms it? Can you take your data and the records with you?

What will an auditor want to see on the day?

Evidence, not intentions. The directive gives authorities the power to request documented security policies, access to data and documents, and evidence that policies are applied, such as the results of security audits and the evidence underneath them.1

How often this happens depends on your group. Essential entities can be subject to regular and targeted security audits, on site inspections and random checks.1 Important entities are supervised after the fact, when there is evidence or an indication that they may not comply.1 The cost of a targeted audit by an independent body is, as a rule, paid by the audited company.1

ENISA's guidance lists examples of evidence for each requirement.4 For access rights, they include clear definitions of user roles, a central register of all access granted with dates of changes, approved access requests, periodic access reviews and logs of every change to access rights, with timestamps and user names.4 For logging, they include the logging settings, samples of the log files and safeguards that protect the logs themselves.4 ENISA notes that the list is indicative and that national authorities decide how strictly to supervise.4

A practical checklist for the day follows from that.

  • The security policy, with the date management approved it.
  • A list of your systems and data, and who owns each one.
  • For each important system, the list of who has access and the last review of it.
  • Records of sign-ins, changes and administrative actions, kept so they cannot be altered.
  • The incident procedure, and the record of the last incident or exercise.
  • The last backup restore test.
  • The list of suppliers with the security terms of each contract.
  • Training records for management and staff.

What should you do first?

Scope comes first, because everything else follows from it.

  1. Check your sector against the two annexes and your size against the EU definition.12 Then check your country's own law, registration and deadlines.
  2. List the systems your business cannot run without, and the suppliers behind each one.
  3. For each of those systems, try the checklist above. Note what the system can show today and what it cannot.
  4. Rehearse the first 24 hours of an incident, from noticing it to the early warning.1
  5. Bring the results to management for approval, since the directive makes them answerable.1

The gaps from step 3 are usually concrete, such as a system with no record of who changed what, and they can be fixed.

On 20 January 2026 the Commission proposed targeted amendments to NIS2 to make it clearer and simpler.3 At the time of writing its page describes them as a proposal, so this guide follows the directive as it stands.

In Ireland

NIS2 is a directive, so it binds companies only through national law.1 Ireland has not yet adopted one. The National Cyber Security Centre (NCSC) states that the deadline of 17 October 2024 was not met.7 The bills register of the Oireachtas shows no bill to transpose NIS2 up to 16 November 2026.6

What applies today. The NIS1 rules of 2018 still apply, the European Union (Measures for a High Common Level of Security of Network and Information Systems) Regulations 2018, S.I. No. 360 of 2018.8 They cover designated operators of essential services and digital service providers.78 An incident must be notified within 72 hours.8 On conviction on indictment, a company can be fined up to EUR 500,000.8

Authority. The NCSC, with the national incident response team CSIRT-IE, is the place to watch.7 Its NIS2 registration and reporting portals open only once the national law is in place.7

What this means for you. The NIS2 duties described in this guide will apply once an Irish act passes. A company that falls within NIS2 by sector and size can use the time to make its systems show what an auditor will ask for, and should follow the NCSC for the law and the registration.

Next step

If it would help, we are glad to go through one of your systems with you in a meeting and look at what it can show an auditor today and what it would need. We build custom business systems and applications with access control, records of who did what and documentation in from the start, so they are audit-ready. Certification is the auditor's decision; we deliver the software and the evidence.

Custom business systems and applications

Sources

  1. 1. Directive (EU) 2022/2555 (NIS2), Articles 2, 3, 20, 21, 23, 32 to 34 and Annexes I and II, EUR-Lex. Read on 17 November 2026
  2. 2. Commission Recommendation 2003/361/EC on the definition of micro, small and medium-sized enterprises, Annex Article 2, EUR-Lex. Read on 17 November 2026
  3. 3. European Commission, NIS2 Directive, securing network and information systems. Read on 17 November 2026
  4. 4. ENISA, NIS2 Technical Implementation Guidance, June 2025, version 1.0. Read on 17 November 2026
  5. 5. NIST, The NIST Cybersecurity Framework (CSF) 2.0, CSWP 29, 26 February 2024. Read on 17 November 2026
  6. 6. Houses of the Oireachtas, bills register, bills updated 1 June 2024 to 17 November 2026. Read on 17 November 2026
  7. 7. National Cyber Security Centre, NIS2. Read on 17 November 2026
  8. 8. S.I. No. 360/2018, European Union (Measures for a High Common Level of Security of Network and Information Systems) Regulations 2018, Irish Statute Book. Read on 17 November 2026

Change log

  1. Published.

Let's talk about your project

Leave us your contact details and we will get back to you with a date. Free and without obligation.

With the country code, for example +353.

We use your details only to answer you. Privacy notice

This form is protected from automated submissions by Google reCAPTCHA. Google Privacy Policy (opens in a new window) Google Terms of Service (opens in a new window)

Or contact us directly

Write to us office@disruptivelab.dev
Call us +420 777 702 032

Our preferred language of communication is English.

All contact details and addresses