Anthropic Launches Claude Security Plugin to Let Claude Review Its Own Code in Terminal Workflow
Anthropic has introduced the Claude Security plugin in beta, integrating it directly into the Claude Code terminal workflow. Developers who finish a feature with Claude Code now see an option to let the AI scan the code for vulnerabilities it may have introduced before committing.
How the Plugin Operates
Traditional rule-based scanners rely on matching known vulnerability patterns, which produces high false-positive rates and misses logic flaws. Claude Security instead uses a multi-agent system: it first reads the code and maps the architecture, then identifies potential threat points, and finally verifies suspicious findings to filter out false positives. The plugin generates patch suggestions that match the project’s existing coding style rather than generic alerts.
Every proposed fix must be reviewed and approved by a human; the tool never commits changes automatically. This design keeps the developer in control while adding an extra layer of analysis inside the existing command-line workflow.
Addressing Gaps in Traditional Tools
The plugin targets severe vulnerability classes that rule-based scanners often overlook, including memory corruption, injection defects, authentication bypasses, and complex logic errors. It excels at cross-file issues where data flows from one file to another and is incorrectly trusted in a business branch. By reading Git history and tracing data flows across files, the system reasons about whether a potential issue is actually exploitable instead of applying mechanical pattern matching.
Limitations and Practical Considerations
The feature remains in beta, and Anthropic has not published quantitative data on false-positive or false-negative rates. Large full-repository scans can consume significant tokens and occasionally switch to more expensive models, so teams are advised to limit scans to changed directories or use scheduled incremental checks. The company positions the tool as a supplement to existing SAST, DAST, and human security processes rather than a replacement.
Recommended Daily Usage
The most cost-effective approach is to run the scanner on uncommitted diffs before each commit. Results can be forwarded via webhook to Slack or Jira, exported as CSV or Markdown for audit trails, and dismissed findings are tracked to prevent repeated review. This workflow raises the security baseline for small teams and open-source maintainers who lack dedicated security staff.
Broader Implications of AI Reviewing AI-Generated Code
The release highlights an emerging pattern in which the same AI capabilities used to generate code are now applied to detect vulnerabilities created by that generation process. While the approach can surface issues traditional tools miss, Anthropic emphasizes that human oversight remains essential and that token costs must be managed. The long-term impact on code security will depend on real-world performance data gathered during the beta period.
Related articles
Fine-Tuning Prompt Injection Detector: Five Rounds, Four Failures and Gates Against Regression
AGIMA technical director Andrey Nepryakhin details the challenges of adapting an open-source GLiNER-based prompt injection detector for Russian corporate traffic. The system processes nearly one million requests monthly from eighty employees using agentic tools. Five fine-tuning rounds using LoRA adapters on microsoft/mdeberta-v3-base were conducted, yet only the second round reached production. Failures stemmed from regression on previously fixed attacks, imbalanced negative samples, and reliance on rule-based signals instead of the model. The team introduced cumulative corpora, person-based splits, and ablation checks against the base model to prevent silent rollbacks. A gradient mass rule limits any single phenomenon to 10-20 percent of training data to avoid precision or recall collapse.
Secure AI-Assisted Development: Five Critical Practices for Vibe Coding
AI has become the default path for quickly turning ideas into working applications, yet most security flaws in these projects stem not from model errors but from developer assumptions. The AI simply implements what is requested, and security requirements are rarely included in prompts. Five key areas account for the majority of issues: explicitly defining what an application must not do, distinguishing authentication from authorization, reviewing AI-suggested dependencies, removing secrets from commit history, and validating business logic rules that automated scans cannot detect. Applications built this way are already attracting cybercriminals because the resulting vulnerabilities can be identified and exploited at scale. The HackerSec Pentest Platform is positioned as an accessible option for vibe coders seeking quality security testing before production deployment.
Selectel Launches Local AI Admin Agent aish in SELECTOS to Eliminate Cloud Data Risks
Selectel has introduced aish, a generative AI agent embedded directly into its SELECTOS server operating system. The solution allows system administrators to analyze incidents, review logs, and perform routine operations entirely on-premises without transmitting sensitive data to external cloud providers. Aish operates with a human-in-the-loop model, generating proposed commands and explanations that must be approved by an operator before execution. The primary goal is to support organizations bound by strict data-protection policies, including compliance with Russian Federal Law 152-FZ, by keeping all context within local infrastructure. SELECTOS is based on Debian and is distributed in ISO, QCOW2, and container formats for both cloud and dedicated servers. According to Kirill Dmitriev, Director of System Software at Selectel, the agent is intended to lower the entry barrier for Linux system administration while respecting restrictions on the use of foreign large language models.
Three-Phase Defense Model OGL-Mini Protects AI Agents from Prompt Injection and Modern LLM Threats
The article presents OGL-Mini, an open-source hybrid security model designed to defend AI agents, chatbots, and RAG systems against contemporary threats including prompt injection, system prompt leakage, and agentic attacks. It details real-world incidents from 2025-2026 involving Microsoft Copilot Studio, OpenAI Atlas, and Claude Code, showing how attackers bypass safety filters using structured formats and obfuscation. OGL-Mini employs a three-stage pipeline of heuristics, TF-IDF mini-classifier, and PII detection to intercept malicious inputs before they reach the LLM. The model was trained on over 110,000 examples covering OWASP LLM01 categories, agentic misuse, and modern obfuscation techniques. Available in TypeScript, Python, and Go, it runs efficiently on standard CPUs with low latency. The solution aims to address gaps in built-in LLM safeguards that remain vulnerable to techniques like Policy Puppetry.