Join our Newsletter — 33% off our NHI Course
Home› Guides› Latin America Cybersecurity Laws Guide: National Rules, Regulators…
Guide Regulations & Frameworks

Latin America Cybersecurity Laws Guide: National Rules, Regulators and Incident Clocks Compared

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 14 November 2026 13 min read
On this page

A security team operating across Latin America faces a patchwork in which one country has a full cyber framework law with a three hour alert, another a 24 hour statutory clock, another a decree that binds only public bodies, and another no federal cybersecurity law at all. This guide maps the national, cross-sector cybersecurity rules of eight countries, Argentina, Brazil, Chile, Colombia, Costa Rica, Mexico, Peru and Uruguay, side by side, with who is covered, which authority receives incident reports, the clock and the current status. It sits beside the Latin America Financial Cyber Rules guide, which covers banking supervisors, and the Chile Cybersecurity Framework Law guide, which covers Chile in depth. It is written for regional CISOs, compliance leads and incident response managers who need one view of where duties already bite and where they are still forming. Countries are listed alphabetically, and order is not a ranking.

Status: summarised from official texts and government publications listed under Standards and references, checked 14 November 2026. English renderings of Spanish and Portuguese terms are our own. Several regimes here are policies, drafts or bills that can change quickly, so confirm every obligation and deadline against the official text before relying on it.

Key takeaways

  • Only two countries set a statutory hour clock for critical sectors. Chile's Ley 21.663 requires an early alert within 3 hours, and Uruguay's Law 20.212 requires covered entities to report incidents to AGESIC within 24 hours of becoming aware of them.
  • Peru has a duty but not yet a final clock. Emergency Decree 007-2020 obliges public bodies and listed digital service providers to notify every digital security incident to the Centro Nacional de Seguridad Digital; a draft regulation published in 2025 proposed 48 hours for critical incidents.
  • Brazil and Colombia rely on governance decrees. Brazil's Decree 11.856/2023 created a national policy and committee without a private sector reporting duty, and Colombia's Decree 338 of 2022 binds public authorities, with private critical operators covered mainly by sector rules.
  • Mexico and Costa Rica have no general cyber law in force. Mexico's 2025 to 2030 national plan promises a Ley General de Ciberseguridad, and Costa Rica's 2022 cybersecurity bill (file 23.292) is archived.
  • Privacy clocks still apply everywhere. Where no cyber law applies, breach notification under data protection law, such as Brazil's three working day rule under ANPD Resolution 15/2024, is often the fastest binding deadline.

Scope: who and what is covered

The table compares the main cross-sector instrument in each country. Sector supervisors (banking, telecoms, energy) add their own rules on top: see the Latin America Financial Cyber Rules for banks and payment firms.

CountryMain instrumentTypeWho is coveredLead body
ArgentinaSecond National Cybersecurity Strategy, approved by Resolution 44/2023 of the Chief of Cabinet's OfficeStrategy (policy)Sets objectives for the federal state, critical infrastructure and industry; no binding private sector duties identifiedJefatura de Gabinete de Ministros, with a Unidad de Gestión de Cooperación en Ciberseguridad
BrazilDecree 11.856 of 26 December 2023 (Política Nacional de Cibersegurança, PNCiber)Decree (policy and governance)Guides national cybersecurity activity; creates the Comitê Nacional de Cibersegurança (CNCiber)Gabinete de Segurança Institucional (GSI), which chairs CNCiber and runs its secretariat
ChileLey 21.663, Ley Marco de CiberseguridadStatuteEssential service providers, with heavier duties for designated operadores de importancia vital (OIV)Agencia Nacional de Ciberseguridad (ANCI) and CSIRT Nacional
ColombiaDecree 338 of 8 March 2022, adding Title 21 to Decree 1078 of 2015Decree (governance)Public authorities and private persons performing public functions; private critical infrastructure and essential service operators may apply itCoordinación Nacional de Seguridad Digital; MinTIC runs ColCERT and CSIRT Gobierno
Costa RicaLey de Ciberseguridad bill, file 23.292 (presented 22 August 2022)Bill, archivedWould have covered critical information infrastructure and created an agency within MICITTMICITT (as proposed)
MexicoPlan Nacional de Ciberseguridad 2025 to 2030 (presented 4 December 2025)National planFederal public administration first; a general law for wider scope is announcedAgencia de Transformación Digital y Telecomunicaciones (ATDT), Dirección General de Ciberseguridad
PeruEmergency Decree 007-2020, Marco de Confianza Digital (8 January 2020)Decree with force of lawPublic entities; digital service providers in finance, basic services (electricity, water, gas), health and passenger transport; internet service providers; critical activity providers; education providersCentro Nacional de Seguridad Digital, under the Presidency of the Council of Ministers (Secretaría de Gobierno Digital)
UruguayLaw 20.212 (2023), Articles 78 to 84StatutePublic entities and private entities linked to critical services or sectorsAGESIC, with CERTuy as national response centre

Chile in one paragraph: Chile's framework law created ANCI, applies duties to every essential service provider and imposes management system, continuity and delegate duties on OIV. Its reporting duty and sanctions have applied since 1 March 2025, with an early alert to CSIRT Nacional within 3 hours, an update within 72 hours (24 hours for an affected OIV) and a final report within 15 days. Fines reach 40,000 UTM for the most serious OIV infractions. Detail, designation procedure and Article 8 duties are in the Chile Cybersecurity Framework Law guide; this page does not repeat them.

Key obligations

Read the obligations by type rather than by country: the same four questions apply everywhere. Who must report, to whom, by when, and what security programme must exist before an incident.

CountryIncident report toClockSecurity programme duties
ArgentinaNo cross-sector statutory duty identified; sector rules apply (for example BCRA for financial entities)None in the strategyStrategy objectives include developing the regulatory framework and protecting national critical infrastructure
BrazilNo private sector duty in Decree 11.856; personal data incidents go to the ANPDANPD: three working days for incidents that may cause relevant risk or damage (Resolution CD/ANPD 15/2024, Arts. 6 and 9)Decree objectives include regulation, supervision and control mechanisms and information exchange with the private sector (Art. 3)
ChileCSIRT Nacional3 hours, 72 hours, 15 daysApply ANCI protocols; OIV also run an ISMS, continuity and cybersecurity plans and appoint a delegate
ColombiaPublic authorities report to the competent authorities; ColCERT runs the Plataforma Nacional de Notificación y Seguimiento de Incidentes (Art. 2.2.21.1.5.9)No deadline in the decreeIdentified critical operators register with ColCERT, keep a digital security plan and run periodic risk assessments (Arts. 2.2.21.1.4.2 and 2.2.21.1.4.3)
Costa RicaNo statutory duty in forceNoneNone from the archived bill
MexicoNo statutory duty in force; the plan creates a CSIRT for the federal public administrationNoneFederal cybersecurity framework, early warning and critical infrastructure inventory planned in stage 1
PeruCentro Nacional de Seguridad Digital, feeding the Registro Nacional de Incidentes de Seguridad Digital (Arts. 8.1 and 9.1 a)"Every" incident; the 2025 draft regulation proposes 48 hours from awareness for critical incidents (draft Art. 32.1)Report personal data incidents to the data protection authority as well (Art. 9.1 e); the draft regulation requires an Oficial de Seguridad y Confianza Digital
UruguayAGESIC, which keeps the Registro Nacional de Incidentes de Ciberseguridad24 hours from awareness (Art. 80); Art. 78 also requires complete and immediate reporting under CERTuy criteriaAdopt AGESIC measures and its cybersecurity framework by maturity level, appoint an information security officer and notify AGESIC (Art. 78)
  • Supplier duties flow down: Peru's 2025 draft regulation says third-party providers must report incidents to the digital service provider they serve (draft Art. 34.4). Plan the same clause in contracts across the region, because your own clock starts when you become aware, not when the supplier tells you. See the Third-Party Incident Notification Clauses Guide.
  • Named officers: Uruguay requires an information security officer notified to AGESIC; Chile requires an OIV cybersecurity delegate; Peru's draft requires an OSCD registered on the notification platform before an incident. Register the person and a deputy in advance.
  • Dual reporting: Peru's decree and Brazil's ANPD rule both mean a single incident involving personal data can trigger a cyber report and a privacy report with different recipients and clocks. See the Brazil LGPD Guide and the Peru, Ecuador and Uruguay Data Protection Laws Guide.

Timeline and current status

DateEventStatus as of 14 November 2026
8 January 2020Peru: Emergency Decree 007-2020 approves the Marco de Confianza DigitalIn force; implementing regulation published as a draft in 2025
8 March 2022Colombia: Decree 338 sets the digital security governance modelIn force
22 August 2022Costa Rica: cybersecurity bill 23.292 presentedArchived
2 January 2023Argentina: Resolution 1/2023 opens consultation on a second strategySuperseded by approval
1 September 2023Argentina: Resolution 44/2023 published, approving the second strategyPolicy in force
2023Uruguay: Law 20.212 enacted with Articles 78 to 84 on cybersecurityIn force
26 December 2023Brazil: Decree 11.856 creates PNCiber and CNCiberIn force; strategy and plan are named instruments (Art. 4)
24 April 2024Brazil: ANPD Resolution 15/2024 on security incident communicationIn force
1 March 2025Chile: reporting duty and sanctions of Ley 21.663 applyIn force
4 December 2025Mexico: Plan Nacional de Ciberseguridad 2025 to 2030 presentedPlan; general law announced, not enacted as of August 2026 press reporting

Treat every "planned" or "draft" row as a watch item. Mexico's plan sets out three stages (2025 to 2026, 2027 to 2028 and 2029 to 2030), with the general law sent to Congress in the first stage. Peru's draft regulation may change before adoption, including the 48 hour figure.

Enforcement and penalties

  • Chile: the most developed sanctions regime in the region, with fines in UTM that double for OIV. See the Chile guide for amounts.
  • Uruguay: AGESIC can require changes to procedures within deadlines, order specific prevention measures, demand incident information and issue warnings (Art. 79). It must report the list of non-compliant entities to the General Assembly every six months, which makes non-compliance publicly visible.
  • Peru: the duty exists in a decree with force of law; check the final regulation for the supervisory and sanction model before assuming none applies.
  • Brazil, Colombia, Argentina: the cross-sector instruments are governance tools without their own fines; enforcement comes through sector regulators and data protection authorities.
  • Mexico and Costa Rica: no cyber-specific penalties in force; the Mexican plan says the future general law will carry proportional sanctions.

What it means for AI agents and non-human identities

None of these instruments names AI agents or service accounts. They matter anyway, because incident definitions cover compromise of systems and data regardless of whether a person or a credential was the entry point, and because two practical duties depend on machine access.

  • Detection within the clock: a 3 or 24 hour clock starts on awareness. Leaked API keys, abused service accounts and agent tokens are often found late because nobody owns them. Log every non-human credential's use centrally so the first alert can be confirmed in hours, not days. See the Service Account Security Guide.
  • Reportable scope: for an initial report you will be asked which systems and data were reached. An inventory that maps each NHI to its owner, system and data is what makes that answer possible.
  • Supplier credentials: integration tokens held by suppliers bring their incidents into your clock. Keep a register of third-party credentials and revoke on notice. See the Third-Party Credential Register Template.
  • Agent actions as evidence: if AI agents operate on regulated systems, keep tool call and identity logs that can be handed to a CSIRT or regulator. See the AI Agent Audit Trails for Regulators Guide.

Compliance steps

  1. Map entities to regimes. List every legal entity and service by country and decide whether it is an essential service (Chile), a critical service (Uruguay), a listed digital service provider (Peru) or a critical operator (Colombia). Record the reasoning.
  2. Build one incident clock table. For each country, list recipient, clock, form or platform and the parallel privacy deadline. Put the shortest clock (Chile's 3 hours, where it applies) at the top of the incident response plan. See the Incident Response Plan Template.
  3. Register people and platforms in advance. Appoint the Uruguayan information security officer, the Chilean delegate where required and, once adopted, the Peruvian OSCD, and obtain any platform accounts before an incident.
  4. Align the security programme once. AGESIC's framework, ANCI protocols and sector rules overlap with ISO/IEC 27001 and NIST CSF 2.0. Build one control set with a country column for local additions.
  5. Flow duties to suppliers. Add notification clauses with hours, not days, and the right to request incident information, matching what AGESIC and the CSIRTs may ask of you.
  6. Test the clock. Run an exercise that starts with a leaked machine credential and measure time from detection to a draft Chilean early alert and Uruguayan report.
  7. Set a watch list. Track Mexico's general law, Peru's final regulation and Brazil's strategy and plan instruments quarterly, and update the clock table when they change.

Framework mapping

Duty in regional lawsNIST CSF 2.0NIST SP 800-53 Rev 5ISO/IEC 27001:2022 Annex A
Know which national rules applyGV.OC-03PM-15 (contacts with security groups and authorities)A.5.31 Legal, statutory, regulatory and contractual requirements
Report incidents to CSIRT, agency or regulatorRS.CO-02IR-6 Incident ReportingA.5.24 and A.5.26 incident planning and response
Named security officer or delegateGV.RR-02PM-2 Information Security Program Leadership RoleA.5.2 Information security roles and responsibilities

Practitioner checklist

  • Classify every Latin American entity against Chile, Colombia, Peru and Uruguay scope tests and record the result.
  • Publish a single clock table: Chile 3 hours, Uruguay 24 hours, Peru per final regulation, Brazil ANPD three working days for personal data.
  • Register the Uruguayan security officer with AGESIC and any Chilean delegate, with deputies.
  • Pre-create accounts on national notification platforms where entities are in scope.
  • Inventory service accounts, API keys and agent credentials with owners so initial reports can state scope.
  • Add hour-based incident notification clauses to supplier contracts in the region.
  • Exercise a credential-led incident against the shortest clock at least once a year.
  • Review Mexico, Peru, Brazil and Costa Rica developments every quarter.

Standards and references

This guide summarises national cybersecurity laws and policies in Latin America and is not legal advice. Related NHI Mgmt Group resources: Chile Cybersecurity Framework Law · Latin America Financial Cyber Rules · Critical Infrastructure Regulation Map · Cyber Incident Reporting Requirements Map

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 14 November 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.