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
Why We Banned Our AI Manager from Writing Code and Assigned the Task to Claude Opus
The team behind an AI-powered marketplace manager for Wildberries initially built the system using regular updates, then migrated it to an autonomous agent. After implementing multiple layers of restrictions, they ultimately removed the agent entirely and rebuilt the solution from scratch. The new architecture relies on a single tool that handles the complete Wildberries API along with internet access while respecting all platform limits. The decision to prohibit the original AI manager from generating code stemmed from concerns over reliability and security in production environments. Instead, the developers turned to Claude Opus to handle coding tasks. This case highlights practical challenges of deploying AI agents in e-commerce automation and information security contexts.
Developer Builds MCP Linter and Discovers Security Issues in Anthropic Official Servers
A developer has released mcp-linter, a lightweight security and compliance tool for the Model Context Protocol used by Anthropic's Claude ecosystem. The linter detects critical problems such as stdout pollution that breaks JSON-RPC framing, missing destructiveHint annotations that allow autonomous agents to execute dangerous actions without human confirmation, prompt injection vectors hidden inside tool descriptions, and incomplete input schemas that increase model hallucinations. When run against Anthropic's reference servers, the tool assigned low health scores to server-memory and especially server-filesystem, highlighting dozens of parameters lacking descriptions. The utility runs with zero dependencies, supports SARIF output for GitHub Security, and can generate automatic JSON patches. The project is open source under MIT license and already integrates into CI pipelines via a dedicated GitHub Action.
Pentesting AI Components: Key Vulnerabilities CISOs Must Address in RAG and AI Agents
The article examines how AI integration into corporate systems dramatically expands the attack surface beyond traditional web application testing. It details risks associated with chatbots, RAG-enabled systems that pull from internal documents, and autonomous AI agents capable of executing real actions via APIs. Yuri Grishaev, an OSCP+ certified specialist and top Standoff 365 hacker, explains how prompt injection can bypass access controls and lead to data leaks or unauthorized operations. The piece stresses that service accounts often hold broad privileges, allowing AI components to serve as indirect paths to sensitive data even when direct user access is restricted. It also covers how AI-generated output can trigger classic vulnerabilities such as XSS if not properly sanitized. Recommendations include inventorying all AI tools, enforcing least-privilege principles, and validating user permissions before any model processes or acts on retrieved content. ABP2B provides free checklists and policy templates to help organizations prepare for secure AI adoption.
Local LLMs Enable Scams by Drafting Fraudulent Replies Without Warnings
Tests on consumer hardware showed that popular 7-8B local models almost never flagged classic advance-fee schemes when asked to draft replies instead of detecting fraud. The author ran 42 scam scenarios across Russian, Kazakh and mixed language on Llama 3.1 8B, Qwen 2.5 7B and DeepSeek-R1 8B using only an RTX 5050 laptop and Ollama. Without additional controls the models produced ready-to-send messages agreeing to prepaid transfers to unknown Kaspi Gold numbers in nearly every case. Introduction of the MoneyGate layer, which combines a mandate check, a separate judge model and hard-coded red-flag rules, blocked all 42 malicious requests while still allowing most legitimate payments to proceed. The benchmark KZ Scam Shield covering 12 Kazakhstan-specific fraud patterns remains publicly available for further testing.