How CISOs Can Speak to CEOs: Translating Cyber Risks into Business Impact and Financial Consequences
The morning of July 28, 2025, brought a major cyber incident to Aeroflot, resulting in widespread flight cancellations. Groups Silent Crow and Belarusian Cyber-Partisans claimed they had maintained access to the airline’s internal network for over a year, exfiltrated data, and disabled thousands of servers. Although the company did not publicly confirm the full scope, the operational fallout—canceled flights, a criminal case opened by prosecutors, market scrutiny of shares, and stranded passengers—moved the event beyond purely technical territory.
In almost every large organization, security teams have previously documented weak points such as legacy systems, third-party contractors, privileged accounts, and poorly segmented networks. Yet these warnings are frequently viewed by executives as routine budget requests rather than credible scenarios for business disruption. The core issue often lies not in firewalls or detection tools but in the language used to convey risk to the CEO.
Two Languages in One Office
CISOs typically present data on EDR coverage, mean time to detect, vulnerability remediation rates, and multi-factor authentication adoption. CEOs mentally convert these figures into questions about potential financial loss, halted processes, accountability to customers and regulators, and effects on revenue if action is postponed. Surveys by EY reveal a perception gap: 68% of CISOs believe senior leadership underestimates cyber threats, while 57% of other C-level executives agree. Splunk’s CISO Report 2025 shows that 46% of CISOs measure success by security milestones, compared with only 19% of board members who expect return-on-investment language and concrete damage reduction.
Real-World Consequences of Miscommunication
Several 2024–2025 incidents illustrated the cost of failing to translate technical risks:
- Marks & Spencer lost contactless payments and online order fulfillment for weeks after an attack attributed to a third-party contractor, with profit impact estimated at £300 million.
- Jaguar Land Rover halted global production for nearly six weeks following detected unauthorized activity, causing an estimated £1.9 billion loss to the UK economy.
- Clorox filed a $380 million lawsuit against Cognizant over a 2023 incident allegedly enabled by inadequate identity verification at the service desk.
- Change Healthcare suffered a breach through a Citrix portal lacking multi-factor authentication; UnitedHealth later confirmed a $22 million ransom payment and exposure affecting approximately 190 million individuals.
Regulatory Pressure and Personal Liability
Actions by the SEC against SolarWinds CISO Timothy Brown and the criminal conviction of Uber’s former security chief Joe Sullivan established that statements to regulators and disclosure timing can result in personal legal consequences. In Russia, Federal Law No. 420-FZ introduced turnover-based fines for personal data breaches, reaching 1–3% of annual revenue. These developments make cybersecurity a direct concern for boards and top executives.
Recommended Translation Approach
The article supplies a practical mapping of common CISO statements into language CEOs understand, emphasizing specific business processes that could stop, daily downtime costs, and comparisons between proactive investment and post-incident remediation expenses. Effective dialogue begins with three questions: which business process may halt, what a day of downtime costs, and whether reducing risk now is cheaper than explaining consequences later.
Related articles
Russian Businesses Face 50-Ruble Fee per MVD Query for Passport and Residence Checks
The Russian government has backed a proposal requiring businesses to pay 50 rubles for each completed session querying Ministry of Internal Affairs databases. The fee covers checks on Russian passport validity, residence registration, residence permits, and foreign citizen migration records. Projected annual budget revenue reaches 120 billion rubles. Companies must still perform client identification under Federal Law 115-FZ and the Law on Communications, with fines up to 0.1 percent of own funds for banks or 500,000 rubles for telecom operators. Smart Engines highlights its Sherlock anti-fraud platform as a local alternative that detects over 600 forgery indicators, including deepfakes and NFC chip tampering, without repeated paid queries. The company cites a June 2026 legal opinion from the National Council of Financial Markets confirming that such tools can satisfy compliance requirements.
Russian Court Convicts Former IT Director for Unauthorized Access to Huawei Storage After Moving Servers Offsite
A former IT director at an Omsk manufacturing plant was found guilty under Part 3 of Article 272 of the Russian Criminal Code for blocking and modifying data on a Huawei Dorado 3000 v6 storage array after relocating the entire server infrastructure to a privately rented office. The court relied heavily on detailed logs from the Huawei system that recorded the exact sequence of disk removals, reinsertions in altered order, and the shutdown command, even after the administrator attempted to delete portions of the event journal. The incident occurred on the same day new management took over, causing immediate loss of access to corporate email, 1C systems, design software, and shared network resources. Despite the defendant's claims that he was preparing the array for cloud backup and that a script had frozen, the court rejected the explanation based on audit concealment, lack of notification to owners, and post-incident behavior. The ruling imposed a 400,000-ruble fine and a one-year ban on computer-information work involving protected secrets, while leaving a civil claim for 18.27 million rubles in recovery costs for separate proceedings. The case highlights how storage-array logs can serve as decisive forensic evidence and underscores the legal risks of retaining physical or logical access after employment ends.
False 50,000 Ruble Fine Claims Circulate About Russia's Unified Bank Card Registry
Social media posts falsely warn Russian citizens of a 50,000 ruble fine for failing to submit personal bank card data to a new unified registry. The claims have been identified as fabricated, with the project "Lapsa Media" noting that the accompanying images were likely generated by AI and contain multiple errors and typos. In reality, individual citizens are not required to take any action, as banks themselves will transmit the necessary information. The Bank of Russia has confirmed that banks must upload card numbers, card types, and owners' INN identifiers to the system operated by NSPK no later than September 1, 2027. Starting on that date, banks will begin enforcing a limit of 20 cards per client to hinder mass issuance of cards for fraudulent purposes. Previously issued cards exceeding this limit will remain valid and will not be forcibly closed.
Webiomed AI Platform Processes Millions of Medical Records Daily on Certified RED OS Infrastructure
The Russian Webiomed platform now serves more than 4,000 medical organizations across 55 regions and supports over 300,000 physicians. Its algorithms analyze up to one million electronic health records every day, generating recommendations that physicians must review and approve. The entire server infrastructure runs on RED OS, which holds FSTEC Russia certification for use in critical information infrastructure. Legal responsibility for any harm remains with the medical organization and, in some cases, the individual physician, even when AI suggestions are involved. The article highlights risks such as incomplete data, synchronization errors that could revoke physician access via RED ADM directory services, and the need for selective recovery tools like Granulex Recovery. Joint testing by MDIS and RED SOFT confirmed that Granulex Recovery can restore specific objects and attributes without stopping the directory service. Questions remain about where liability falls when errors occur at the intersection of the algorithm, medical systems, and underlying IT infrastructure.