
On July 17, 2026, a Colombian state-owned company detected unauthorized access to its digital resources and blocked an encryption attempt. The technical controls did exactly what they were supposed to do. Two days later, the organization publicly announced that the integrity of the information had not been compromised.
On July 27 —ten days after the access— the attackers published the files they had taken from fifteen companies in the group. During those ten days, the story of the incident was not written by the affected organization. It was written by the attacker. That gap, and not the technical failure, is what this case leaves for anyone responsible for information security.
The technical side worked. The narrative did not
The containment was correct: access detected, encryption blocked, systems under control. In information security terms, that is a good result. But the question that decides an organization’s reputation after an incident is not whether it contained the attack, but who told the story first and how accurately. When the information vacuum is filled by the attacker, every subsequent statement by the organization reads as a reaction, not as control.
The timeline: ten days apart
- July 17, 2026 — unauthorized access detected; encryption attempt blocked; extortion demands made.
- July 19 — public statement: the integrity of the information was not compromised.
- July 27 — the attackers publish the files copied from fifteen companies in the group.
Both statements can be true at the same time —not compromising integrity is not the same as preventing exfiltration— and that is the problem. A technically accurate statement that the public interprets as “nothing happened” becomes a liability the day the files appear online.
Two different capabilities, two different preparations
Containing an attack and responding publicly to an attack are separate capabilities. They are prepared differently, rehearsed differently and fail differently. The first lives in the IT team and is measured in minutes. The second involves management, legal, human resources, procurement and communications, and is measured by how the organization stands with its stakeholders months later.
Most incident response plans describe in detail what to shut down, what to isolate and what to restore. Very few describe what to say, who says it and in what order.
The regulatory clock keeps running
In Colombia, Law 1581 of 2012 and Chapter II of Title V of the Superintendence of Industry and Commerce’s Single Circular —amended by External Circular 002 of 2015— require security incidents affecting personal data to be reported within fifteen (15) business days of their detection and notification to the responsible area. That deadline runs whether or not the organization is prepared, and failure to comply creates a sanctioning exposure separate from that of the incident itself.
While the technical team isolates systems, someone has to answer the employees asking whether their data is in those files, the contractors, the suppliers and the regulator.
What must be written down before the incident
Four decisions that no organization makes well by improvising at three in the morning:
- Who decides. A crisis committee with names, alternates and real authority to speak without waiting for chain approval.
- Who speaks. A single spokesperson per audience, with the other channels closed. Parallel versions are the attacker’s favorite material.
- With what message. Core messages drafted and approved in advance, by scenario and by audience: employees, contractors, suppliers, clients, regulator, media.
- In what order. The notification sequence, with regulatory deadlines built into the timeline and not looked up afterwards.
The reference standard for this capability is ISO/IEC 27001:2022, in its Annex A controls 5.24 to 5.27 —incident planning and preparation, assessment, response and learning— and, for continuity and crisis communication, clause 8.4.3 of ISO 22301:2019, which requires documenting what, when, with whom and how to communicate during a disruption.
Are you prepared to respond
Don’t worry about when you will be attacked. Focus on being prepared to respond.
At AXONA we do not sell the promise that you will not be attacked. We prepare the response for when it happens: who decides, who speaks, with what message and in what order.
Does your response plan include what you will say, or only what you will shut down?
Write to us at contacto@axona.org and we will send you the four questions your plan should answer: who decides, who speaks, with what message and in what order. If your plan already answers them in writing, with an assigned owner, you don’t need anything else from us. If any of them is blank, that is your next task — and that conversation is worth having before the incident.
Public sources for the case referred to
- Confirmation of the unauthorized access and the extortion demands — Portafolio, 07/17/2026.
- The organization rules out any impact on the integrity of the information — Portafolio and Vanguardia, 07/19/2026.
- Publication of the files copied from fifteen companies in the group — El Colombiano and El Espectador, 07/27/2026.
- Threat intelligence report on ransomware in Colombia IN-20260802-043 — ColCERT, 08/02/2026.
- Fifteen-business-day deadline to report security incidents involving personal data — SIC Single Circular, Title V, Chapter II.
CYBER by AXONA — ICT Services · Sergio Javier Martínez R., CEO AXONA
Need support on this topic? We offer an initial scope assessment at no cost.
Let’s talk about your case →About the author
ONAC Lead Evaluator since 2012 and ISO Management Systems Lead Auditor since 2005 at accredited certification bodies. Industrial Engineer, Master in Organizational Management and Specialist in Occupational Health and Safety. Graduate professor in specialization and master’s programs at Colombian universities. More than 25 years of experience in manufacturing and services, in the public and private sectors.
View professional profile on LinkedIn →