European reference · updated on 2026-08-17

Your credentials have leaked.
The real question lies elsewhere.

Knowing that an address has appeared in a leak costs nothing and changes nothing: it is true for almost everyone. The question that engages your responsibility is twofold: does this leak still open a door into your organisation, and whom must you notify, within what deadline.

72 hto notify the competent authority GDPR, Article 33
30countries, each authority verified individually official EDPB list
15 000 000 000records in the public reference corpus figure published by Have I Been Pwned
0leaked credentials kept by usno one can steal from us what we have never seen

What « having leaked » means, and what it does not mean

A credential leak is not an isolated event on your side: it is a worldwide flow. To give an order of magnitude, the public reference in the field indexed 1 957 476 021 unique addresses in a single operation in November 2025 (figure published by Have I Been Pwned).

Practical conclusion: the presence of your domain name in a leak is likely, and it is not in itself actionable information. What matters is what comes next.

The three questions that do change something

  • Does the account still exist, and is it active?
  • Was the password changed after the date of the leak, or before?
  • Is that account covered by strong authentication, and is it a privileged account?

None of these three answers is found in a breach database. They are read inside your directory or your tenant, with your agreement.

If the leak is confirmed: the procedure, in order

  1. Establish and date it. Record the exact moment you became aware of the facts: that is what starts the 72 hour deadline, not the date of the leak itself.
  2. Contain. Reset the affected accesses, revoke current sessions and tokens. Changing a password does not close a session that is already open.
  3. Measure the scope. Which people, which categories of data, what volume. That measurement is what the authority will ask you for, not your impression.
  4. Notify the competent authority if the breach is likely to result in a risk to individuals. The table below gives the authority for your country.
  5. Inform the individuals concerned where the risk to them is high.
  6. Document. Every breach must be recorded, including one you chose not to notify, together with the reason for that choice.

This procedure follows the GDPR, Articles 33 and 34. Official text. It does not replace legal advice: we are auditors, not lawyers. Official sources: Regulation (EU) 2016/679, Articles 33 and 34 (EUR-Lex); EDPB Guidelines 9/2022; CNIL: personal data breaches; CNIL: notifying a breach; Directive (EU) 2022/2555, Article 23 (EUR-Lex).

Whom to notify, country by country

The competent data protection authority for 30 countries of the European Economic Area. Twenty-seven lines were verified individually against the official list of members of the European Data Protection Board, and carry the link to that source; for Liechtenstein, the source is the authority's own website; for Iceland and Luxembourg, the verification is not published: check the authority against the Board's list before notifying.

CountryData protection authorityVerification
AustriaOsterreichische Datenschutzbehorde (DSB)source
BelgiumAutorite de la protection des donnees - Gegevensbeschermingsautoriteit (APD-GBA)source
BulgariaCommission for Personal Data Protection (CPDP)source
CyprusOffice of the Commissioner for Personal Data Protection (Cyprus Data Protection Authority)source
CzechiaUrad pro ochranu osobnich udaju (UOOU) - Office for Personal Data Protectionsource
GermanyBfDI - Die Bundesbeauftragte für den Datenschutz und die Informationsfreiheitsource
DenmarkDatatilsynetsource
EstoniaEstonian Data Protection Inspectorate (Andmekaitse Inspektsioon)source
SpainAgencia Espanola de Proteccion de Datos (AEPD)source
FinlandOffice of the Data Protection Ombudsman (Tietosuojavaltuutetun toimisto)source
FranceCNIL (Commission Nationale de l'Informatique et des Libertes)source
GreeceHellenic Data Protection Authority (HDPA) - Arkhi Prostasias Dedomenon Prosopikou Kharaktirasource
CroatiaAgencija za zastitu osobnih podataka (AZOP) - Croatian Personal Data Protection Agencysource
HungaryNemzeti Adatvedelmi es Informacioszabadsag Hatosag (NAIH) - Hungarian National Authority for Data Protection and Freedom of Informationsource
IrelandData Protection Commission (DPC)source
IcelandPersonuvernd (Icelandic Data Protection Authority)not published
ItalyGarante per la protezione dei dati personalisource
LiechtensteinDatenschutzstelle Fürstentum Liechtensteinsource
LithuaniaState Data Protection Inspectorate (Valstybine duomenu apsaugos inspekcija - VDAI)source
LuxembourgCommission Nationale pour la Protection des Données (CNPD)not published
LatviaData State Inspectorate (Datu valsts inspekcija)source
MaltaOffice of the Information and Data Protection Commissioner (IDPC)source
NetherlandsAutoriteit Persoonsgegevens (AP)source
NorwayDatatilsynetsource
PolandUrząd Ochrony Danych Osobowych (UODO)source
PortugalComissão Nacional de Proteção de Dados (CNPD)source
RomaniaANSPDCP - Autoritatea Nationala de Supraveghere a Prelucrarii Datelor cu Caracter Personal (National Supervisory Authority for Personal Data Processing)source
SwedenIntegritetsskyddsmyndigheten (IMY) - Swedish Authority for Privacy Protectionsource
SloveniaInformation Commissioner of the Republic of Slovenia (Informacijski pooblascenec)source
SlovakiaUrad na ochranu osobnych udajov Slovenskej republikysource

A missing line means we could not verify it, not that it does not exist. We prefer a shorter table to a less accurate one.

What we can do, and what we do not do

We know how to look from outside

8 public sources describe what an attacker sees of you before entering: certificate logs, DNS and mail records, exposed services, look-alike domain names, code publications, indexed documents.

  • Without installing anything on your side
  • Without holding any stolen data

And above all, look from inside

That is where the three answers that matter are found. We audit Microsoft 365 and Active Directory from your own workstation, read-only, and we cross-check what the leak announces against the real state of your accounts.

  • Report in the language of each reader
  • Roadmap ranked by effort and by impact

Where we stand, said plainly

The engine that queries these 8 sources is written and working, but it has not yet run with a client. We are therefore not selling a self-service diagnosis here: we run it ourselves, with you, and you are told that you would be among the first. We prefer to say so rather than let you find out.

The Microsoft 365 audit and the Active Directory audit, by contrast, already run at real client sites.

Free analysis of your domain: syaga.eu/scan. The free tool “Is my Microsoft 365 under attack?” is coming.

  Describe your situation   See the other doors