In the first hours of a computer security incident, the company makes decisions it will not be able to undo later: what gets shut down, what gets deleted, who is notified and what is said. Many of them have legal consequences, and a written, rehearsed protocol keeps them from being made under pressure and without information.
What the law requires
Toward data subjects. Under Article 19 of the Federal Law on the Protection of Personal Data Held by Private Parties (Ley Federal de Protección de Datos Personales en Posesión de los Particulares), if the breach significantly affects their economic or moral rights, the controller must inform them immediately. The law sets no deadline in hours and no duty to notify the authority.
Regarding the company’s own security. The duty to maintain security measures proportionate to the risk is ongoing (Article 18). After an incident, the root cause analysis and the corrective actions are the best evidence that the company meets that duty. The 2011 Regulations, whose force is debatable, require this expressly (Article 66 of the Regulations), and even without that text it is the conduct the authority expects.
Regarding the crime. The Federal Criminal Code (Código Penal Federal) punishes anyone who, without authorization, modifies, destroys or causes the loss of information contained in systems protected by a security mechanism with six months to two years in prison and one hundred to three hundred day-fines (días multa), and anyone who, without authorization, learns of or copies that information with three months to one year in prison and fifty to one hundred fifty day-fines (Article 211 bis 1). A day-fine equals the convicted person’s net daily income (Article 29). Penalties are higher when the systems belong to financial system institutions (Articles 211 bis 4 and 211 bis 5). The law does not require a private company that is the victim to file a criminal complaint in every case, but if it decides to do so it needs preserved evidence.
Regarding personnel. Under the Federal Labor Law (Ley Federal del Trabajo), an employee’s disclosure of manufacturing secrets or of confidential matters, to the company’s detriment, is cause for terminating the employment relationship without liability for the employer (Article 47, section IX). If the incident was caused by an insider, the company must act within the labor law deadlines and with the formalities of the termination notice.
Regarding the verifying authority. The Ministry of Anti-Corruption and Good Governance (Secretaría Anticorrupción y Buen Gobierno) may open a verification proceeding on its own initiative when it presumes, on reasoned and justified grounds, a violation of the law, and in that proceeding it has access to the information and documentation it considers necessary (Articles 54 and 55). A publicly known incident is a likely reason for verification, and obstructing verification acts is in itself an infraction (Article 58, section XIV), regardless of what is concluded about the incident.
Regarding customers and vendors. Contracts often impose notice, cooperation and audit deadlines after an incident. Breaching them creates contractual liability separate from the administrative penalty.
What to do and by when
- Form a response committee with people from technology, management, legal and communications, with alternates and contact details kept outside the company’s systems.
- Define the criteria for classifying the severity of an incident and for deciding whether the impact on data subjects is significant.
- Set evidence preservation rules to apply before restoring systems: forensic copies, activity logs and a decision log recording the time and the person responsible.
- Prepare notice templates for data subjects, for customers with contractual notice obligations and for insurers, if you have a policy.
- Define who decides to file a complaint with the Public Prosecutor’s Office (Ministerio Público) and with what evidence.
- Plan the labor procedure in case the incident involves your own personnel.
- Rehearse the protocol at least once a year with a simulated case and document the improvements.
- After each incident, prepare a root cause analysis and a corrective action plan approved by management.
- Designate who will deal with the authority if it opens a verification proceeding and prepare the index of documents that would be delivered to it.
Recommendations to mitigate risk
If the incident is attributable to the company, the personal data fine ranges from 200 to 320,000 times the Unit of Measurement and Update (UMA), equivalent to MXN 23,462 to MXN 37,539,200, under Article 58, section XI, and Article 59, section III. An improvised response increases that risk. If systems are restored without preserving evidence, the company loses the ability to show what happened, both before the authority and in a criminal complaint. Late or incomplete notice to data subjects opens the door to claims for damages that could have been avoided (Article 53), and a hasty public statement may contradict what is later established and compromise the defense. If a verification proceeding follows, a disorganized response or a failure to deliver information may constitute the obstruction described in Article 58, section XIV, punishable within the same range of 200 to 320,000 UMA (MXN 23,462 to MXN 37,539,200), under Article 59, section III.
Self-assessment
Answer yes or no for your own company.
- Do you have an incident response committee with members and alternates designated in writing?
- Have you defined the criteria for deciding whether a breach is significant?
- Does your team know what evidence to preserve before restoring systems?
- Do you have notice templates for data subjects and customers?
- Do you know which contracts impose notice deadlines on you after an incident?
- Have you defined who decides to file a criminal complaint?
- Have you rehearsed the protocol in the past year?
How we approach it at LEXURE
We draft the legal incident response protocol and integrate it with your team’s technical plan: committee, decision criteria, evidence rules, notice templates and a matrix of contractual obligations. We run a simulated exercise with management and, if a real incident occurs, we support the legal decisions from the first hour.
If your company has a technical plan but no legal protocol, schedule a diagnostic meeting with us.
Legal basis
- Federal Law on the Protection of Personal Data Held by Private Parties, Articles 18, 19, 53, 54, 55, 58, sections XI and XIV, and 59, section III. Current text (opens in a new tab)
- Regulations of the Federal Law on the Protection of Personal Data Held by Private Parties (Reglamento de la Ley Federal de Protección de Datos Personales en Posesión de los Particulares), Article 66. Published text (opens in a new tab)
- Federal Criminal Code, Articles 29, 211 bis 1, 211 bis 4 and 211 bis 5. Current text (opens in a new tab)
- Federal Labor Law, Article 47, section IX. Current text (opens in a new tab)
- 2026 value of the Unit of Measurement and Update, National Institute of Statistics and Geography (INEGI). Official publication (opens in a new tab)
This note is for information only and describes the law in force on the verification date. It is not legal advice on a specific matter. It is a translation of the Spanish original: Mexican law is published in Spanish, and the official Spanish texts prevail.