Russia Boosts Digitalization Budget by 58% Using Telecom Operators' Universal Service Fund
The Russian government plans to allocate 16.3 billion rubles in 2027 for digital solutions from the universal service reserve, which is 58% higher than the previously planned 10.3 billion rubles. This reserve is replenished by contributions from telecom operators, yet its spending extends well beyond rural internet connectivity.
According to Vedomosti, the additional funds are directed toward the national project Data Economy and the state program Information Society. For 2028, the proposed allocation rises to 18.6 billion rubles from the earlier figure of 11.1 billion rubles. The contribution rate from operators remains fixed at 2% of revenue, and MinTsifry has confirmed that any increase is not currently under discussion.
Separately, 19.3 billion rubles are still planned for universal communication services, including connecting small settlements and developing infrastructure, with no change to this amount. The extra digital funding will support state information systems, digital platforms, cloud infrastructure, artificial intelligence projects, and quantum technologies.
At the same time, financing for digitalization from additional revenues generated by traffic fines is proposed to drop from 34.3 billion rubles to 21.2 billion rubles in 2027. Analyst Vladimir Bespalov from Euler suggests the revision may reflect improved collection of contributions and is unlikely to have a significant impact on tariffs.
Related articles
Prod is Down: Free gVisor-Based Simulator Gives Strangers Root Access for Realistic Linux Incident Training
A Russian systems administrator has launched Prod is Down, a free online platform that lets users practice real incident response by granting them root consoles on deliberately broken Linux servers. The tool currently offers 13 scenarios covering PostgreSQL failures, OOM Killer events, full disks, expired certificates, nginx 502 errors, inode exhaustion, DNS issues, and open file limits. Each exercise runs inside gVisor sandboxes with strict resource limits, internal-only networking, and automated verification that checks service health rather than player commands. The author implemented an emulated systemd in Python so trainees can use familiar systemctl and journalctl commands without running a real init system. Multiple layers of isolation, including overlay filesystem tweaks and size monitoring, prevent abuse while still allowing sudo and realistic debugging. The platform records three random variants per scenario so memorized fixes from previous runs do not work on subsequent attempts.
Home Lab Guide: Deploying Active Directory, Windows 7 Client and ELK Stack for Security Logging
A detailed tutorial walks readers through building an isolated VirtualBox lab featuring a Windows Server 2019 domain controller with DNS and DHCP, a Windows 7 client joined to the domain, and an ELK stack running Elasticsearch, Logstash and Kibana 9.4.2. The guide covers creation of organizational units, Group Policy Objects for advanced auditing, and configuration of Winlogbeat 7.17 to forward Security, System and Application logs to Logstash. Special attention is given to common pitfalls such as missing GPO extension attributes that prevent audit policies from applying and memory constraints when running the full ELK stack on limited RAM. The author emphasizes that Windows 7 is unsupported and should only be used in isolated lab networks. All steps are provided with exact PowerShell commands, netplan configurations, and Logstash pipeline examples suitable for a 192.168.100.0/24 NAT network.
Building Your First Home Network Lab: Essential Tools and Experiments to Understand Corporate Networks
A cybersecurity professional without network knowledge resembles a guard without a building blueprint, spotting alarms but unable to trace the intruder. Setting up a personal lab on a standard computer bridges this gap through virtualization and hands-on practice with protocols and attacks. The guide recommends GNS3 for topology emulation, VirtualBox or VMware for running Windows and Linux workstations, Cisco Packet Tracer for quick simulations, Wireshark for traffic analysis, and draw.io for diagramming. Key experiments include configuring Cisco IOS routers with IP addressing, testing default gateways, observing ARP requests and replies, triggering broadcast storms via switch loops, and enabling STP to prevent loops. The lab demonstrates how legacy protocols like ARP expose networks to spoofing and why segmentation with VLANs and firewalls matters. Resources from CyberED provide demo access to courses on SOC analysis, penetration testing, and AI applications in security to extend learning.
PSLC and Agent-Ops: From Product Support to Infrastructure Transformation
Sergey Zhitinsky, founder of Git in Sky, attended the OPS Talk by Sber meetup on October 19 and discussed the PSLC methodology with architect Alexander Shapovalov. PSLC, or Product Service Lifecycle, outlines two loops for restoring services immediately and improving reliability to prevent recurrence through teams, knowledge, and platform support. Agent-Ops focuses on eight detailed steps for individual infrastructure tasks: intention, evidence collection, diagnostics, planning, approval, controlled change, verification, and lessons learned. The article illustrates their complementary use in a scenario where post-release log growth fills a database disk, requiring both service restoration and root-cause fixes. Both approaches emphasize knowledge retention, action control, and human accountability, though Agent-Ops v0.5.1 mandates explicit human approval and separate execution for production changes. PSLC suits larger organizations with shared platforms, while Agent-Ops targets smaller teams handling infrastructure operations with AI agents.