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

Foreign creditors and incident response and notification obligations under Russian law: a briefing for general counsel

Elena Pavlova · February 2026 · 12 min read

Foreign companies face 24-hour Roskomnadzor notification on data breaches under Russian law. Key steps for in-house counsel. Make an enquiry.

Following amendments to Russian personal data legislation that introduced mandatory breach-notification timelines, general counsel at foreign companies with Russian operations face a structured set of regulatory obligations that activate the moment an incident is identified. The requirements are procedurally precise, time-critical, and enforced by Roskomnadzor – the federal supervisory authority for personal data. For in-house counsel accustomed to GDPR's 72-hour notification window, the Russian framework contains both familiar elements and material distinctions. Understanding each procedural step before an incident occurs is not preparation for an unlikely event; it is a compliance baseline for any foreign company that processes personal data of Russian individuals.

What to prepare before an incident occurs

Effective incident response under Russian law begins not at the moment a breach is discovered, but in the operational and documentary groundwork that precedes it. The following checklist reflects the minimum preparatory state that general counsel should verify for any Russian-facing entity.

What to prepare — minimum readiness checklist:

If your Russian entity's incident readiness has not been reviewed recently, make an enquiry: info@vetrovpartners.com |

Step 1 — Assess the incident: what triggers notification obligations?

Not every operational disruption or system failure triggers mandatory notification under Russian personal data law. The obligation activates when there has been an unlawful or accidental loss, modification, destruction, blocking, or disclosure of personal data of individuals whose data is processed by the operator. The key threshold question for general counsel is whether personal data – defined broadly under Russian legislation to mean any information relating to an identified or identifiable individual – has been compromised in a manner that falls within the statutory triggers.

Russian law does not adopt a harm-based threshold equivalent to the GDPR's test of "risk to the rights and freedoms of natural persons." The obligation is triggered by the fact of the incident itself, not by an assessment of the probable impact on data subjects. This is a significant practical distinction: in-house counsel familiar with GDPR may instinctively begin a harm-assessment exercise before deciding whether to notify; under Russian law, that assessment does not suspend or defer the notification obligation.

The assessment phase – which must be completed rapidly – should address four questions: (1) Is the compromised information personal data as defined under Russian law? (2) Does the company hold the status of personal data operator or personal data processor in Russia? (3) Is there evidence of unlawful access, disclosure, destruction, or modification, or of a loss of control over the data? (4) Can the scope of affected individuals be identified or estimated at this stage? The answers to these questions determine both the immediacy and the content of the notifications that follow.

In a recent engagement, the firm advised a European group company that had experienced a supplier-side systems compromise affecting a Russian customer database. The assessment phase – conducted jointly by internal IT security, external forensic consultants, and Russian legal counsel – established within hours that the incident met the statutory threshold, allowing the notification process to begin before the 24-hour clock became a pressure point rather than a planning window.

Step 2 — Notify Roskomnadzor: the 24-hour and 72-hour obligations

The Russian legislative framework creates a two-stage notification obligation addressed to Roskomnadzor. The first notification must be submitted within 24 hours of the operator becoming aware of the incident. This initial notification is intentionally brief: it identifies the operator, describes the nature of the incident, the approximate scale of data affected, and the immediate containment steps taken or underway. Roskomnadzor publishes a prescribed submission channel – its official portal – and the notification must be directed there.

The second, fuller notification must follow within 72 hours of the operator becoming aware of the incident. This submission is materially more detailed: it must describe the causes of the incident (to the extent determinable at that stage), the categories and volume of personal data affected, the consequences of the incident as assessed by the operator, and the measures taken or planned to address the breach and prevent recurrence. Where the investigation is ongoing and full information is not yet available, Russian regulatory practice permits the submission of information on a best-available basis, with a commitment to provide supplementary detail as the investigation progresses – but the 72-hour window itself is not extended.

For foreign companies, the practical difficulty is that both notifications must be submitted in Russian and through Roskomnadzor's official portal, which requires prior registration. General counsel should confirm that the entity's Roskomnadzor registration is live and that someone with portal access credentials is available at short notice. Correspondence with Roskomnadzor following the initial notification – including any requests for additional information, inspection visits, or formal enquiries – should be managed by or coordinated with Russian-qualified counsel familiar with the regulator's operational practice.

For assistance drafting Roskomnadzor notifications or managing regulatory correspondence, make an enquiry: info@vetrovpartners.com |

Step 3 — Who must be notified among data subjects, and when?

Beyond the regulatory notification to Roskomnadzor, Russian personal data law imposes a separate obligation to notify the affected individuals whose data has been compromised. The obligation to notify data subjects falls on the personal data operator – that is, the entity that determines the purposes and means of processing. Where the incident involves a processor acting on behalf of the operator, the processor's obligation is to notify the operator promptly; the obligation to notify data subjects then rests with the operator.

The notification to data subjects must be made without undue delay. Russian law does not prescribe a specific hour-count for this obligation in the way the 24-hour and 72-hour Roskomnadzor timelines operate, but "without undue delay" is construed narrowly in regulatory practice and in the decisions of Russian courts. General counsel should treat this obligation as running concurrently with the Roskomnadzor notification process, not sequentially after it.

The content of data-subject notifications under Russian law must include: the nature of the incident and what data was affected; the measures the operator has taken or is taking to address the breach; and information about how the data subject can obtain further information or raise a concern. There is no prescribed format, but the notification must be comprehensible to ordinary individuals – it must not be drafted in the register of a legal notice addressed to professional readers. Where the affected population is large or geographically dispersed, Russian regulatory guidance has indicated that public announcement through mass media or the operator's official website may fulfil the obligation where individual notification is not practicable, but this alternative should be approached with caution and legal advice.

The intersection of data-subject notification with cross-border data transfers and data localisation requirements deserves particular attention for foreign groups. If the personal data in question is subject to the Russian localisation requirement – that is, if it concerns Russian citizens and must be stored on servers located in Russia – then the breach itself, if it involved data held outside Russia in contravention of localisation obligations, creates a compounding compliance problem. Counsel reviewing an incident should confirm the data's storage location early in the assessment phase. For guidance on how these obligations interact, see the firm's Regulatory update on incident response and notification and the related analysis of recent Russian judicial practice on incident response.

Step 4 — Contain, document, and preserve evidence

Regulatory compliance following an incident is not exhausted by the notification obligations. Russian personal data law requires operators to take measures to eliminate the consequences of the breach and to prevent the recurrence of similar incidents. The practical implication is that containment and remediation are not merely operational matters – they form part of the operator's legal obligation and will be scrutinised in any subsequent regulatory review or court proceeding.

Documentation discipline during the incident period is critical. General counsel should ensure that a contemporaneous log is maintained from the moment the incident is identified: recording who was notified, when, and in what terms; what containment steps were taken and when; what evidence was preserved; and what communications were issued internally and externally. This log serves a dual function: it supports the 72-hour Roskomnadzor notification and provides the evidentiary base for any follow-on regulatory enquiry or litigation defence. Under the civil procedure rules governing Russian state court proceedings, the party with the burden of demonstrating compliance bears the evidentiary cost of gaps in documentation.

The evidence preservation obligation is particularly important where the incident involves a third-party supplier, a cloud services provider, or a counterparty in a commercial relationship that includes personal data processing. Service-level agreements and data-processing agreements should be reviewed for notification-trigger and evidence-preservation clauses at this stage. Where those agreements are governed by foreign law, Russian legal counsel should review whether the Russian law obligations are fully addressed or whether there are gaps requiring immediate remediation. Vetrov & Partners advises on data protection matters and can review existing contractual frameworks in the context of a live incident or as part of a preparedness review. Foreign companies that have handled prior data incidents in Russia are also encouraged to review the Matters Hub for illustrative engagement profiles.

Step 5 — What does a post-incident compliance review require?

Once the immediate notification obligations are discharged and containment measures are in place, Russian personal data law contemplates a post-incident phase that extends the operator's obligations. Roskomnadzor retains the authority to conduct an unscheduled inspection following a notified breach, and the operator's response to such an inspection – including the documentation presented, the measures described, and the undertakings given – materially affects the regulatory outcome.

A post-incident compliance review should address at minimum: whether the root cause of the incident has been identified and whether a structural rather than symptomatic fix has been applied; whether the operator's data-processing records (including the register of personal data processing operations) have been updated to reflect any changes to systems, third-party relationships, or processing activities that the incident revealed; whether staff with access to personal data have received updated guidance or training; and whether the incident reveals any gap in the operator's cross-border data transfer authorisation, localisation compliance, or consent-collection procedures.

For foreign companies, the post-incident review is also the appropriate moment to assess whether the incident and the regulatory response have created any exposure under foreign data protection regimes – particularly the GDPR, where the Russian breach notification will not, in itself, satisfy the GDPR obligations if those are also triggered. General counsel should coordinate the Russian post-incident workstream with the GDPR response managed by European counsel, ensuring that the two notifications and the subsequent remediation records are consistent and do not create contradictory accounts of the same incident. For matters requiring cross-jurisdictional coordination, the firm collaborates with trusted counsel in the relevant jurisdictions. See also the firm's practice page for Regulatory & Licensing matters where related licensing obligations may be in scope.

The regulatory timeline leaves limited margin for delay in completing this review: if Roskomnadzor schedules an inspection, it will typically do so within a period during which the facts of the incident are still fresh and documentation gaps are most apparent.

For a post-incident compliance review or to discuss preparedness for Russian regulatory obligations, make an enquiry: info@vetrovpartners.com |

Frequently asked questions

Q: How quickly must a foreign company notify Roskomnadzor after discovering a personal data breach in Russia?

A: The initial notification to Roskomnadzor must be submitted within 24 hours of the operator becoming aware of the incident. A second, more detailed notification must follow within 72 hours. Both timelines run from the moment of awareness, not from a formal internal declaration of a breach. Foreign companies operating in Russia should confirm in advance that their Roskomnadzor registration is current and that portal access credentials are available to authorised personnel at short notice, since the 24-hour window does not accommodate a registration process initiated at the time of an incident.

Q: What documents should a foreign company have ready before an incident occurs?

A: At minimum, the company should hold: a current Roskomnadzor registration as a personal data operator; pre-drafted template notifications in Russian for both the initial 24-hour and the fuller 72-hour submissions; a designated responsible person with authority to submit notifications and correspond with the regulator; a contemporaneous incident log template that records decisions, timelines, and communications from the moment an incident is identified; and a confirmed relationship with Russian-qualified counsel who can be reached outside normal business hours. The absence of any one of these elements typically extends the response time into the period when regulatory timelines have already begun to run.

Q: Does a Russian data breach notification discharge the GDPR notification obligation for the same incident?

A: No. A notification to Roskomnadzor under Russian personal data law is a distinct obligation directed to a distinct supervisory authority and does not constitute or substitute for a notification to a European data protection authority under the GDPR. Where the same incident triggers both regimes – which is common for foreign groups that process personal data of both Russian and European individuals – general counsel must manage two parallel notification streams, directed to the appropriate authorities in each jurisdiction, within the applicable timelines. The content and framing of the two notifications must be consistent: contradictory accounts of the same incident in different regulatory submissions create independent compliance exposure. Coordination between Russian and European counsel from the outset of the incident response is the standard approach.

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