Russian Data Centers May Face Temporary State Management Under Decree 604 for Protection Shortfalls
Large Russian data centers may fall under the scope of presidential decree No. 604, which permits temporary state management of critical infrastructure facilities with insufficient protection. By default, Rosimushchestvo would assume the role of administrator.
The measure can be applied when an owner fails to fulfill security requirements, poses a threat to stable operations, inadequately protects the facility from drone attacks, or restores operations too slowly after an incident. The decree covers communications, energy, transport, industry, utilities, and other critical sectors.
Industry participants believe that major commercial and departmental data centers serving government bodies, banks, and federal operators clearly qualify. While Tier III and higher facilities usually maintain solid cyber defenses, the primary new expenses will involve physical security measures.
Operators must now protect generators, cooling systems, communication nodes, and other external engineering equipment against aerial threats. The challenge is especially acute in European Russia, where 80–90 percent of commercial data center capacity is concentrated in Moscow and St. Petersburg.
Protection against drones was not previously part of standard data center design. Some companies are already modernizing infrastructure. RTK-DC stated it continuously reviews security measures, while RUVDS confirmed work on safeguarding external equipment.
The market anticipates detailed sector-specific requirements tied to facility category and criticality. Experts highlight the need for redundant communication channels, DDoS protection, vulnerability management, and accelerated recovery processes. Additional protection will require significant capital expenditures that may ultimately be passed on to clients, particularly in government, financial, and telecommunications segments.
First Deputy Prime Minister Denis Manturov assured that no mass campaign or nationalization is planned; decisions will be made on a case-by-case basis at the highest level.
Related articles
I Know but Cannot Tell: The Forensic Expert's Struggle to Share Real Cases Under NDA Constraints
A cybersecurity journalist reflects on the inherent difficulties of writing about digital and financial forensics while bound by strict confidentiality agreements. The article explores how verifying financial documents involves far more than spotting Photoshop alterations, raising questions about data origin, accuracy, interpretation, and the validity of conclusions drawn by examiners. Automated verification systems often produce conflicting results because they assess different aspects of a document, yet lack transparent justification for their verdicts. Attempts to anonymize cases, obtain client consent, or use synthetic data each carry limitations that can still lead to identification or fail to demonstrate actual expertise. The author recounts collaborating with an AI to draft the piece, only to realize the meta-discussion about the inability to publish real cases itself became the only publishable story. Ultimately, the piece highlights the tension between the professional desire to share knowledge and the contractual and ethical barriers that prevent meaningful disclosure in the field of forensic analysis.
Three Hypotheses on Information Security Risk Assessment: Where Automation Truly Saves Time at Avito
Avito expert Irina Sozinova details how the company tested automation in its risk assessment process after scaling issues emerged with thousands of risks in the GRC system. The team formulated and piloted three hypotheses focused on automating typical risks, eliminating manual team preparation, and validating data to reduce InfoSec workload. Results showed a 16% drop in total risks registered, zero preparation time for teams, and improved coverage and context quality, though overall expert time savings were partially offset by new post-processing tasks. The pilot confirmed that automation works best on repeatable scenarios with stable data sources rather than promising immediate proportional time cuts. Avito plans to complete automation of context collection and finding classification this year to expand risk assessments across the company next year.
Integrating OAuth 2.0 with PDP Architectures Without Modifying Core Authorization Engines
The article explores how to combine OAuth 2.0 delegated access with traditional PEP/PDP authorization systems. It proposes an OAuth-aware PDP layer that translates access tokens into standard PDP checks while preserving the original PDP implementation. Three main use cases are analyzed: stored user grants, tenant-level administrative grants, and scopes carried directly inside tokens. The design relies on synthetic subjects such as u+c and t+c pairs, ephemeral policies for token-embedded scopes, and optional OAuth-aware PAP components. Special attention is given to token contents, policy storage via PAP, and the need for deterministic subject identifiers. The approach supports both classic scope models and structured RAR-style authorizations while maintaining separation between OAuth grants and subject permissions.
Russian Businesses Face 50-Ruble Fee per MVD Query for Passport and Residence Checks
The Russian government has backed a proposal requiring businesses to pay 50 rubles for each completed session querying Ministry of Internal Affairs databases. The fee covers checks on Russian passport validity, residence registration, residence permits, and foreign citizen migration records. Projected annual budget revenue reaches 120 billion rubles. Companies must still perform client identification under Federal Law 115-FZ and the Law on Communications, with fines up to 0.1 percent of own funds for banks or 500,000 rubles for telecom operators. Smart Engines highlights its Sherlock anti-fraud platform as a local alternative that detects over 600 forgery indicators, including deepfakes and NFC chip tampering, without repeated paid queries. The company cites a June 2026 legal opinion from the National Council of Financial Markets confirming that such tools can satisfy compliance requirements.