Yandex Builds Secure KVM Access for BareMetal Servers with IPMI Proxy and Network Isolation
Yandex BareMetal engineers have published a detailed account of how they enabled external customers to use KVM over IPMI without exposing the management network to the kinds of attacks that previously compromised an internal cloud of 25,000 hosts.
The service must deliver two critical capabilities: installation of custom operating systems and recovery when network settings are misconfigured. Both require remote console and virtual media access that legacy BMC firmware only provides through proprietary protocols, often Java Web Start applications signed with outdated hashes such as md4.
To unify access, the team created IPMI Proxy. Each user session launches a lightweight Docker container containing only the components required for a given hardware platform: an XWindow system, a VNC server, a legacy Java runtime with relaxed security settings, Firefox for HTML5 KVM, and optional Java applications for ISO mounting. The container converts the vendor-specific protocol into standard VNC, which noVNC then renders inside the Yandex Cloud console.
Because many BMCs speak only IPv4 while Yandex infrastructure uses IPv6, the team deployed IPMI Router servers running the jool kernel module for stateless NAT64 translation. Each IPv4 address is mapped to a predictable IPv6 address by preserving the last three octets, allowing DHCP to remain stateless and eliminating the need to synchronize lease databases during VRRP failover.
Security controls were added at every layer. Switch ACLs forward frames only toward IPMI Router MAC addresses. 802.1X authentication prevents MAC spoofing. An eBPF program on the routers drops any packet whose IPv4 address does not match the expected MAC, blocking ARP poisoning. Inside the proxy containers, network rules enforced by ip6tables restrict outbound connections to the single authorized BMC.
ISO images stored in S3 are mounted from outside the container as volumes rather than granting the container direct S3 access. Permission checks performed every ten seconds through the Yandex Cloud IAM model ensure that only users with current server-management rights can maintain an active KVM session.
The resulting architecture normalizes KVM and virtual media across heterogeneous hardware while keeping the IPMI fabric isolated from both external attackers and compromised neighboring servers.
Related articles
Amazon Confirms Irrecoverable Data Loss in UAE and Bahrain Data Centers After Drone Attacks
Amazon Web Services has officially confirmed that data stored in specific availability zones within its Middle East regions was permanently destroyed following physical attacks on data centers in the UAE and Bahrain. The incidents began on March 1 and continued through April and July, damaging infrastructure tied to AI development projects. In the UAE region mec1, only zone mec1-az2 was completely destroyed with no external backups, while mec1-az3 suffered severe damage and mec1-az1 remained operational but overloaded. All three zones in the Bahrain region me-south-1 were rendered inoperable. AWS had spent six months attempting recovery before issuing the final statement on September 15, 2026, and has advised customers to migrate workloads to unaffected regions. The event highlights growing risks to data from physical-world attacks beyond traditional network threats.
Bots Overload OT Commerce Store on OT Box, Spike Paid OTAPI Calls Mistaken for DDoS Attack
An online store running OT Commerce experienced CPU loads reaching 98-100% and a 6-7x increase in paid OTAPI calls over three days due to automated bot traffic rather than a traditional DDoS. The site owner had already deployed a paid anti-bot module on the VPS, yet behavioral bots continued to bypass protections and force expensive calls to the external OTAPI platform for product data from Taobao, Tmall, 1688 and other marketplaces. Traffic analysis after switching to the CRONARMOR WAF revealed that 41.9% of page requests were automated, with 99.3% of early-stage automation blocked before reaching the origin server. Only 0.5% were behavioral bots visible in analytics, while legitimate search crawlers accounted for 27,190 requests that were explicitly allowed. The WAF approach stopped requests at the reverse proxy layer, preventing PHP execution, database queries and OTAPI billing events on the origin. Post-deployment CPU dropped to single digits for most of the day, eliminating both performance issues and the anomalous rise in paid API usage.
Teenage Smartphone Addiction: Causes, Consequences, and Treatment Approaches
Smartphone use has become an integral part of adolescent life, but problematic usage patterns rather than device ownership itself are the focus of concern. Medical experts avoid the term smartphone addiction and instead address issues like disrupted self-control, social media overuse, and gaming disorder that interfere with sleep, studies, relationships, and mental health. Data from Pew Research indicates nearly 50% of U.S. teens aged 13-17 are online almost constantly, while CDC findings link four or more hours of daily screen time to elevated anxiety and depression symptoms. Family digital habits strongly influence teen behavior, and rigid bans often fail without addressing underlying issues such as boredom, anxiety, or social isolation. Parents are advised to track specific disruptions over a week and consider professional help when signs of depression, bullying, or self-harm appear alongside device overuse.
VK WorkSpace Federation Enables Secure Multi-Organization On-Premise Messaging Without Infrastructure Merge
VK Tech has released federation capabilities for its VK WorkSpace corporate messenger that connect independent On-Premise installations while preserving each organization's full control over data, administration, and security policies. The feature, first piloted in November 2025 and expanded in the July 2026 26.2 release, supports multi-party chats across more than two separate environments. Federation relies on mutual trust establishment and per-user access grants rather than full directory replication or proxy access to a single host instance. Each participating organization maintains local copies of messages, files, and chat metadata, allowing continued access even if a partner installation becomes unavailable. The architecture deliberately avoids both centralized hosting and open protocols such as Matrix to keep changes to the existing messenger core minimal. Administrators retain independent levers to create or revoke trusts and to limit which employees may communicate externally.