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
Protecting Data Centers from Kinetic and Cyber Attacks: What Regulators Worldwide Are Proposing
InfoWatch experts have updated their April report on data center resilience, highlighting how physical and cyber threats now directly threaten business continuity and national security. Regulators in the United States, European Union, and Russia are treating data centers as strategic infrastructure requiring layered defenses that combine physical hardening, geographic distribution, and strict cybersecurity controls. The United States has launched the Cyberstrategy for America 2026 emphasizing offensive operations, Zero Trust modernization, and supply-chain restrictions. The European Union is implementing ProtectEU and the Cyber Solidarity Act with real-time threat sharing and mandatory resilience standards under DORA. Russia is advancing technological sovereignty targets, new siting rules for data centers, and Presidential Decree No. 604 that enables temporary state management of inadequately protected critical facilities. The report also notes growing recognition that attacks on data centers can constitute acts of aggression under the Tallinn Manual.
US Department of Homeland Security Orders Federal Agencies to Remove DeepSeek Products
The US Department of Homeland Security issued an order on October 19 requiring federal civilian agencies to cease purchasing products from DeepSeek and to remove related technology from government systems. The directive, published the following day, targets Hangzhou DeepSeek Artificial Intelligence, its affiliates, and any third-party products or services built on DeepSeek implementations. The measure stems from the Federal Acquisition Supply Chain Security Act of 2018 and follows a recommendation by the Federal Acquisition Security Council, though no specific incidents or evidence were detailed in the notice. The restriction applies only to federal environments and does not prohibit private sector or individual use outside government systems. No removal deadline was set, and the document does not name the signing authority. The order is filed under docket DHS-2026-0628 with the CISA implementation team listed as the contact point.
AKIT Requests Temporary Permission for Russian Companies to Transfer Personal Data Abroad After Data Center Incidents
The Association of Internet Trade Companies (AKIT) has sent a formal letter to Russian Prime Minister Mikhail Mishustin proposing a temporary exemption from strict data localization rules. The measure would allow affected companies to move critical systems and Russian citizens' personal data to data centers in friendly countries when domestic infrastructure is unavailable due to accidents or damage. Members including Ozon, Wildberries, Cooper, and Yandex Market argue that services must continue operating even if Russian facilities are compromised. The proposed special regime would apply only after an officially confirmed incident, require compliance with information security standards, and end no later than March 1, 2028. After recovery, companies would be required to return to normal data processing within Russia. Expert Alexey Muntyan noted that the mechanism activates only after incidents occur and questioned whether countries should be selected based on data protection levels rather than political alignment.
Anthropic Model Reconstructs NSA Seeds for NIST Elliptic Curves in Under 30 Minutes
An internal Anthropic research model traced the origins of the five seeds used by the NSA to generate the NIST elliptic curves P-192, P-224, P-256, P-384, and P-521. The discovery resolves a 25-year-old question that arose when the curves were standardized in FIPS 186-2 for ECDSA in 2000. Researchers combined analysis of 1990s random number generators, 34 generator-output combinations, and lattice reduction techniques to identify lrand48 initialized with Unix timestamps from May 1997 to April 1998. The P-256 seed corresponds to the 1842nd candidate from a run started on 16 August 1997, and example seeds from ANSI X9.62 follow the same pattern. The work does not demonstrate any cryptographic break or backdoor in the curves and does not recommend changes to production systems. Several questions remain open, including the seed for curve B-163 and the reason certain candidate values were discarded.