Novosibirsk · Russian-qualified counsel Recognised by Pravo-300 · Best Lawyers · Kommersant
Corporate & Regulatory

Recent Russian judicial practice on incident response and notification obligations under Russian law — commentary

Elena Pavlova · July 2026 · 5 min read

Russian courts are clarifying when data incident notification obligations arise. In-house counsel should review their procedures. Make an enquiry.

In a period when Russian courts are actively shaping how statutory obligations translate into live compliance programmes, a recent line of decisions concerning incident response and notification obligations under Russian data protection legislation has drawn the attention of in-house counsel at foreign companies operating in Russia. The decisions do not alter the statutory framework — the core notification requirements introduced by amendments effective September 2022 remain unchanged — but they clarify the evidentiary and procedural standards to which operators will be held when Roskomnadzor or a court examines whether notification was timely and adequate.

Background

Russian data protection legislation requires operators who process personal data to notify Roskomnadzor in two stages following the discovery of an incident that compromises the security of personal data: an initial notification within twenty-four hours of discovery, followed by a fuller report within seventy-two hours. For multinational subsidiaries and Russian operating entities owned by foreign groups, meeting these deadlines requires internal escalation protocols that function independently of head-office approval cycles — a coordination challenge that frequently surfaces only when an incident has already occurred. The cases under commentary arose from enforcement proceedings initiated after Roskomnadzor reviewed notification submissions from several operators and found them procedurally deficient. In each instance, the supervisory authority took the position that the operator had failed either to notify within the prescribed window or to provide substantive information in the initial notification. The matters proceeded through administrative and judicial review, with courts asked to consider what standard of conduct the legislation demands and how documentation of the discovery timeline should be assessed.

What did the court decide?

The courts upheld the core principle that the twenty-four-hour clock runs from the moment the operator had grounds to conclude that an incident affecting personal data had occurred — not from the moment internal investigation confirmed the full scope of the breach. This distinction is significant. In practice, operators frequently delay initial notification while their IT security teams assess the scale of the incident, on the basis that a premature notification may be factually incomplete. The courts rejected this approach as a general rule, holding that an initial notification submitted with limited technical detail is preferable — and compliant — provided it is supplemented by the seventy-two-hour report. A secondary finding concerned the evidentiary burden. Courts confirmed that the operator bears the burden of demonstrating when discovery occurred, and that internal ticketing systems, security operations logs, and contemporaneous communications would be assessed for consistency. Operators whose records showed awareness of anomalous activity before the date recorded as the formal discovery date faced adverse inferences.

"What these decisions establish is a documentation discipline, not merely a notification obligation — operators must be able to reconstruct the precise moment of discovery from records that predate any regulatory inquiry." — Elena Pavlova, Associate, Vetrov & Partners

If your organisation is reviewing its incident response procedures in light of recent Russian court decisions, make an enquiry: info@vetrovpartners.com |

What does this ruling mean for foreign companies in Russia?

For in-house counsel managing Russian subsidiaries or branches from abroad, these decisions have three practical consequences. First, the internal definition of "discovery" must be explicit in the organisation's incident response policy. Vague language — such as "upon confirmation of the incident" — will not withstand scrutiny if Roskomnadzor can point to earlier log entries or helpdesk records. Second, the twenty-four-hour initial notification should be treated as a low-threshold obligation: file early, file with whatever information is available, and supplement within seventy-two hours. Third, the evidential weight placed on contemporaneous records means that security operations documentation maintained in Russian — or at least translatable into Russian without material delay — is likely to be treated more favourably in any subsequent review. Foreign companies operating through a Russian entity are advised to confirm that their incident response runbooks reflect these standards and that the Russian legal entity has authority to notify Roskomnadzor independently, without waiting for group-level sign-off. The Data Protection practice at Vetrov & Partners has assisted clients in reviewing and updating their notification procedures in the light of this developing judicial practice. Related guidance on the regulatory framework is available at Regulatory Update: Incident Response and Notification and Foreign Creditors and Incident Response Notification Obligations.

To discuss how these decisions apply to your organisation's Russian operations, make an enquiry: info@vetrovpartners.com |

Frequently asked questions

Q: What does this ruling change?

A: The decisions do not amend the statutory notification timeline — the twenty-four-hour and seventy-two-hour requirements remain as enacted. What has changed is the courts' articulation of when the notification clock begins. Operators can no longer rely on the completion of an internal investigation as the trigger; the clock runs from the point at which the operator had reasonable grounds to conclude an incident had occurred. For companies with mature incident response programmes, this may require a revision to internal policy definitions rather than a wholesale procedural overhaul.

Q: What should foreign companies do in light of this decision?

A: In-house counsel should review three areas: the internal definition of "discovery" in the organisation's incident response policy; the independence of the Russian legal entity to file a Roskomnadzor notification without group-level approval; and the completeness and contemporaneousness of security operations logs maintained by the Russian entity. Where existing runbooks require investigation sign-off before notification is triggered, those documents should be updated. Companies that have not yet mapped their Russian incident response obligations to local procedural requirements should consider doing so before their next internal audit cycle.

Practitioner note

This briefing is general information and does not constitute legal advice. For advice on a specific matter, write in confidence to info@vetrovpartners.com.

Facing a matter like this?

Our team advises foreign clients on exactly these questions across Russia and the EAEU region. Initial 30-minute consultation — complimentary.

Make an enquiry