FSTEC Order 60 Expands Attestation Rules to Municipal Systems, Defense Industry and Personal Data Operators
Russian regulators have significantly widened the circle of organizations required to perform attestation of information systems starting 1 September 2026. The key document, FSTEC Order No. 60 of 27 February 2026, amends the earlier FSTEC Order No. 77 of 29 April 2021 and changes the very definition of entities covered by the attestation procedure.
The updated rules now explicitly apply to state and municipal information systems, including municipal personal data systems; industrial control systems at defense-industry organizations, including CNC machine tools; and protected premises used for confidential negotiations. The order also covers any information systems belonging to state bodies, state unitary enterprises or state institutions that are not formally classified as state systems, as well as critical information infrastructure objects, non-state personal data operators and industrial control systems at critically important or potentially hazardous facilities.
Two new articles introduce concrete control methods. Article 31¹ states that post-attestation monitoring must include vulnerability analysis and penetration testing. Article 16¹ makes penetration testing mandatory for state information systems and other systems of state bodies, unitary enterprises and institutions that have first or second protection class and are connected to the internet or interact with external systems, with the sole exception of encrypted VPN channels using certified cryptographic means.
Reporting deadlines have also changed. Article 32 now requires submission of control results to FSTEC at least once every three years and no later than five working days after completion of the control. Failure to meet the deadline can lead to suspension of the attestation certificate. Only organizations holding an FSTEC license that explicitly includes rights to conduct attestation tests and protection control against unauthorized access may perform the work.
A second document, FSB Order No. 297 of 6 August 2026, implements new incident-reporting obligations for every state institution under the amended Article 16 of Federal Law 149-FZ. Each school, hospital or other state-funded body must independently conclude an interaction regulation with NKTSKI, obtain a personal cabinet and transmit information about incidents within 24 hours. Three separate 24-hour clocks apply to incident reporting, confirmation of receipt and notification of preventive measures.
Finally, Government Decree No. 1024 allows the use of Russian-hosted cloud services for state systems provided the service meets or exceeds the required protection class, yet places full compliance responsibility on the heads of the user organizations. All three regulatory acts enter into force on 1 September 2026.
Related articles
Alfa-Bank Balances Cloud Trust and Zero Trust Models During Migration to Yandex Cloud
Alfa-Bank's head of container and cloud security, Sasha Chertok, detailed how the bank migrated regulated workloads to Yandex Cloud while preserving existing Zero Trust controls. The organization mapped on-premises network segmentation, Active Directory authentication, and firewall policies directly onto Yandex Cloud resources using interconnect links secured with GOST encryption. Responsibility for managed services is shared under a Cloud Trust model, yet the bank retains oversight through Terraform-managed Security Groups, custom CSPM checks, and internal CI/CD gates. User access continues to authenticate via on-premises Active Directory and KeyCloak federations, while authorization leverages granular Yandex Cloud IAM roles. Logging and detection rely on a combination of Yandex Cloud Audit Trail, Cloud Logging, and the YCDR service to compensate for incomplete control-plane visibility. The resulting hybrid architecture now supports 1,500 virtual machines, 100 managed services, and 1,000 identities across multiple environments without disrupting established security processes.
EnvSpec Naming Standard Introduces Strict Six-Environment Hierarchy for Zero Trust Infrastructure
The EnvSpec Naming 1.0.0 standard proposes replacing ad-hoc hostnames with a strict hierarchical naming system based on environment, perimeter, system, slot and node. It defines exactly six environments—dev, test, stage, prod, infrastructure and workplace—and treats any test or pilot system processing real data as prod. The model projects names into SPIFFE IDs, Kubernetes namespaces, cloud projects and mandatory tags for automated policy enforcement. Rules prohibit direct communication between different linear environments and require all access from workplace devices through dedicated gateways. The standard is published under CC BY-SA 4.0 and includes machine-checkable criteria for compliance.
Russian Woman Fined 30,000 Rubles and Loses iPhone 11 for Posting AI-Generated Bear Photo
A resident of Duldurga village in Zabaykalsky Krai was fined 30,000 rubles under part 9 of article 13.15 of the Russian Code of Administrative Offenses for publishing an AI-generated image of a bear presented as authentic. The court also ordered confiscation of her iPhone 11 as the instrument of the administrative violation. The woman knew the photograph was fake before posting it, yet the image spread widely online and was even shared by a local Ministry of Natural Resources channel on 10 September. Local authorities used the case to warn residents that publishing neural-network-generated fake images carries real legal consequences. The incident highlights ongoing enforcement of Russian legislation against the distribution of knowingly false socially significant information under the guise of credible reports. Meanwhile, wildlife specialists continue to investigate separate reports of actual bears near populated areas in the region.
Inserting Contracts into ChatGPT Risks Major Fines Under Russia's 152-FZ Personal Data Law
A detailed analysis examines the legal consequences of uploading contracts containing personal data into foreign AI services such as ChatGPT under Russian Federal Law 152-FZ. The article clarifies that even standard supply agreements include names, positions, passport details, INN numbers, phones and emails that qualify as personal data. It breaks down applicable administrative penalties from Article 13.11 of the Code of Administrative Offenses, including 150-300 thousand rubles for processing without a proper legal basis and separate fines for failing to notify Roskomnadzor. Cross-border transfer rules under Article 12 require a dedicated notification to the regulator before sending data to services hosted in the United States or European Union. The piece also reviews recent court practice, including a Moscow district court ruling that treated uploading commercial information to DeepSeek as disclosure of trade secrets. No criminal liability under Article 272.1 of the Criminal Code applies to ordinary business use, yet the absence of a data processing agreement with OpenAI or similar providers creates ongoing compliance exposure.