RUEN
Home/Materials/Why companies hide cyberattacks
Cybersecurity and continuity

Why companies hide cyberattacks — and what it leads to

First, partners are told about “scheduled maintenance”. Then the company admits there was an attack but says it “dealt with it quickly”. In fact, it spends another six months restoring its processes. Why businesses hide cyberattacks, and why it costs them dearly.

Updated: 26 June 2026 · Author: Evgeny Telenkov · ≈ 6 min read

How it usually looks

The scenario repeats from company to company. First, clients and partners are told that “scheduled maintenance” or a “software update” is under way. When it can no longer be hidden, the company cautiously admits that yes, there was an attack, but everything is under control. In reality, weeks and months go into restoring processes, searching for lost data and rebuilding what had worked for years.

Ransomware, a stolen database, systems down for several days: companies of every size go through this. It is simply embarrassing to admit it in public, so the market sees the true scale only out of the corner of its eye.

Why they hide it

The reasons are clear: fear of losing clients and reputation, reluctance to show weakness to competitors, and worry about questions from regulators and partners. As a result, the incident is “swept under the carpet”, no lessons are learned, and the company stays just as vulnerable to the next blow.

The real scale of the damage

The most worrying part is that damage of hundreds of millions of roubles, and sometimes as much as RUB 1 billion, hardly surprises anyone any more. The number of attacks on businesses in Russia almost doubled in a year. Gradually, people have come to see this as an unavoidable cost of doing business.

Key point: protection would have cost a tenth of the price of recovery after the blow, or even less. The same tasks can be handled in advance: understand your vulnerabilities, build resilience and train the team to act in a crisis.

What to do about it

Secrecy does not cure the problem. It keeps the problem in place. Healthy practice is the opposite: accept in advance that an incident can happen to anyone, and prepare for it. This means knowing your critical processes, having a recovery plan and backup options, and after any incident, examining its causes openly instead of hiding them.

You can find out how resilient your business is right now. Start with a short assessment that shows your level of readiness and your main risks.

Hide or disclose: the consequences for the business

StrategyShort-term effectLong-term outcome
Complete silenceNo panic, quiet repairsThe leak comes out, and the loss of trust and the fines hit twice as hard
Partial admissionA managed story for the mediaInconsistencies damage trust more than the attack itself
Honest disclosureA short wave of negative coverageReputation as a reliable partner, client loyalty
Disclosure plus lessons learnedAttention from the industry, questions from clientsStatus of a mature company; the case works for the brand

Frequently asked questions

Do you have to report a cyberattack?

For some organisations and types of data, the law requires notifying regulators. But even where you may formally stay silent, concealment usually costs more: causes that were never investigated raise the risk of a repeat incident.

Why is prevention cheaper than recovery?

Recovery means downtime, lost data, fines, client churn and reputational damage, all at once. Preventive measures (assessment, a continuity plan, redundancy, training) cost a fraction of that and reduce both the likelihood and the consequences.

Is your team ready for the first hour of a crisis?

You test a plan by running a scenario. Reading it is not enough. The assessment shows the gaps, and the corporate format works through them with your team on your own processes.

Evgeny Telenkov
Director, Business Continuity Practice · PhD in Economics · Academic Director and Chief Examiner
Best Risk Manager of Russia 2020 (RusRisk). Built business continuity at Nornickel from scratch. Author of more than 30 continuity plans. Worked in the risk functions of Beeline, Rosneft and EY. Chief Risk Officer of a USD 20 billion petrochemical megaproject. Deputy Chair of Rosstandart Technical Committee 010 “Risk Management”, co-author of six GOST R standards. Author of the ERGP and SAFE programmes.
Section 05 · Crisis and cyber threats What to do in a cyberattack → · All materials in this section