Has something happened to you? We tell you what to do, in order, and the deadlines that are running
Choose what has happened and the time you found out. We give you the steps, the legal deadlines that apply to you with their official source and an incident sheet to download. Everything is worked out in your browser: nothing reaches us.
Have you paid or given your passwords as an individual? Better to use the Emergency button. Is there personal data involved? Afterwards the breach notice will help you.
Your deadlines
What to do, in order
Tick each step when you do it: the sheet notes the time. Contain without deleting anything: what you delete cannot be investigated.
Ransomware: encrypted files and a ransom note
- Write down when you saw it. The deadlines run from that moment. If you don't know the exact time, put your best estimate.
- Disconnect them from the network (cable and wifi) and unplug the backup drives. Don't format or reinstall them yet: the evidence is there.
- Take photos of the ransom note and of the screen, and keep a sample encrypted file. Note down which computers are affected and at what time.
- From a clean computer that is not on your network, change the administrator, email and banking passwords, and sign out open sessions.
- Check that you have a copy from before the attack and that it is not encrypted. Do not restore until the computer is clean.
- It does not guarantee that you will get your files back, and it funds the next attack.
- Call INCIBE's 017 and report it to the police. If personal data is involved, watch the AEPD clock.
GDPR in this case: If there is personal data on the encrypted computers, the breach is one of availability and may be one of confidentiality too.
Email account taken over
- Write down when you saw it and, if you know, when it started.
- From a computer or a phone that you don't use with that account, change the password, turn on two-step verification and sign out all open sessions.
- Check whether there are rules that forward or delete messages, forwarding to other addresses, and connected applications that you do not recognise. Take a screenshot of each before removing it.
- If you used the same password elsewhere, change it there too, starting with banking.
- Tell them to ignore messages from that account, especially invoices or changes of bank account.
- If any payment was requested or made through that account, call your bank now.
- Keep the messages sent from your account and the screenshots. Call 017 if you are unsure, and report it.
GDPR in this case: If that account holds personal data of customers, staff or suppliers, someone may have seen it.
I have paid a fake IBAN
- Write down when you made the transfer: the sooner you notify, the more chance there is of holding the money.
- Ask them to try to hold the money and to request a refund from the receiving bank. Do not wait to write to them.
- The destination IBAN, the amount, the date and time, the receipt, and the email or message that asked for the change.
- Do not reply or pay anything more, whether “costs” or “claims”.
- Call them on a number you already had, not the one in the email, and tell them what has happened.
- If the email about the change looked genuinely like your supplier's, an email account may have been taken over, yours or theirs. If yours, also follow the case “Email account taken over”.
- Keep the evidence and report it: your bank will ask for the report in order to make a claim.
GDPR in this case: Only if, in addition, someone saw personal data (for example, because an email account had been taken over).
Leaked data
- Write down when you found out. The deadlines run from that moment, not from when it happened.
- Remove the public link, close the shared access or disconnect the computer it came from. Ask for an email sent by mistake to be deleted.
- Do not delete logs or messages. Save screenshots of where the data is published and of who has it.
- Change the passwords of the accounts that gave access and sign out their sessions.
- What the data is (name, email, DNI, IBAN, health...), how many people, and whether it was encrypted.
- Prepare the AEPD draft, the notice to the people affected and your breach register in the breach notice.
- In plain language and directly, with what they can do to protect themselves.
- If someone has stolen them or asks you for money in return for not publishing them, report it and call 017.
GDPR in this case: It is the typical case: if there is personal data and a risk to people is likely, you have to notify.
Website down or modified
- Write down when you saw it and who saw it first.
- Capture what is shown, the address and the time. If it has been altered, don't fix it yet.
- If it shows something malicious or asks for data, put it in maintenance mode or disconnect it.
- Copy the files and the server logs as they are: they will help to find out how they got in.
- Change the hosting password, the content management system password and the database password, and sign out all sessions.
- Ask them for the access logs for those days and to help you see how they got in.
- Only from a backup made before the incident and after changing the passwords; update the manager and the plugins.
- Check what the website was holding. If personal data is affected, watch the AEPD clock.
- If it was an attack, keep the screenshots and logs and report it; call 017 if in doubt.
GDPR in this case: If the website holds customer data (forms, orders, accounts) and someone may have accessed it.
Lost or stolen laptop or phone
- Write down when you realised and when you last saw it.
- From another device, use the system's own lock and location. Wipe its contents only if there is no hope of recovering it or it held unencrypted data.
- Change the passwords of the accounts it had open and sign out their sessions, starting with email and banking.
- Call your mobile operator to block the line and ask for a new SIM card.
- What data there was, whose, and whether the disk was encrypted. Note it down: you will need it if you have to notify.
- If the computer had the bank app or saved cards, call your bank to block them.
- It serves as proof for insurance and for your incident log.
GDPR in this case: If the computer held unencrypted personal data. If the disk was encrypted, the risk drops a lot: note it down.
Your incident sheet
The sheet stays in your browser. Download it before closing the page.
The clocks, with their official source
All of them count from when you became aware of the incident. For each one, the link to the source that sets it.
- AEPD: notify the breach (72 hours). If the breach is likely to pose a risk to individuals. The clock runs from when you become aware of it, not from when it happened. If you don't know everything, notify what you know and complete the notification within 30 days. If the risk is high, also tell the people affected. If you conclude that there is no need to notify, note it down with the reason. Source: AEPD: personal data breaches, GDPR on EUR-Lex (recital 85), AEPD: breaches guide (2021).
- NIS2: early warning (24 hours). For a significant incident, to your reference CSIRT or the authority for your sector. Source: INCIBE-CERT: NIS2 frequently asked questions, NIS2 Directive on EUR-Lex (art. 23.4).
- NIS2: incident notification (72 hours). With a first assessment of the severity and the impact. Source: INCIBE-CERT: NIS2 frequently asked questions, NIS2 Directive on EUR-Lex (art. 23.4).
- NIS2: final report (one month). One month at the latest after submitting the notification. Here it is counted from the 72-hour limit: if you notify earlier, the deadline moves earlier. Source: INCIBE-CERT: NIS2 frequently asked questions, NIS2 Directive on EUR-Lex (art. 23.4).
- DORA: initial notification (4 hours from when you classify it; 24 from when you found out). For a serious ICT-related incident, to your authority (Banco de España, CNMV or DGSFP). Whichever limit comes first applies: 4 hours from when you classify it as serious, or 24 from when you found out. Enter the time of classification to see the first. Source: Delegated Regulation (EU) 2025/301 (Art. 5), in the BOE, INCIBE: DORA is now mandatory.
- DORA: intermediate report (72 hours). 72 hours after the initial notification, even if nothing has changed. Here it is counted from the limit of the initial one: if you notify earlier, it moves earlier. Source: Delegated Regulation (EU) 2025/301 (Art. 5), in the BOE.
- DORA: final report (one month). One month at the latest after the last intermediate report. Here it is counted from the limit of the intermediate one. The rules for weekends and public holidays are in Article 5 of the regulation: don't count on them. Source: Delegated Regulation (EU) 2025/301 (Art. 5), in the BOE.
Reporting to the police and notifying your bank have no legal deadline that counts here, but the sooner the better: your bank will ask for the report and every hour counts to hold back a payment.
Status of NIS2 in Spain
- As of 31 October 2026, NIS2 is not yet a Spanish law in force: we have not found any law in the BOE (Spain's Official State Gazette) that transposed it.
- The Council of Ministers approved the draft bill on the Coordination and Governance of Cybersecurity Act on 14 January 2025, and on 17 March 2026 La Moncloa was still saying that the directive would be transposed with that law.
- On 8 July 2026 the European Commission referred Spain to the EU Court of Justice because it had not yet notified full transposition.
- While there is no law, which authority or CSIRT you must notify, and in how much detail, is not fixed in Spain: INCIBE-CERT says it will be known with the transposition. The deadlines of 24 hours, 72 hours and one month are those of the directive: use them as a reference if your client or your sector already asks for them.
- If you were already an operator of essential services or a digital service provider under the previous rules (Royal Decree-Law 12/2018 and Royal Decree 43/2021), keep complying with what you already had.
- Check it in the BOE before trusting this page: it may have changed.
For your security file, the NIS2 file. If you make products with software, see the CRA notice.
Who to call
- INCIBE: 017 helpline. Free and confidential, from 8:00 to 23:00, every day of the year. Also by WhatsApp (900 116 117) and Telegram (@INCIBE017). For citizens, businesses and minors. incibe.es/linea-de-ayuda-en-ciberseguridad
- INCIBE-CERT. Notify the incident using its form; incident response operates 24 hours a day, every day. It does not replace the police report. incibe.es/incibe-cert/incidentes/notificaciones
- AEPD (Spanish Data Protection Agency). Breaches are notified using the form on its electronic office. Telephone 900 293 183, Monday to Friday from 9:00 to 17:30 (in August, from 9:00 to 15:00). sedeaepd.gob.es
- Guardia Civil. Electronic report, with an electronic signature and no later ratification, for scams and fraudulent charges by computer means, damage and thefts, among others. Citizen service office: 900 101 062. web.guardiacivil.es
- Policía Nacional. With the Policía Nacional you start online and sign at the police station within 72 hours. policia.es
- If you are a financial institution (DORA). You notify your authority: the Banco de España (credit, payment and electronic money institutions), the CNMV (investment services, management companies and markets) or the DGSFP (insurance and pensions). incibe.es: DORA is now mandatory
If there is immediate danger to people, do not use this page.
Frequently asked questions
From when do the deadlines count?
From when you become aware of the incident, not from when it happened. If you don't know the exact time, put your best estimate and say so on the sheet. Don't wait until you know everything: you can notify in phases, with what you know and completing it afterwards.
Does NIS2 already apply to me in Spain?
The Spanish law that transposes it is not recorded as in force (see the status and sources above). That is why the NIS2 deadlines appear as a reference from the directive, and only if you tick that your organisation is essential or important.
What is DORA and does it apply to me?
It is the European regulation on digital resilience in the financial sector. It only applies to you if you are a financial entity (bank, insurer, payment or investment firm...). If you are, your deadlines are those of your authority: here are those of the European regulation, which you can check against it.
Does notifying INCIBE-CERT replace reporting to the police?
No. Notifying the incident to INCIBE-CERT and reporting to the Policía or the Guardia Civil are different things. If money or data has been stolen from you, report it: your bank or your insurer will ask for the report.
Do I have to notify the AEPD for every incident?
No: only if there is personal data and there is likely to be a risk to people. If you decide not to, note down why. The breach notice prepares the draft of the notification, the notice to the people affected and the record for you: /aviso-de-brecha
Do I pay the ransom?
We do not recommend it: it does not guarantee that you will get your files back, and it funds the next attack. Before deciding anything, call 017 and report it to the police.
Can I switch off the affected computer?
First disconnect it from the network, and do not format it or reinstall it: the evidence is there. If in doubt, call 017 or whoever looks after your IT before switching it off.
Do you keep it?
No. Everything is calculated in your browser and nothing reaches us: not the time, not what you tick, not the sheet. Download it before closing the page: we will not be able to recover it.
Does this replace my lawyer, my data protection officer or my IT person?
No. It puts the first steps in order and reminds you of the deadlines; what to notify and to whom is your decision. If you have a data protection officer or an adviser, involve them from the first minute.
Official sources
- AEPD: personal data breaches
- AEPD: guide to managing and notifying breaches (2021)
- AEPD: where to find us
- GDPR on EUR-Lex
- INCIBE-CERT: NIS2 frequently asked questions
- NIS2 Directive (EU) 2022/2555 on EUR-Lex
- European Commission: referral of Spain to the Court of Justice over NIS2 (8 Jul 2026)
- European Commission: NIS2 in Spain
- La Moncloa: Council of Ministers of 17 Mar 2026
- Departamento de Seguridad Nacional: draft bill on the Coordination and Governance of Cybersecurity Act
- Delegated Regulation (EU) 2025/301 (DORA), in the BOE
- INCIBE: DORA is now mandatory
- INCIBE-CERT: managing cyber incidents in the private sector
- INCIBE-CERT: incident response
- INCIBE: 017 helpline
- INCIBE: how to report
- Guardia Civil: electronic report
- Policía Nacional: reports
Consulted on 31 October 2026. The deadlines and phone numbers are those on those pages on that date; check them when you notify.