K2 Cloud Adds Native OVN Traffic Mirroring for NTA/NDR Deployment in Public Cloud
K2 Cloud has become the first Russian public cloud to support native traffic mirroring from virtual-machine interfaces for NTA/NDR systems. The implementation was achieved by extending OVN overlay-network capabilities and contributing the changes upstream, where the patch was accepted into the main code base.
Why cloud traffic visibility was missing
Until this development, no Russian public cloud offered the ability to mirror VM traffic. PT Network Attack Discovery (PT NAD) from Positive Technologies and similar tools require an exact copy of network packets to perform signature analysis, indicator-of-compromise checks, sandbox integration, and behavioral anomaly detection. Without this copy the systems cannot function.
How the mirroring works
Mirroring is performed after the packet has passed the load balancer and cloud firewall for inbound traffic, and immediately after the VM for outbound traffic. The original packet continues to its destination while an identical copy is sent to the designated PT NAD sensor. The feature operates across any project networks, including different VPCs, and mirrors exactly the same traffic that would be seen by tcpdump inside the VM.
Filters solve duplicate, one-sided, and elephant-flow problems
- Inbound filter rules drop traffic originating from other VMs inside the same VPC to prevent duplicate packets from reaching the sensor.
- Outbound rules explicitly allow traffic to the default gateway so that DNS and DHCP sessions remain complete.
- Heavy but legitimate flows such as backups can be excluded by IP, port, and protocol to reduce sensor load.
Filters are applied only to the cloned packets and have no effect on the original traffic.
Operational constraints and performance
Mirroring is limited to a single availability zone; each additional zone requires its own PT NAD instance. Load testing conducted jointly with Positive Technologies demonstrated more than 3 Gbit/s of mirrored HTTP traffic, roughly 400 000 packets per second, and 30 000 HTTP transactions per second with negligible packet loss. The official PT NAD rating is 2 Gbit/s; higher rates are achievable with multiqueue configuration on the capture interface.
Deployment notes
Administrators must remove the automatically assigned IP address from the capture interface by uninstalling the c2-ec2-netutils package, otherwise the DPDK-based sensor will not start. Disk IOPS should be monitored when raw traffic storage is enabled. All resources—sources, destinations, sessions, and filters—can be managed through the web console, the EC2-compatible API, or the K2 Cloud Terraform provider.
Related articles
OpenAI Releases GPT-6.1 Terra: Cost-Effective Model Focused on Computer Control, Image Analysis and Practical Automation
OpenAI has launched GPT-6.1 Terra, a new model positioned between its high-end GPT-6 Astra and more affordable options in the GPT-6 family. The model emphasizes real-world computer interaction, visual understanding of documents and interfaces, and reduced error rates rather than raw reasoning benchmarks. It supports a 1.05 million token context window, image inputs, and tool use through the Responses API while cutting input token prices by half compared with its predecessor. Published benchmarks show substantial gains on Terminal-Bench 4.0, OSWorld 2.1 and Agents' Last Exam, with error rates dropping sharply at both low and maximum reasoning levels. OpenAI stresses that the model still requires human oversight for high-stakes actions and does not directly process audio or video. The release targets developers and enterprises seeking reliable automation of repetitive multi-step tasks at lower cost than flagship models.
Yandex Black October: How Architectural Flaws and Capacity Mismanagement Turned Data Center Losses Into a 11-Day Fintech Coma
In October 2026 three Yandex data centers in Central Russia were physically destroyed within days, triggering the collapse of Yandex Cloud and multiple core services. Between the first and third site failures engineers had 74 hours to restore quorum and rebalance workloads yet failed to do so because Control Plane components remained tied to the lost zone and spare capacity had been eliminated to cut costs. Core banking and BNPL systems entered Read-Only mode after losing quorum, forcing a complete stop-the-world reconciliation that lasted until 22 October. Backups stored inside the same regional S3 buckets proved unusable, resulting in a seven-day RPO and primary-key collisions after restoration. The incident exposed that Metro-Cluster designs had been incorrectly treated as full Disaster Recovery and that aggressive AP microservice patterns created logical split-brain conditions outside the database layer.
Astra Group Releases Low-Code Astra AI Platform for Building Corporate AI Agents in Closed Environments
Astra Group has launched the Astra AI Platform, a low-code constructor designed for creating corporate AI applications that operate entirely within closed circuits without reliance on foreign clouds. The platform targets small and medium businesses as well as large corporations, enabling rapid deployment of AI secretaries, technical support assistants, and other agents in days rather than months. It forms part of the broader Astra AI ecosystem and includes two main constructors: one for machine learning model training and deployment, and another for LLM-based language assistants, document search, and process automation. Users can assemble scenarios from visual blocks, debug them in real time, or extend functionality with custom Python code when needed. The solution supports RAG-based knowledge bases, integration with external tools such as CRM and ERP systems, and the coordination of multiple agents for distributed task handling. One demonstrated use case involves processing ten pages of engineering drawings and specifications in five minutes to prepare data for downstream systems. The product is already listed in the Russian domestic software registry and available to customers.
Multi-Tenancy Isolation in VictoriaMetrics, VictoriaLogs and Grafana: Building Client Separation in a Shared Stack
Voltir runs a single shared monitoring stack consisting of VictoriaMetrics, VictoriaLogs, Grafana and vmalert for all customers instead of deploying separate instances per tenant. Isolation relies on numeric account IDs enforced at every layer: nginx validates tokens against the platform API before proxying writes, Grafana data sources hard-code tenant accounts, and vmalert rules receive automatic account filters. The team discovered that a single malformed rule or template could break alerting for every tenant because vmalert loads the entire rules directory at once. They also found that Grafana automatically created personal organizations granting Org Admin rights, accumulating hundreds of orphaned organizations and users that consumed disk space and resources. A dedicated cleanup module plus hourly reconciliation now removes rules, organizations, series and users when a tenant is deleted, while isolation tests verify both data and API objects across tenants.