Russia's Data Leak Penalties: 2.6 Million Rubles in Fines Despite 1.58 Billion Records Exposed in 2025
Half a year before May 30, 2025, the economics of data leaks in Russia were straightforward: the maximum fine for a legal entity stood at 100,000 rubles, rising to 300,000 rubles for repeat offenses. Implementing effective protection against leaks through DLP systems, audits, dedicated staff, and processes cost tens of millions of rubles annually, making breaches cheaper than prevention.
Federal Law 420-FZ of November 30, 2024, linked fines to the number of affected data subjects and introduced a turnover-based component for repeat violations under CoAP RF Article 13.11. Storage of unnecessary records suddenly carried direct financial risk because each excess entry became a line item in potential penalty calculations.
In the 18 months since the norm took effect, authorities conducted 52 administrative investigations, drew up 40 protocols, and imposed a total of 2.6 million rubles in fines. Not a single turnover fine has been applied. These figures stand against 1.581 billion leaked records in 2025, equating to roughly one-sixth of a thousandth of a kopeck per record.
The volume of fresh data leaks from Russian companies fell noticeably in the first half of 2026, yet activity on shadow marketplaces increased by almost 60 percent. Several non-exclusive explanations exist: operators now sell databases privately rather than publishing them openly to protect reputation; businesses have learned to conceal incidents because disclosure became costlier than silence; and some real reduction occurred as companies began questioning data retention periods instead of simply buying more DLP tools.
The core insight is that investment decisions are driven by expected loss rather than actual penalties paid. When the potential damage figure L in the risk equation p × L increased by two orders of magnitude, budgets were approved regardless of enforcement statistics. This effect has a limited shelf life: without turnover fines materializing in the next two to three years, the modeled probability will approach zero and budgets will follow.
Direct costs include the administrative fine, external forensics starting at 1.5 million rubles per medium incident, subject notification campaigns, and legal defense against individual claims. Indirect costs, often larger, encompass customer churn, increased customer acquisition expenses, service downtime, diverted team time, and higher future insurance and audit premiums. In a modeled service with 3 billion rubles annual revenue and an 800,000-client base, a conservative 2 percent churn already dwarfs all other loss categories combined.
Over-collection now appears on the balance sheet as an unhedged liability. Reducing retention periods from three years to six months directly lowers both risk exposure and infrastructure spend, delivering measurable ROI that most organizations still overlook in favor of additional security tooling.
Related articles
Protecting Data Centers from Kinetic and Cyber Attacks: What Regulators Worldwide Are Proposing
InfoWatch experts have updated their April report on data center resilience, highlighting how physical and cyber threats now directly threaten business continuity and national security. Regulators in the United States, European Union, and Russia are treating data centers as strategic infrastructure requiring layered defenses that combine physical hardening, geographic distribution, and strict cybersecurity controls. The United States has launched the Cyberstrategy for America 2026 emphasizing offensive operations, Zero Trust modernization, and supply-chain restrictions. The European Union is implementing ProtectEU and the Cyber Solidarity Act with real-time threat sharing and mandatory resilience standards under DORA. Russia is advancing technological sovereignty targets, new siting rules for data centers, and Presidential Decree No. 604 that enables temporary state management of inadequately protected critical facilities. The report also notes growing recognition that attacks on data centers can constitute acts of aggression under the Tallinn Manual.
US Department of Homeland Security Orders Federal Agencies to Remove DeepSeek Products
The US Department of Homeland Security issued an order on October 19 requiring federal civilian agencies to cease purchasing products from DeepSeek and to remove related technology from government systems. The directive, published the following day, targets Hangzhou DeepSeek Artificial Intelligence, its affiliates, and any third-party products or services built on DeepSeek implementations. The measure stems from the Federal Acquisition Supply Chain Security Act of 2018 and follows a recommendation by the Federal Acquisition Security Council, though no specific incidents or evidence were detailed in the notice. The restriction applies only to federal environments and does not prohibit private sector or individual use outside government systems. No removal deadline was set, and the document does not name the signing authority. The order is filed under docket DHS-2026-0628 with the CISA implementation team listed as the contact point.
AKIT Requests Temporary Permission for Russian Companies to Transfer Personal Data Abroad After Data Center Incidents
The Association of Internet Trade Companies (AKIT) has sent a formal letter to Russian Prime Minister Mikhail Mishustin proposing a temporary exemption from strict data localization rules. The measure would allow affected companies to move critical systems and Russian citizens' personal data to data centers in friendly countries when domestic infrastructure is unavailable due to accidents or damage. Members including Ozon, Wildberries, Cooper, and Yandex Market argue that services must continue operating even if Russian facilities are compromised. The proposed special regime would apply only after an officially confirmed incident, require compliance with information security standards, and end no later than March 1, 2028. After recovery, companies would be required to return to normal data processing within Russia. Expert Alexey Muntyan noted that the mechanism activates only after incidents occur and questioned whether countries should be selected based on data protection levels rather than political alignment.
Anthropic Model Reconstructs NSA Seeds for NIST Elliptic Curves in Under 30 Minutes
An internal Anthropic research model traced the origins of the five seeds used by the NSA to generate the NIST elliptic curves P-192, P-224, P-256, P-384, and P-521. The discovery resolves a 25-year-old question that arose when the curves were standardized in FIPS 186-2 for ECDSA in 2000. Researchers combined analysis of 1990s random number generators, 34 generator-output combinations, and lattice reduction techniques to identify lrand48 initialized with Unix timestamps from May 1997 to April 1998. The P-256 seed corresponds to the 1842nd candidate from a run started on 16 August 1997, and example seeds from ANSI X9.62 follow the same pattern. The work does not demonstrate any cryptographic break or backdoor in the curves and does not recommend changes to production systems. Several questions remain open, including the seed for curve B-163 and the reason certain candidate values were discarded.