Habr•October 3, 2026•🇷🇺Translated from Russian

How to Complete the Roskomnadzor Personal Data Notification Form in 2026: Field-by-Field Analysis

The Roskomnadzor notification form is not a questionnaire about a company but an extract from documents that must already exist. Regulators expect operators to copy information already recorded in the personal data processing policy, the list of processed data categories, the appointment order for the responsible person, the act determining the protection level of information systems, and the list of applied security measures.

Before opening the form, operators must verify whether notification is required at all. Following the September 2022 amendments to 152-FZ, only three narrow exemptions remain: data in state information systems created for national security, processing performed exclusively without automation tools, and processing required by transport security legislation. Paper-based card indexes qualify for the second exemption, but Excel files, 1C, CRM systems, email, and cloud storage constitute automated processing.

Five documents supply the answers required by the form. The personal data processing policy provides processing purposes. The attached list of data categories supplies both categories of data and categories of data subjects. The appointment order gives the name and contact details of the responsible person. The protection level act and threat model, prepared under Government Decree No. 1119 of 1 November 2012, feed the largest text block. The list of applied security measures populates the two fields on protective measures and tools.

The form itself contains several practical features. A draft can be saved at any time and later retrieved via a permanent link. Entering an INN triggers an automatic check against the register; if a record already exists, the system blocks submission of a primary notification and offers links to the change-of-information form. An auto-population link can import data from a previously submitted notification using its identifier and email address.

Section I asks for the region of registration, taken from the Unified State Register of Legal Entities, and separately for the regions where processing actually occurs. The latter field refers to territories where staff with data access work or where equipment storing personal data is located, not merely the legal address or client locations.

Subsequent sections require operators to list each processing purpose together with five mandatory details: categories of data subjects, categories of data, legal grounds, actions performed, and data retention periods. Protection measures must be described with reference to the protection level act. Geographic scope, cross-border transfers, and final declarations complete the form.

After submission, the operator remains obliged to keep internal documents up to date and to notify Roskomnadzor of any changes. Failure to submit or submission of inaccurate information can result in administrative liability, although the absence of a record alone does not automatically trigger a fine without detection during an inspection.

Related articles

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.

AntiMalware•Policy & Regulation

Kaspersky Container Security Earns FSTEC Russia Certification as Antivirus Protection Tool

Kaspersky Container Security has received official certification from FSTEC Russia under certificate number 5122 dated October 23, 2026. The product was validated as a means of antivirus protection and meets the regulator’s requirements at the fourth level of trust. It also complies with the protection profile of type B for the fourth class, designated IT.SAVZ.B4.PZ. The certification enables deployment of the solution in government information systems, personal data processing environments, critical information infrastructure facilities, and industrial control systems. Specific usage must still align with individual system requirements and the conditions stated in the certificate. The solution has been listed in the Russian software registry maintained by the Ministry of Digital Development since 2023. Primary audiences include government agencies, large enterprises, and industrial operators that rely on containerized workloads inside regulated perimeters.

AntiMalware•Policy & Regulation

Russian Lawmaker Clarifies Apple and Microsoft ORI Registry Listing Does Not Ban Products

State Duma deputy Anton Nemkin stated that the inclusion of Apple and Microsoft in Russia's ORI registry imposes standard data retention obligations without automatically prohibiting their products. The registry entry requires companies to store user information and message exchange records in Russia for three years and message content for up to six months. Nemkin emphasized that these rules apply equally to Russian and foreign digital market participants regardless of business scale or country of registration. The companies were added on October 2, 2026, while Google Meet has been listed since January 26. Although the status mandates data provision to authorized bodies in legally defined cases, the listing itself does not confirm that corporations will share Russian users' correspondence with the state. Non-compliance may trigger separate regulatory measures, but the deputy urged against exaggerating consequences through sensational headlines.