Why Defending a Company Costs Millions While Attacks Can Succeed for Just Hundreds of Dollars
In the 26th episode of Belyaev Podcast, two experienced CISOs examined a question every security leader eventually faces: how to explain to business stakeholders exactly what they are paying for when investing in information security.
Vyacheslav Kasimov, CISO of Tochka Bank, and Boris Evdokimov, Director of Information Security at the ASNA pharmacy network, highlighted a fundamental imbalance. Attackers can often launch campaigns using relatively inexpensive cloud computing, automation tools, and anonymization services, while organizations must spend millions on layered defenses, continuous monitoring, and incident response capabilities.
The discussion emphasized that security value cannot be measured by the number of security products purchased or the lack of public breach announcements. Instead, it should be evaluated through the lens of critical business processes, potential impact, probability of realization, and the organization’s ability to continue operations after an incident.
Kasimov noted that the absence of known leaks can be misleading. Undetected compromises, unconnected signals, or data already sold on closed channels may exist without the company’s awareness. Evdokimov added that organizations need systematic monitoring of public and underground sources to detect early signs of exposure.
Both experts stressed that mature security programs require clear answers to several practical questions: which assets are most critical, who has access to them, what indicators of compromise can be detected, and how the company will respond in the first hours after confirmation of an incident.
The conversation also addressed the common perception of security as a business obstacle. When security teams only block initiatives without offering safe implementation paths, they risk being bypassed. The recommended approach is to present risk scenarios, compensating controls, their costs, and the remaining residual risk so business leaders can make informed decisions.
Regarding emerging technologies, the speakers discussed the responsible integration of artificial intelligence into security operations. Automation can accelerate initial triage and response, yet models must be tested, access rights limited, actions logged, and irreversible decisions kept under human control. Any AI system granted infrastructure access becomes part of the attack surface and requires ongoing validation.
In closing, the participants agreed that the most damaging consequence of a security incident is often the long-term loss of customer trust, which can result not only from the breach itself but also from inadequate communication or lack of a clear recovery plan.
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.