HabrJuly 23, 2026🇷🇺Translated from Russian

AI in Cybersecurity: Where It Delivers Real Value and Where It Remains Marketing Hype

The cybersecurity industry faces a severe talent shortage, making it increasingly difficult to hire experienced SOC analysts, incident responders, and threat hunters. At the same time, businesses seek greater efficiency and lower costs, while vendors promote their products as highly innovative. These pressures create unrealistic expectations that simply purchasing an AI-labeled solution will resolve major security problems.

What Counts as AI in Information Security Today

Vendors often blur distinctions between technologies by labeling everything as AI. Classical correlation rules in SIEM systems trigger on predefined conditions, such as a user logging in at night, gaining administrative rights, and exfiltrating data. These contain no artificial intelligence, only engineering. Machine learning systems build behavioral models from historical data and flag deviations, yet they require extensive calibration and still produce high volumes of false positives. Generative AI and large language models can draft queries, summarize incidents, and explain detection rules, but they lack business context.

Where Marketing Claims Outpace Reality

One common promise is that AI will automatically discover unknown attacks. Solutions such as UEBA, NDR, and XDR do detect anomalies, for example when an accountant suddenly accesses servers via VPN at 3 a.m. and runs PowerShell. However, the system identifies deviation, not confirmed malice, so analysts must still validate each alert. Another claim is fully automatic investigation of complex incidents. While tools can assemble timelines, they cannot assess which systems are business-critical or predict operational impact without human input.

Assertions that AI will replace SOC analysts also fall short. Modern platforms can group events, suppress some false positives, and generate report drafts, yet they cannot answer questions about client impact, backup availability, or financial consequences. Similarly, generative models can produce plausible security strategies, but they ignore budget limits, corporate culture, and specific regulatory constraints, resulting in generic templates rather than actionable plans.

Areas Where AI Delivers Measurable Value

In anti-fraud systems used by financial institutions such as Alfa-Bank, machine learning has moved beyond simple threshold rules. Modern models analyze click patterns, typing speed, device behavior, and transaction context simultaneously. They can block a transaction made by a pensioner in one city minutes after a high-value purchase from a newly installed app in another country. Behavioral analytics platforms also excel at spotting insider threats by comparing current activity against an individual’s historical profile.

Generative AI assists analysts by translating complex detection logic into plain language and automatically building queries against large datasets. Correlation engines in contemporary SIEM and XDR platforms process millions of daily events and surface relationships spanning days or weeks that no human could review manually.

How to Separate Real AI from Marketing Labels

Organizations should demand concrete metrics from vendors, including false-positive rates, time required to validate each alert, and the percentage of incidents actually detected. Understanding which underlying technology—rules, machine learning, or generative models—is being used remains essential before committing significant budgets to solutions that may deliver only conventional correlation under a new label.

Related articles

BoletimSecAI Security

AgentForger Vulnerability in ChatGPT Workspace Agents Enabled Malicious AI Deployment via Single Phishing Link

A vulnerability in ChatGPT Workspace Agents allowed attackers to create and deploy a malicious AI agent inside an organization from a single phishing link. Named AgentForger, the flaw was fixed by OpenAI on June 8, 2026. The attack exploited a permissive parameter in the Agent Builder that accepted instructions directly through the URL. An authenticated user opening the prepared link would trigger automatic execution of the command without additional confirmation. The victim required access to Workspace Agents and at least one pre-authorized enterprise connector such as Outlook, Gmail, Google Drive, Slack, Teams, or Google Calendar. The malicious prompt instructed the platform to create an agent, connect available applications, disable approval requests, publish the component, and schedule it for recurring operation. In the demonstration, the agent monitored emails from the attacker with subjects starting with “TASK” and executed the contained instructions while returning results to the attacker-controlled address.

安全客AI Security

AI Coding Tools Under Fire: Grok Build Uploads Entire Git Histories, Claude Code Suspected of Silent Transfers

Security researcher cereblab uncovered that Grok Build 0.2.93 establishes separate HTTPS channels to exfiltrate full Git repositories, resulting in a 27800-fold traffic discrepancy between task context and storage uploads to Google Cloud Storage buckets. The tool ignores user instructions such as "do not read" and decouples the improve_model_enabled client switch from the server-controlled trace_upload_enabled flag, allowing continued uploads even when privacy settings are disabled. Similar concerns emerged around Claude Code, which maintains undisclosed WebSocket connections that transmit file paths, dependency trees, and code metadata without user awareness or audit logs. Comparative traffic audits showed that Codex and Gemini produced no anomalous outbound activity, while Grok Build and Claude Code were the only tools confirmed to perform data transfers beyond user authorization. The incidents highlight systemic issues including server-side remote control of client behavior, lack of third-party audits for closed-source binaries, and the conflict between model training data needs and user data sovereignty. Experts recommend zero-trust measures such as network blocking, Docker sandboxing without mounting .git directories, git filter-repo sanitization, and preference for auditable open-source alternatives like Continue.dev or locally deployed Ollama models.

安全客AI Security

PentesterFlow Launches Open-Source AI CLI Tool for Penetration Testers and Bug Bounty Hunters

PentesterFlow is a new open-source, human-in-the-loop AI command-line tool designed specifically for penetration testers and bug bounty hunters. It automates the full workflow from reconnaissance to report generation while requiring explicit analyst approval before executing sensitive commands. The tool addresses common issues in agentic AI security tools such as hallucinations, weak context retention, and poor tool integration by incorporating built-in pentesting skills and evidence-based vulnerability confirmation. It supports connections to local or hosted LLMs including Ollama, Gemini, Groq, and others, and features continuous local learning that stores user preferences and lessons without retraining models. A key differentiator is its integration with Burp Suite and a permission-based execution model that includes a YOLO mode for isolated environments. The project positions itself as a transparent alternative to fully autonomous tools like PentAGI and PentestGPT.

SecuritylabAI Security

Optimizing Cybersecurity Content for LLMs: How Sites Can Enter Generative AI Answers

Search engines and AI services like ChatGPT, Gemini, Perplexity, Copilot and Google AI Overviews increasingly deliver synthesized answers instead of link lists. For cybersecurity publishers this changes competition because high traditional rankings no longer guarantee visibility or accurate citation. The article explains GEO, AEO and LLMO practices, shows how material moves through indexing, fragment selection and summarization stages, and stresses the need for self-contained facts that survive extraction and paraphrasing. It provides concrete writing frameworks for vulnerability reports, including required fields such as CVE identifiers, affected versions, attack conditions and real-world exploitation evidence. Technical requirements cover correct robots.txt handling for Googlebot, OAI-SearchBot, GPTBot and Bingbot plus the use of IndexNow for rapid updates. The piece also warns about poisoning risks, prompt injection and slopsquatting attacks that can feed false data into generative systems.