Russia Hands Out 2.2 Million Rubles in Data Leak Fines During First Half of 2026
Russian organizations are facing steeper financial consequences for personal data leaks, with authorities issuing 13 fines worth a combined 2.195 million rubles during the first half of 2026.
According to the expert-analytical center InfoWatch, this figure is approximately 1.6 times higher than the total penalties imposed throughout the whole of 2025, which amounted to 1.385 million rubles. The research examined fines for data protection violations both in Russia and worldwide.
Globally, analysts recorded 115 fines over the same six-month period, meaning the Russian cases represented about 11 percent of the international total. Roughly one quarter of the Russian penalties were linked to violations caused by staff actions.
The organizations most frequently fined in Russia operated in the fields of IT and information security, industry, and trade. InfoWatch emphasizes that the new enforcement practice is still gaining momentum.
As of the study’s publication on 27 August, turnover-based fines for data leaks had not yet been applied. Analysts expect more widespread use of the updated rules starting in 2027.
Related articles
Kaspersky Container Security Earns FSTEC Russia Certification as Antivirus Protection Tool
Kaspersky Container Security has received official certification from FSTEC Russia under certificate number 5122 dated October 23, 2026. The product was validated as a means of antivirus protection and meets the regulator’s requirements at the fourth level of trust. It also complies with the protection profile of type B for the fourth class, designated IT.SAVZ.B4.PZ. The certification enables deployment of the solution in government information systems, personal data processing environments, critical information infrastructure facilities, and industrial control systems. Specific usage must still align with individual system requirements and the conditions stated in the certificate. The solution has been listed in the Russian software registry maintained by the Ministry of Digital Development since 2023. Primary audiences include government agencies, large enterprises, and industrial operators that rely on containerized workloads inside regulated perimeters.
Russian Lawmaker Clarifies Apple and Microsoft ORI Registry Listing Does Not Ban Products
State Duma deputy Anton Nemkin stated that the inclusion of Apple and Microsoft in Russia's ORI registry imposes standard data retention obligations without automatically prohibiting their products. The registry entry requires companies to store user information and message exchange records in Russia for three years and message content for up to six months. Nemkin emphasized that these rules apply equally to Russian and foreign digital market participants regardless of business scale or country of registration. The companies were added on October 2, 2026, while Google Meet has been listed since January 26. Although the status mandates data provision to authorized bodies in legally defined cases, the listing itself does not confirm that corporations will share Russian users' correspondence with the state. Non-compliance may trigger separate regulatory measures, but the deputy urged against exaggerating consequences through sensational headlines.
Fines for Telegram Advertising May Be Delayed Beyond Transition Period
Russian authorities are reportedly considering delaying enforcement of new fines targeting advertisers in Telegram after the end of the announced transition period. According to sources cited by the Post- outlet, the government has not yet reached a clear decision on practical application of the advertising ban. Law enforcement agencies are also said to have stepped back from demanding strict punitive measures. Without official confirmation, advertisers and channel owners continue to operate under existing rules. The Federal Antimonopoly Service (FAS) had previously signaled stricter oversight starting in 2027, but current indications point to a possible extension of the status quo. Industry participants are advised to monitor developments closely as the situation remains fluid.
TLS Encrypted Client Hello Officially Standardized as RFC 9849
In March 2026 the IETF published RFC 9849, formally adopting TLS Encrypted Client Hello (ECH) as an official standard for protecting the Server Name Indication field during TLS handshakes. The specification replaces the earlier Encrypted SNI proposal and uses Hybrid Public Key Encryption (HPKE) as defined in RFC 9180 to encrypt the inner ClientHello. Major browsers including Chrome, Edge, Firefox, and Brave now enable ECH by default when Encrypted DNS (DoT or DoH) is active, while Safari remains an exception. Adoption on the server side remains limited; Cloudflare continues to be the only major CDN offering production ECH support, and real-world usage hovers around 0.06 percent of connections despite 20 percent of devices using encrypted DNS. The change breaks SNI-based traffic filtering, proxy inspection, and host-name-driven security analytics, prompting organizations to reassess monitoring architectures. OpenSSL added ECH support immediately after standardization, and Nginx introduced configuration options in version 1.29.4.