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

Habr•Other

How a Personal Site Counts Bots Without Storing Any IPs: Pure PHP, No Database, Strict CSP and 160 Tests

A personal website built entirely in pure PHP without frameworks or databases demonstrates advanced defensive security practices while tracking bot activity from an SSH honeypot. The site stores all content in a single JSON file with atomic writes and automatic backups, eliminating database-related attack surfaces and simplifying deployment to folder copying. Strict Content-Security-Policy rules prohibit inline styles and scripts without nonces, forcing the use of SVG attributes, CSSOM updates, and JSON data blocks instead of direct attribute injection. Over 160 automated tests written in PHP attack the site with XSS payloads, CSRF attempts, path traversals, and malformed Markdown to verify that no malicious output reaches the browser. Bot identification relies on behavioral signatures derived from the first twelve cleaned commands of each session, combined with HASSH fingerprints and activity patterns, allowing the site to report unique bot families and address counts without ever publishing IPs. Additional browser-based tests using Chromium validate accessibility, performance budgets, and CSP compliance across desktop and mobile viewports. The entire system runs with zero external dependencies and integrates tests directly into the deployment pipeline.

AntiMalware•Other

Russian Finance Ministry Seeks Central Bank Reports on Systematic P2P Transfers to Tax Authorities

The Russian Ministry of Finance has proposed amendments requiring the Central Bank to share data with the Federal Tax Service on individuals whose bank accounts show signs of regular income received from other private citizens. The changes target article 85 of the Tax Code and form part of the budget package bill numbered 617-9. Under the new rules, the Central Bank would identify such citizens through transaction analysis and transmit the information according to a future agreement with the tax service. The Federal Tax Service would also gain expanded powers to request bank statements from non-entrepreneurs without needing prior debt collection or audit triggers. If approved, the provisions would take effect on 1 January 2027 and apply to operations conducted after 1 January 2026. Separate bills under discussion would impose monthly transfer limits of 30,000 rubles on suspected clients starting in 2028 and require the tax service to notify the Central Bank about account openings and income categories.

安全客•Other

Baidu Launches Ciyuan Exchange to Establish Trust Standards for AI Model Trading

Baidu Intelligent Cloud has introduced the Ciyuan Exchange, a dedicated trading platform for large AI models that aims to solve quality verification and credit issues in an increasingly crowded market. The platform, unveiled at the Baidu World 2026 Conference, already hosts over 100 supply resources with daily calls exceeding 50 million and daily token usage surpassing 700 billion. Founder Li Yanhong positioned the exchange as an infrastructure layer that moves beyond simple model aggregation toward verifiable identity, ongoing performance monitoring, and supplier credit records. The initiative addresses real procurement risks where identical models from different providers show up to twofold differences in throughput and reliability, according to a China Academy of Information and Communications Technology report. By combining model fingerprinting, capability testing, periodic audits, and continuous credit scoring, the platform seeks to create transparent market mechanisms similar to commodity exchanges. This development signals a broader industry shift from raw model capability competition toward standardized service quality, pricing transparency, and reliable delivery infrastructure.

Habr•Other

Windows and MacBook Pro Setup Combines Local Network Access with Dual VPNs and Kill Switch Protection

A user detailed how they integrated an older MacBook Pro into an existing Windows workstation environment while preserving separate user accounts, file sharing, and independent VPN connections. The setup required careful routing configuration to keep the Kill Switch active on both Amnezia VLESS and AmneziaWG without breaking local SMB connectivity. After initial failures caused by the Windows Kill Switch blocking the 192.168.1.0/24 subnet, split tunneling was implemented to route local traffic directly. Separate macOS accounts were created for daily use and a dedicated “Serverok” account for remote scripting and compute tasks. SSH and SFTP ultimately replaced problematic SMB shares for the secondary account, enabling reliable file transfers at over 50 MB/s. The configuration allows simultaneous or sequential use of both machines while maintaining strong VPN protection on each.