In Russia, operators must report data breaches to Roskomnadzor within 24 hours. What GCs with Russian operations need to know. Make an enquiry.
Amendments to Russian personal data legislation that took effect following a series of high-profile data leaks have materially changed the obligations placed on every operator that processes the personal data of Russian subjects. Foreign companies with Russian subsidiaries, branches, or digital service operations are subject to the same framework as domestic operators – and, in practice, face greater operational difficulty in meeting the notification deadlines that the law now imposes. This update sets out what changed, who is affected, and what in-house counsel managing Russian operations should do to ensure their organisation is in a position to respond.
Before the 2022 amendments to Federal Law No. 152-FZ on Personal Data, Russian law imposed no hard notification deadline for personal data incidents. Operators were expected to take measures to address breaches, but there was no obligation to notify the supervisory authority within a defined timeframe, and there was no mandatory notification to affected data subjects. The regulatory landscape has shifted substantially.
Under the current framework, an operator that discovers a personal data breach – meaning any incident involving unauthorised access, disclosure, dissemination, or destruction of personal data – must notify the Federal Service for Supervision of Communications, Information Technology and Mass Media (Roskomnadzor) within 24 hours of discovery. This is the first notification, and its function is to alert the regulator that an incident has occurred. It does not require the operator to have completed a full investigation.
A second, more detailed notification is required within 72 hours of the initial discovery. That notification must include the results of the operator's internal investigation: the categories of personal data affected, an estimate of the number of data subjects whose data was compromised, the cause of the breach (insofar as it can be established), and the measures the operator has taken or intends to take in response. Where the investigation is not yet complete at the 72-hour mark, operators are generally expected to submit what is available and supplement the filing once further information is obtained – though the obligation to file on time is not suspended because the investigation is ongoing.
Notifications are submitted through a dedicated portal operated by Roskomnadzor. Foreign operators who are registered as personal data operators in Russia (which is itself a distinct obligation under the law) are expected to use the same portal. Operators who have not completed their Roskomnadzor registration face a compounding compliance problem: they are both unregistered and unable to notify through the standard channel.
"The shift from a disclosure-at-will approach to a hard dual-deadline obligation is the most operationally significant change to Russian data protection law in the past decade. The practical difficulty for foreign operators is not understanding the rule – it is building the internal process to honour it." — Elena Pavlova, Associate, Vetrov & Partners
The notification obligation applies to any entity that qualifies as a personal data operator under Russian law – that is, any organisation (or individual) that independently determines the purposes and means of processing personal data. For foreign companies, the key question is whether their Russian-connected activities bring them within the definition.
In practice, the obligation is likely to engage any foreign company that: operates a Russian legal entity (subsidiary, representative office, or branch) that maintains HR records, client databases, or any other repository of personal data relating to individuals in Russia; provides digital services to consumers or businesses in Russia and processes their personal data in connection with those services; or processes personal data as part of a cross-border data transfer arrangement where Russian subjects are among the data subjects.
Foreign companies that have taken the position that their Russian data processing is minimal or incidental should revisit that assessment. Russian courts and Roskomnadzor have, in recent enforcement practice, taken a broad view of what constitutes processing activity sufficient to engage the operator designation. The storage of a contact database, the logging of IP addresses, or the maintenance of an employee payroll in Russia can each be sufficient.
For foreign companies that are members of groups subject to the EU General Data Protection Regulation, there is an important distinction to draw. The GDPR's 72-hour notification requirement to a supervisory authority runs from the point at which a controller becomes aware of a breach; the Russian 24-hour requirement runs from discovery, and Roskomnadzor has indicated that discovery for these purposes is not limited to formal confirmation – awareness of an incident at any level of the organisation capable of acting on it can trigger the clock. Group companies should therefore ensure their Russia-specific incident response procedures do not rely on GDPR timelines.
If your organisation processes personal data in Russia and has not yet reviewed its incident response procedures against the current Russian framework, this is a material compliance gap. Make an enquiry: info@vetrovpartners.com |
The primary compliance challenge is operational, not legal. The rules are sufficiently clear; the difficulty lies in building an internal process that can meet a 24-hour notification deadline – an interval that is substantially shorter than most multinational incident response procedures are designed to accommodate.
In-house counsel responsible for Russian compliance should consider the following priorities.
First, confirm the organisation's registration status with Roskomnadzor. Without valid registration as a personal data operator, the organisation cannot notify through the correct channel, and non-registration is itself a separate regulatory violation. The registration obligation applies to operators regardless of whether they have experienced an incident.
Second, review existing incident response procedures against the Russian timeline. Most international incident response frameworks are built around 72-hour notification cycles. Where Russian operations are in scope, a parallel 24-hour notification stream must be grafted onto the existing framework, with clear ownership, escalation triggers, and pre-approved notification text to reduce the decision time when an incident occurs.
Third, identify the categories of personal data processed in Russia and the systems in which they are held. The 72-hour notification requires this information; producing it for the first time during an active incident is likely to result in either a missed deadline or a materially incomplete filing. A data mapping exercise conducted in advance reduces both risks.
Fourth, consider the position of Russian subsidiaries. Where a foreign parent is the group entity that controls incident response, it must ensure that its Russian subsidiary has clear authority and instruction to notify Roskomnadzor without waiting for group-level approval – a process that, under normal group governance, may take longer than 24 hours.
Fifth, note the separate obligations applicable to operators of critical information infrastructure (CII). Organisations whose Russian operations fall within the definition of CII – which includes certain operators in energy, finance, healthcare, transport, and communications – face additional incident notification obligations to the state system GosSOPKA, administered by the Federal Security Service (FSB). The timelines and technical requirements for GosSOPKA notifications differ from those applicable under 152-FZ and must be addressed through a separate compliance stream.
For in-house counsel managing Russian data protection compliance, early-stage guidance on registering with Roskomnadzor and structuring incident response procedures is more cost-effective than remediation after a breach. Request our practice review: info@vetrovpartners.com |
Operators that fail to notify Roskomnadzor within the required timeframes face administrative sanctions. The Russian administrative regime for data protection violations has been progressively tightened, and the trend in enforcement activity reflects an increased willingness on the part of Roskomnadzor to investigate and sanction operators that fail to comply with notification obligations. Sanctions may include administrative fines and, in cases involving repeated or egregious violations, potential criminal exposure for responsible individuals under provisions of the Criminal Code concerning unauthorised access to computer information.
Foreign companies should note that the sanctions regime does not distinguish between domestic and foreign operators, and that Roskomnadzor has, in recent years, brought enforcement proceedings against both. The reputational dimension of a public Roskomnadzor enforcement action should also be considered: decisions in significant cases are typically published on the regulator's website.
Beyond regulatory sanctions, operators that fail to notify affected data subjects (where required) face a separate track of potential civil liability. The law permits data subjects to claim compensation for non-material damage resulting from a violation of their personal data rights. While Russian courts have historically applied modest awards in such cases, the volume of claims following high-profile incidents has increased, and group actions remain a developing area of Russian procedural law.
Q: What specifically changed in Russian law on personal data breach notification?
A: Russian personal data law – Federal Law No. 152-FZ – was amended to introduce mandatory incident notification obligations that previously did not exist. Operators are now required to notify Roskomnadzor within 24 hours of discovering a personal data breach, and to submit a more detailed notification within 72 hours that includes the outcome of the operator's internal investigation. Prior to these amendments, there was no hard notification deadline; operators were expected to take remedial measures but were not required to notify the supervisory authority within a prescribed timeframe. The amendments apply equally to domestic and foreign operators processing the personal data of Russian subjects.
Q: Which foreign companies are affected by the Russian incident notification rules, and how?
A: Any foreign company that qualifies as a personal data operator under Russian law is subject to the notification obligations. In practice, this covers foreign companies that maintain Russian subsidiaries, representative offices, or branches that hold HR records or client data; foreign companies providing digital services to users in Russia; and foreign companies involved in cross-border data transfers involving Russian data subjects. Roskomnadzor has taken an expansive approach to the operator designation in recent enforcement practice. Foreign companies in EU-regulated groups should be aware that the Russian 24-hour notification timeline is shorter than the GDPR's 72-hour standard and requires a separate, parallel compliance procedure.
Q: What should in-house counsel do following the Russian incident notification amendments?
A: In-house counsel responsible for Russian compliance should as a priority confirm their organisation's registration status with Roskomnadzor, map the personal data processed in Russia, and review existing incident response procedures to introduce a parallel 24-hour notification stream for Russian-facing incidents. Organisations whose Russian operations fall within critical information infrastructure categories face additional notification obligations to GosSOPKA that must be addressed separately. Proactive preparation – documentation, clear escalation authority, and pre-approved notification templates – substantially reduces the compliance risk at the point an incident occurs. Vetrov & Partners advises on all aspects of Russian data protection compliance, including Roskomnadzor registration and incident response procedure review.
This briefing is general information and does not constitute legal advice. For advice on a specific matter, write in confidence to info@vetrovpartners.com.
Our team advises foreign clients on exactly these questions across Russia and the EAEU region. Initial 30-minute consultation — complimentary.
Make an enquiry