Russian Data Centers Above 500 kW May Receive Protection from Forced Relocation Under Gilotina 2.0 Roadmap
Land plots containing large data centers may receive special protection against compulsory seizure for state and municipal needs. The proposal has been included in the draft roadmap Gilotina 2.0 for the data center sector.
The ban is planned to come into force on 15 December 2027. Facilities with capacity of 500 kW and above that are entered in the Russian registry of data centers would fall under the protection, according to information obtained by Vedomosti.
The amendments are intended to prevent the demolition of an operating facility for the sake of comprehensive territory development. A data center cannot simply be disassembled in the evening and moved to a neighboring plot.
The Association of Data Center Industry Participants considers the 500 kW threshold unjustified, pointing out that no standardized method yet exists to separate IT load from total electrical capacity. The association also criticizes the linkage to the registry, noting that participation remains voluntary and therefore protection may not cover all facilities.
The Coordination Council of Data Centers supports the threshold, arguing that guarantees should primarily cover large and difficult-to-replace sites. Should land release still prove necessary, the initiator of new construction would be required to provide an equivalent plot or finance its creation.
Compensation would extend beyond walls and server racks. Reimbursement is proposed to include construction of a new data center, relocation of equipment and IT load, reservation of power capacities, laying of communication lines and power grids, as well as losses arising from early termination of client contracts.
The initiative has received support from RTK-COD, MTS, and Megafon, although the operators also oppose mandatory registry linkage. The issue is especially acute in Moscow, where local data centers operate at approximately 95 percent capacity and free power resources are nearly exhausted, forcing new sites to be built in the regions.
Related articles
How to Prepare Your Website for Data Center Outages: Business Resilience Checklist
Following strikes on Yandex data centers, many businesses discovered that their sites and all backups were stored in a single location, leading to complete outages. The article provides a detailed checklist to mitigate such risks by separating critical components across different providers. Key recommendations include moving DNS to an independent provider, lowering TTL values, maintaining a live mirror site on separate hosting, and isolating corporate email. Additional steps cover local backups, monitoring, access management, and CDN usage. The guidance differentiates between virtual hosting, VPS or dedicated servers, and website builders like Tilda, while emphasizing compliance with Russian data localization laws such as 152-FZ.
How to Properly Compare CDNs: TTFB, p95 Latency, Caching, DDoS Protection and True Pricing
Selecting a CDN based solely on the number of points of presence is as unreliable as choosing a car by dashboard buttons. Networks with dozens of global PoPs may underperform for audiences concentrated in Novosibirsk or Yekaterinburg, while smaller regional providers often deliver superior peering with Russian operators. The article evaluates CDNVideo, EdgeCenter, Curator, NGENIX and Yandex Cloud CDN across verifiable features, network design, caching behavior, security controls, operations and commercial models. Performance data is separated because marketing claims cannot substitute for independent measurements from services such as CDNMON. Emphasis is placed on p95 metrics, cache hit ratios, origin shielding, raw logs and API limits rather than marketing scores. The analysis shows that no single universal ranking exists; optimal choice depends on traffic profile, audience geography, security requirements and operational workflows.
Innostage Lab Benchmarks PT NGFW 1.10.3 Performance in Eight Load Scenarios
Innostage researchers conducted extensive performance testing of PT NGFW version 1.10.3, the certified release at the time of trials. The evaluation covered TCP connection setup rates, concurrent session capacity, and throughput on a custom EMIX traffic profile with varying security modules enabled. Tests used Cisco TRex generators and a high-rule-count policy of 100,000 entries to simulate realistic enterprise conditions. Results showed the device sustaining 700,000 CPS and 6.4 million concurrent connections, matching or approaching vendor claims under HA-cluster configuration. Throughput remained above 27 Gbps even with IPS, application control, antivirus, NAT, URL filtering, and logging active. The report highlights differences in test methodology compared with vendor figures, including packet sizes and clustering setup.
Java Card Tutorial: Implementing Supplementary Security Domain to Limit ISD Privileges
A detailed technical guide demonstrates how to create a Supplementary Security Domain (SSD) on Java Card platforms to isolate applet management from the Issuer Security Domain (ISD). The approach prevents full card compromise if ISD keys are exposed by restricting SSD privileges to specific functions such as accepting extradition only from the ISD. Using the FunGP library and SCP02 protocol, the tutorial walks through installation, personalization with encrypted keys, and extradition of applets under the new domain. GlobalPlatform specifications including GP CS v2.3 and GP CIC v2.0 are followed for install parameters, privileges, and STORE DATA commands. After personalization the SSD reaches the PERSONALIZED lifecycle state, allowing secure delegation of applet control while the ISD retains overall card management rights. The method eliminates the need for custom operating systems and provides a standards-compliant way to enforce least-privilege access on smart cards.