Securitylab•August 4, 2026•🇷🇺Translated from Russian

Security Vision SIEM Tackles Alert Overload with Data Quality Monitoring and MITRE ATT&CK Coverage

In November 2013, a FireEye system costing 1.6 million dollars performed exactly as promised. It detected malware on Target point-of-sale terminals, generated multiple consecutive alerts, and even revealed intermediate servers receiving stolen data. The Bangalore shift noticed the signal and escalated it to Minneapolis, yet nothing further happened.

One month later the company disclosed the theft of 40 million payment cards and personal data of another 70 million people, with direct costs exceeding 200 million dollars. The automatic malware removal function had been manually disabled. Technology worked; process did not.

Since then much has changed, except the core issue. According to Vectra AI data for 2026, organizations receive an average of 2,992 alerts per day, and 63 percent of them remain uninvestigated. The Microsoft and Omdia SOC report adds further detail: 46 percent of alerts prove false positives. In the SANS 2025 survey, 73 percent of teams named false positives the primary detection problem. Analysts simultaneously juggle an average of 10.9 consoles.

Collecting logs is inexpensive and straightforward. Turning those logs into a managed process that reveals data quality, detection quality, and the full incident path is considerably harder.

What Security Vision SIEM Can Do

The product, built on the Russian Security Vision 5 Low-Code/No-Code platform, combines event collection and normalization, data quality control, attack detection, investigation, and basic response actions. Customers receive not an empty box with a promise to configure it themselves, but ready SOC expertise: more than 1,200 correlation rules, coverage of over 70 percent of MITRE ATT&CK techniques, mapping to FSTEC BDU threat implementation methods, and incident handling recommendations.

The July 2026 update introduced monitoring of collection stability and rule performance, SOC analyst SLA control, statistical anomaly detection, rule testing, Sigma rule exchange, and retrospective process chain reconstruction inside incidents.

Three Levels Where Everything Can Break

SIEM effectiveness rests on data completeness, detection quality, and response speed. Failure at any level nullifies the other two.

  • Level one: The SOC must be confident that required events actually arrive. Agents stop, administrators change logging settings for unrelated reasons, or hosts behind WEC or syslog aggregators silently drop out while the aggregator reports healthy status.
  • Level two: Detection rules must reflect real attack scenarios, infrastructure specifics, and temporal event relationships. Simple signatures rarely catch multi-stage attacks when events from different sources arrive delayed and interleaved.
  • Level three: Detection is only the start. Analysts must assess asset criticality, examine processes, accounts, network connections, lateral movement, confirm the incident, and act. Each manual tool switch adds minutes that accumulate into the 200 million dollar losses seen at Target.

Security Vision SIEM unites the entire chain: connect sources, verify data quality, detect suspicious activity, reconstruct attack context, and move to response.

Related articles

Securitylab•Other

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.

Habr•Other

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.

AntiMalware•Other

Russian Organizations Allocate 4.5 Trillion Rubles to Innovation Spending in 2025

Large and medium-sized Russian organizations directed a total of 4.5 trillion rubles toward innovation activities during 2025. Nearly half of the expenditure originated from the services sector, while information technology and telecommunications accounted for 860.9 billion rubles. The Institute for Statistical Studies and Economics of Knowledge at HSE University published the figures based on Rosstat data, showing an innovation intensity rate of 2.7 percent. Services companies alone contributed approximately 2.3 trillion rubles, including 882.7 billion rubles for research and development. Astra Group IR Director Vladislav Anshakov outlined major spending areas such as product development, cloud and AI hardware, and acquisitions of technologies and teams. The group expanded its portfolio with the Perseus DBMS and a 26 percent stake in AI developer AIB. More than one-third of organizations cited high costs and insufficient internal funds as key barriers to further innovation.

AntiMalware•Other

Telegram macOS Developer Says 99.9% of Client Code Is Now Written by AI and Suggests Firing Manual Coders

Mike, the developer of the official Telegram client for macOS, stated that artificial intelligence now generates 99.9 percent of the messenger's client code. He argued that programmers who continue writing code manually should be dismissed. In a Telegram discussion, Mike cited the gram.org website as an example created entirely with AI assistance in a single day, with domain support from Pavel Durov. He also described adapting the iOS client for a foldable iPhone Duo overnight using Claude. According to Mike, even designers are now contributing to client code, and 80 to 90 percent of Telegram developers share his positive view of AI tools. When participants raised questions about code quality and security, Mike replied that AI also identifies and fixes vulnerabilities, claiming the resulting code is superior to human-written equivalents. He further announced plans to open a new GitHub repository for the macOS client source code, as the previous repository had not been updated for over a year.