Habr•August 24, 2026•🇷🇺Translated from Russian

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

Habr•Policy & Regulation

MinTsifry Proposes Requiring Telecom Operators to Install SORM Equipment Before Obtaining Licenses

The Russian Ministry of Digital Development plans to introduce legislation obligating telecom operators to deploy SORM surveillance systems prior to receiving operating licenses. Under the proposed rules, companies will only be permitted to begin serving subscribers after the equipment has been installed and handed over to law enforcement agencies. Non-compliance could result in license revocation through an extrajudicial administrative process. Current regulations allow operators to obtain licenses with a network diagram that merely indicates planned or existing SORM components. The change aims to close loopholes exploited by unscrupulous providers that repeatedly register new legal entities to operate without surveillance capabilities. Industry experts note that the minimum cost of a basic SORM complex starts at 5 million rubles, which could disproportionately affect smaller local providers without a transition period or scaled requirements.

Habr•Policy & Regulation

GOST R 57580 Compliance: Defining Assessment Scope to Verify Real Protection in Financial Organizations

Financial institutions often maintain extensive documentation on information security yet still fail GOST R 57580 assessments due to mismatches between documented processes and actual infrastructure. The standards GOST R 57580.1-2017 and GOST R 57580.2-2018 set distinct requirements for protection levels and evaluation methodology. Correct application begins with identifying the organization's regulatory category under Bank of Russia rules such as Regulation 851-P for credit institutions or Regulation 757-P for non-credit financial organizations. Defining the precise assessment boundary is critical, including systems, remote access channels, virtualization components, and third-party interactions. Organizations must also distinguish between the full assessment scope and the representative sample selected for verification. Evidence collection requires both policy review and technical confirmation that controls function as intended across the evaluated environment.

Habr•Policy & Regulation

Evaluating Secure Development Maturity: Comparing BSIMM, DSOMM, SAMM and GOST R 56939-2024

A detailed analysis compares four methodologies for self-assessing secure software development maturity in Russian companies. The review covers BSIMM from Black Duck, OWASP DSOMM, OWASP SAMM and the updated Russian national standard GOST R 56939-2024. Each model was tested through a simulated audit on a fictional company called ООО «Лиса и лосЬ» that uses GitLab, Nexus and SonarQube. The evaluation scored the methodologies on criteria including ease of maturity calculation, recommendation generation, roadmap building, heat-map creation and SDLC coverage. GOST R 56939-2024 and SAMM received the highest total scores of 35 and 34 out of 47. The article concludes that no single methodology covers all needs and recommends combining approaches tailored to specific company contexts.

Habr•Policy & Regulation

GlobalSign Launches New Wave of SSL/TLS Certificate Revocations Targeting Russian Organizations

GlobalSign has initiated another round of revocations affecting SSL/TLS certificates issued to Russian websites, with a total of 11,000 certificates withdrawn from 1,300 organizations so far. The revocations primarily impact entities listed in EU and US sanctions regimes, in line with updated CA/Browser Forum requirements that took effect in May 2026. Greek CA HARICA has also participated in the revocations, sometimes completing the process within seconds and leaving site owners little time to respond. The actions stem from mandatory checks against the OFAC SDN List, BIS Denied Persons List, and equivalent European sanctions databases. Russian authorities recommend obtaining domestic TLS certificates via Gosuslugi within three business days to maintain secure access in foreign browsers. Let's Encrypt has similarly updated its policies to restrict certificates for sanctioned Russian entities while continuing issuance for others.