Securitylab•October 16, 2026•🇷🇺Translated from Russian

R-Vision SIEM Demonstrates Resilience During Intense Standoff 17 Cyber Defense Exercise

R-Vision SIEM served as the primary platform for monitoring, correlation, and incident investigation during the Standoff 17 cyber exercise, where the akPots blue team defended the Telecom sector under realistic high-pressure conditions.

Most participants encountered the system for the first time during the event. The exercise simulated nine critical events out of 37 architected scenarios while more than ten red-team groups operated simultaneously across the infrastructure. Unlike typical SOC operations that involve large volumes of failed scans and false positives, the competition produced a dense stream of successful exploits and high-severity alerts.

The team highlighted several operational differences from routine work. In everyday environments, targeted attacks unfold over extended periods and defenders can consult system owners. At Standoff, attribution proved difficult because multiple groups attacked concurrently, and no clarification from administrators was available. Initial access vectors were especially challenging to isolate amid heavy scanning noise.

Organization relied on three key practices. A shared chat contained dedicated threads for each critical event. A living document captured IOCs, artifacts, and evidence in chronological order, allowing any team member to regain context quickly. A designated captain distributed tasks and handled organizer communications.

Alongside R-Vision SIEM, the defenders used PT Application Firewall for request and response inspection, PT NAD for traffic analysis, PT Sandbox for malware evaluation, and PT Container Security for eBPF-based visibility inside Kubernetes clusters. The Xello deception service was also deployed. Interfaces proved intuitive, enabling the team to become comfortable within three hours, although complex queries still required occasional reference to documentation.

Most valuable SIEM capabilities included raw search with wildcards, adjustable display fields, event grouping, and exclusion of known benign activity. Pre-built dashboards helped surface attacker intent before critical events were achieved. The team noted that the system handled high data volumes stably and offered clear query syntax.

Requested improvements included one-click navigation from dashboard widgets to underlying raw events, ready-made detection scenarios based on vendor expertise, and nested grouping by host and event type. Overall, the exercise provided intensive hands-on experience with new tools and reinforced the value of structured team coordination under stress.

Related articles

Securitylab•Other

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.

Habr•Other

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.

AntiMalware•Other

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.

Habr•Other

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.