---
title: Your IT supplier was breached, in Ireland | Disruptive Lab
description: For companies in Ireland. Who reports a supplier's breach, to whom and how fast, with the GDPR duties and where NIS2 stands today.
url: https://disruptivelab.dev/en-ie/news/supplier-breach
language: en-IE
covers: 2026-03-09/2026-03-15
---

1.  [News](https://disruptivelab.dev/en-ie/news)
2.  [European rules](https://disruptivelab.dev/en-ie/news/european-rules)
3.  Your IT supplier was breached, in Ireland

[Guide](https://disruptivelab.dev/en-ie/news/guides)  [European rules](https://disruptivelab.dev/en-ie/news/european-rules)

# Your IT supplier was breached, in Ireland

When your IT supplier is breached, it must tell you without undue delay, and you then have 72 hours to decide whether the authorities and the people affected must hear of it.

- **Published:** 17 November 2026
- **Updated:** 17 November 2026
- **Reading time:** 8 min read
- **Editor:** David Lahuta

Week of 9 March 2026

## In short

-   When a supplier that handles personal data for you is breached, it must tell you without undue delay. The report to the data protection authority is then your duty, not the supplier's.[3](https://disruptivelab.dev/en-ie/news/supplier-breach#source-3)[4](https://disruptivelab.dev/en-ie/news/supplier-breach#source-4)
-   Your 72 hours to report usually start when the supplier tells you. A report may be left out only where the breach is unlikely to put people at risk.[3](https://disruptivelab.dev/en-ie/news/supplier-breach#source-3)[4](https://disruptivelab.dev/en-ie/news/supplier-breach#source-4)
-   If your company falls under NIS2 and the incident significantly disrupts your services, a separate report goes to the national incident response team within 24 hours.[5](https://disruptivelab.dev/en-ie/news/supplier-breach#source-5)
-   Much of what happens in those hours depends on what your contract with the supplier says, so the time to settle it is before an incident.[4](https://disruptivelab.dev/en-ie/news/supplier-breach#source-4)

## Contents

1.  [What happened at a large IT supplier in March 2026?](https://disruptivelab.dev/en-ie/news/supplier-breach#what-happened-at-a-large-it-supplier-in-march-2026)
2.  [Who must report what, and to whom?](https://disruptivelab.dev/en-ie/news/supplier-breach#who-must-report-what-and-to-whom)
3.  [When do the 72 hours start?](https://disruptivelab.dev/en-ie/news/supplier-breach#when-do-the-72-hours-start)
4.  [How do the first 72 hours look, step by step?](https://disruptivelab.dev/en-ie/news/supplier-breach#how-do-the-first-72-hours-look-step-by-step)
5.  [What does NIS2 add for companies under it?](https://disruptivelab.dev/en-ie/news/supplier-breach#what-does-nis2-add-for-companies-under-it)
6.  [What should the contract with the supplier say?](https://disruptivelab.dev/en-ie/news/supplier-breach#what-should-the-contract-with-the-supplier-say)

## What happened at a large IT supplier in March 2026?

On 13 March 2026 CGI, a large IT services company, announced that its cybersecurity team had found a security incident the day before.[1](https://disruptivelab.dev/en-ie/news/supplier-breach#source-1) It concerned two internal test servers in Sweden, which were not used for live services but for testing a service delivered to a limited group of customers.[1](https://disruptivelab.dev/en-ie/news/supplier-breach#source-1) A system holding an older version of an application's source code had also been accessible to outsiders.[1](https://disruptivelab.dev/en-ie/news/supplier-breach#source-1) CGI said that there was at that point no indication that customers' live environments, the data in them or their running services had been compromised, and that it was investigating in close cooperation with its customers.[1](https://disruptivelab.dev/en-ie/news/supplier-breach#source-1) Sweden's national incident response team, CERT-SE, reported the intrusion into internal test environments in its weekly letter the same day.[2](https://disruptivelab.dev/en-ie/news/supplier-breach#source-2)

For the customers of any supplier, a notice like this is where their own questions start. Were our data on those servers? Could the code or any access details lead to our systems? Whom must we tell, and by when? The first two only the facts of the case can answer. The last two are decided by the rules, and they are what this guide is about.

## Who must report what, and to whom?

Two sets of European rules apply here, the GDPR to personal data and NIS2 to companies in the sectors it covers. Two GDPR terms come first. The controller is the company that decides why and how personal data are processed, which is usually you.[3](https://disruptivelab.dev/en-ie/news/supplier-breach#source-3) The processor is a supplier that processes them on your behalf, such as the company that runs or hosts your system.[3](https://disruptivelab.dev/en-ie/news/supplier-breach#source-3)

A personal data breach is wider than a theft. The GDPR defines it as a breach of security that leads to personal data being destroyed, lost, altered, disclosed or accessed without authorisation.[3](https://disruptivelab.dev/en-ie/news/supplier-breach#source-3) A loss of access to personal data, such as customer records out of reach, can count as well.[4](https://disruptivelab.dev/en-ie/news/supplier-breach#source-4)

Who

Reports what

To whom

How fast

The supplier, as processor

A personal data breach it becomes aware of

You, the controller

Without undue delay[3](https://disruptivelab.dev/en-ie/news/supplier-breach#source-3)

You, as controller

A personal data breach, unless it is unlikely to put people at risk

The data protection authority

Without undue delay and, where feasible, within 72 hours of becoming aware[3](https://disruptivelab.dev/en-ie/news/supplier-breach#source-3)

You, as controller

A breach likely to put people at high risk

The people affected

Without undue delay[3](https://disruptivelab.dev/en-ie/news/supplier-breach#source-3)

You, as controller

Every personal data breach, reported or not, with its facts, effects and remedies

Your own records, which the authority can check

Always[3](https://disruptivelab.dev/en-ie/news/supplier-breach#source-3)[4](https://disruptivelab.dev/en-ie/news/supplier-breach#source-4)

You, if under NIS2

A significant incident

The national incident response team (CSIRT) or the competent authority

Early warning within 24 hours, notification within 72 hours, final report within one month of the notification[5](https://disruptivelab.dev/en-ie/news/supplier-breach#source-5)

The supplier, if itself under NIS2

A significant incident in its own services

Its own CSIRT and, where appropriate, the customers of the service

Without undue delay[5](https://disruptivelab.dev/en-ie/news/supplier-breach#source-5)

The legal duty to notify the authority stays with you, even when the supplier writes the report for you.[4](https://disruptivelab.dev/en-ie/news/supplier-breach#source-4)

## When do the 72 hours start?

They start when you become aware of the breach. The European Data Protection Board (EDPB), where Europe's data protection authorities work together, reads this as the moment you have a reasonable degree of certainty that a security incident has compromised personal data.[4](https://disruptivelab.dev/en-ie/news/supplier-breach#source-4) A short investigation to establish whether a breach happened at all is allowed, and it should begin as soon as possible.[4](https://disruptivelab.dev/en-ie/news/supplier-breach#source-4)

When the breach happens at a supplier, the EDPB says that you should in principle be considered aware once the supplier has informed you.[4](https://disruptivelab.dev/en-ie/news/supplier-breach#source-4) The supplier does not first have to judge the risk to people. It establishes that a breach occurred and tells you, and the assessment is yours.[4](https://disruptivelab.dev/en-ie/news/supplier-breach#source-4) The GDPR sets no fixed time for the supplier's notice beyond "without undue delay", so the EDPB recommends that the supplier tells you promptly and adds details in phases as they become known.[4](https://disruptivelab.dev/en-ie/news/supplier-breach#source-4)

You may report to the authority in phases too, when not everything is known yet.[3](https://disruptivelab.dev/en-ie/news/supplier-breach#source-3) A report made later than 72 hours must give the reasons for the delay.[3](https://disruptivelab.dev/en-ie/news/supplier-breach#source-3)

## How do the first 72 hours look, step by step?

1.  **Hour 0, the supplier's notice.** Write down when it came, from whom and what it says. For personal data, this is usually the moment your 72 hours start.[4](https://disruptivelab.dev/en-ie/news/supplier-breach#source-4)
2.  **The first hours, the facts.** Ask which of your systems and data were on the affected servers, what was accessed and since when. A supplier whose incident touches several customers must report the details to each of them.[4](https://disruptivelab.dev/en-ie/news/supplier-breach#source-4)
3.  **Within 24 hours, if you are under NIS2.** If the incident significantly disrupts your services, causes you financial loss or considerable damage to others, send the early warning.[5](https://disruptivelab.dev/en-ie/news/supplier-breach#source-5) It says whether the incident is suspected to be malicious or could affect other countries.[5](https://disruptivelab.dev/en-ie/news/supplier-breach#source-5)
4.  **By 72 hours, the reports.** Report a personal data breach to the authority unless it is unlikely to put people at risk.[3](https://disruptivelab.dev/en-ie/news/supplier-breach#source-3) Under NIS2, send the incident notification with a first assessment of severity and impact.[5](https://disruptivelab.dev/en-ie/news/supplier-breach#source-5) Details still missing may follow in phases.[3](https://disruptivelab.dev/en-ie/news/supplier-breach#source-3)
5.  **Afterwards, the people and the records.** Tell the people concerned if the risk to them is high.[3](https://disruptivelab.dev/en-ie/news/supplier-breach#source-3) Record the facts, effects and remedies of every personal data breach, including those you did not report.[3](https://disruptivelab.dev/en-ie/news/supplier-breach#source-3)[4](https://disruptivelab.dev/en-ie/news/supplier-breach#source-4) Under NIS2, the final report follows within one month of the notification.[5](https://disruptivelab.dev/en-ie/news/supplier-breach#source-5)

These steps hold only if your own systems show who had access to what, and when. Without that record, neither the supplier's account nor your own assessment can be checked, and the 72 hours pass in guesswork.

## What does NIS2 add for companies under it?

NIS2 binds companies through each country's own law, which member states had to adopt by 17 October 2024.[6](https://disruptivelab.dev/en-ie/news/supplier-breach#source-6) Where it applies, supply chain security is one of the measures a company must take, including its relations with its direct suppliers and service providers.[5](https://disruptivelab.dev/en-ie/news/supplier-breach#source-5) When choosing those measures, the company must take into account each supplier's vulnerabilities and the quality of its products and security practices, including how it develops software.[5](https://disruptivelab.dev/en-ie/news/supplier-breach#source-5)

The reporting duty covers incidents with a significant impact on the services you provide.[5](https://disruptivelab.dev/en-ie/news/supplier-breach#source-5) The directive explains that its duties apply whether a company runs its systems itself or has outsourced their upkeep.[5](https://disruptivelab.dev/en-ie/news/supplier-breach#source-5) By our reading, an incident that starts at a supplier counts when it has that impact on your services. Where appropriate, you must also tell the recipients of your services, without undue delay, about a significant incident likely to affect them.[5](https://disruptivelab.dev/en-ie/news/supplier-breach#source-5) The directive also states that the mere act of notification does not make the company more liable.[5](https://disruptivelab.dev/en-ie/news/supplier-breach#source-5)

GDPR and NIS2 reports are separate duties. When a NIS2 authority finds that an infringement may involve a personal data breach, it must inform the data protection authority, and the same conduct is not fined under both.[5](https://disruptivelab.dev/en-ie/news/supplier-breach#source-5) Your own two reports, though, still go to different authorities, on different forms and with different content.[3](https://disruptivelab.dev/en-ie/news/supplier-breach#source-3)[5](https://disruptivelab.dev/en-ie/news/supplier-breach#source-5)

## What should the contract with the supplier say?

The GDPR already requires a written contract with every processor. It must oblige the supplier to help you meet your duties on security and on breach notification.[3](https://disruptivelab.dev/en-ie/news/supplier-breach#source-3) The EDPB adds that the contract should say how the supplier's duty to notify you is met, and may require early notification so that you can keep to your 72 hours.[4](https://disruptivelab.dev/en-ie/news/supplier-breach#source-4) A supplier may even file the report on your behalf if the contract authorises it, but the legal responsibility remains with you.[4](https://disruptivelab.dev/en-ie/news/supplier-breach#source-4)

Before you decide

-   The supplier tells you of a suspected breach within a stated number of hours, at any time of day, to a named contact.
-   The first notice says what is known, and further details follow in phases on an agreed schedule.
-   The supplier says which of your systems and data were affected, and keeps the records that show it.
-   The supplier tells you of incidents at its own subcontractors that touch your data or your systems.
-   If you are under NIS2, the supplier's notice reaches you in time for your own early warning within 24 hours.
-   Whether anyone may file a report on your behalf is stated, and you approve such a report before it is sent.
-   The supplier cooperates with the authority and with your own investigation.
-   Who pays for the investigation and for informing the people affected is settled in advance.

These clauses cost a supplier little to agree before signing. On the day of an incident, they decide whether you can meet your own deadlines.

## What this means for a company in Europe

On 21 October 2026 the member states agreed in the Council their position on the Digital Omnibus, a proposal to simplify several European digital laws.[7](https://disruptivelab.dev/en-ie/news/supplier-breach#source-7) It would require a personal data breach to be reported to the authority only when it is likely to put people at high risk, within 96 hours instead of 72, with the support of a national entry point set up under NIS2.[3](https://disruptivelab.dev/en-ie/news/supplier-breach#source-3)[7](https://disruptivelab.dev/en-ie/news/supplier-breach#source-7) The European Parliament's procedure file still showed the proposal awaiting a committee decision on 17 November 2026.[8](https://disruptivelab.dev/en-ie/news/supplier-breach#source-8) Until a change is adopted and applies, the 72 hours of today's GDPR stand.[3](https://disruptivelab.dev/en-ie/news/supplier-breach#source-3)

## In Ireland

NIS2 is not yet Irish law, so its reporting duties do not yet apply, and the National Cyber Security Centre (NCSC), home of CSIRT-IE, has not yet opened its NIS2 reporting portal.[9](https://disruptivelab.dev/en-ie/news/supplier-breach#source-9) Until a national act passes, S.I. No. 360 of 2018 still applies to the operators designated under it, with an incident notice within 72 hours.[10](https://disruptivelab.dev/en-ie/news/supplier-breach#source-10) A personal data breach goes to the Data Protection Commission (DPC) through its online Breach Notification Form, within 72 hours of becoming aware of it.[11](https://disruptivelab.dev/en-ie/news/supplier-breach#source-11) Telecoms and internet providers use a separate form.[11](https://disruptivelab.dev/en-ie/news/supplier-breach#source-11)

## Next step

If it would help, we are glad to go through what your contracts with IT suppliers say about a breach, in a short meeting. The custom business systems and applications we build keep a record of who did what and when, which is what the first hours of an incident rely on. What you do with the result is entirely your decision.

[Custom business systems and applications](https://disruptivelab.dev/en-ie/custom-business-systems)

## Sources

1.  1. [CGI, CGI Ruotsi tiedottaa sisäisiin testipalvelimiin liittyvästä tietoturvapoikkeamasta (CGI Sweden informs of a security incident concerning internal test servers), 13 March 2026](https://www.cgi.com/fi/fi/uutinen/cgi-ruotsi-tiedottaa-sisaisiin-testipalvelimiin-liittyvasta-tietoturvapoikkeamasta). Read on 17 November 2026
2.  2. [CERT-SE, CERT-SE:s veckobrev v.11, 13 March 2026](https://www.cert.se/2026/03/cert-se-veckobrev-v11.html). Read on 17 November 2026
3.  3. [Regulation (EU) 2016/679 (GDPR), Articles 4, 28, 33 and 34, Official Journal of the EU](https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng). Read on 17 November 2026
4.  4. [EDPB, Guidelines 9/2022 on personal data breach notification under GDPR, version 2.0, 28 March 2023](https://www.edpb.europa.eu/our-work-tools/our-documents/guidelines/guidelines-92022-personal-data-breach-notification-under_en). Read on 17 November 2026
5.  5. [Directive (EU) 2022/2555 (NIS2), recital 83 and Articles 21, 23 and 35, Official Journal of the EU](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32022L2555). Read on 17 November 2026
6.  6. [European Commission, NIS2 Directive, securing network and information systems](https://digital-strategy.ec.europa.eu/en/policies/nis2-directive). Read on 17 November 2026
7.  7. [Council of the EU, Digital Omnibus, mandate for negotiations with the European Parliament, document 14756/26, 22 October 2026](https://data.consilium.europa.eu/doc/document/ST-14756-2026-INIT/en/pdf). Read on 17 November 2026
8.  8. [European Parliament, Legislative Observatory, procedure file 2025/0360(COD), Digital Omnibus](https://oeil.secure.europarl.europa.eu/oeil/en/procedure-file?reference=2025/0360(COD)). Read on 17 November 2026
9.  9. [National Cyber Security Centre, NIS2](https://www.ncsc.gov.ie/nis2/). Read on 17 November 2026
10.  10. [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](https://www.irishstatutebook.ie/eli/2018/si/360/made/en/print). Read on 17 November 2026
11.  11. [Data Protection Commission, Breach Notification](https://www.dataprotection.ie/en/organisations/know-your-obligations/breach-notification). Read on 17 November 2026

## Change log

1.  17 November 2026 Published.

## Related articles

Guide · European rules

### [The AI Act for Irish firms that only use AI](https://disruptivelab.dev/en-ie/news/ai-act-for-deployers)

For companies in Ireland. What the AI Act asks of deployers now, what comes in December 2027, and the role of the AI Office of Ireland.

17 November 2026

Guide · European rules

### [E-invoicing in Ireland from November 2028](https://disruptivelab.dev/en-ie/news/mandatory-e-invoicing)

For companies in Ireland. Revenue's plan for e-invoicing from November 2028, what counts as one and what your invoicing system must handle.

17 November 2026

## Company details

- **Company name:** Disruptive Lab s.r.o.
- **Registered office:** Vavrečkova 5262, 760 01 Zlín
- **Company ID (IČO):** 08240647
- **VAT ID (DIČ):** CZ08240647
- **E-mail:** office@disruptivelab.dev
- **Phone:** +420 777 702 032
