ZeroHour

Search: “agent security”

600 stories

What 90 days and a small budget can buy in AI agent security

Versa Field CISO details hidden costs of self-hosting open-weight models and a 90-day AI agent security plan of inventory, blast-radius reduction and testing.

In a Help Net Security interview, Prasad Tharippala, Field CISO at Versa, argues running open-weight models in-house improves control but shifts hardening, patching, access control, monitoring and incident response onto the buyer, with underestimated costs in GPU infrastructure, licensing review, EU AI Act compliance and scarce AI/ML security skills. On red-teaming AI agents, he recommends testing prompt injection, indirect injection, excessive permissions, data leakage, memory and RAG poisoning, malicious tool outputs, cross-agent trust abuse and infrastructure attack paths, mapped to OWASP agentic guidance and MITRE ATLAS. He highlights the handoff between chained agents as a major risk zone and stresses exercising human approval, shutdown and rollback controls under test conditions. For teams with 90 days and small budgets, he ranks inventory, blast radius reduction and ongoing testing as the priority order.

Help Net Security · 19d agoAI safety & security

The Model Proposes, the Code Disposes: A Pre-Registered Ablation of a Verifier-and-Acceptance Stage in an LLM-Orchestrated Offensive-Security Agent

Pre-registered ablation finds a model verifier stage in an LLM offensive-security agent suppresses findings; removing it eliminated suppression with precision tradeoff.

The paper evaluates a verifier-and-acceptance stage in an LLM-orchestrated offensive-security agent via a pre-registered 20-run confirmatory ablation and a 2x2 factorial study with 40 runs on vulnerable lab targets. Removing the stage eliminated pre-report suppression (median 2 vs 0 findings, p = 0.00003) but reduced model-blinded shipped precision (0.471 vs 0.353, p = 0.0087). Suppression was attributed to the model verifier rather than deterministic acceptance rules, and an instrumented canary recorded zero external contacts in all 60 runs. The full design retained 93.8% of model-adjudicated true candidates but failed its pre-registered non-inferiority floor of 0.90.

arXiv cs.CR · 2d agoResearch

Toward Secure AI-Powered Penetration Testing Agents: Security Threats, Guardrails, and Architectural Perspectives

Paper proposes a threat taxonomy and guardrail analysis for LLM-powered autonomous penetration testing agents, covering lifecycle, architecture, and behavioral attacks.

The paper analyzes security threats to autonomous LLM-based penetration testing agents that independently perform reconnaissance, vulnerability identification, exploitation planning, and post-exploitation with minimal human supervision. It characterizes trust boundaries and attack surfaces of representative agent architectures and proposes a threat taxonomy spanning LLM lifecycle attacks, agent-architecture attacks, and cross-cutting behavioral attacks. The authors argue existing conversational-AI guardrails are insufficient for agentic, long-horizon offensive workflows and outline research directions for context-aware, architecture-aware guardrails.

arXiv cs.CR · 1d agoAI safety & security

Vulnerability Localization Benchmark: Measuring Agentic Security Analysis at Repository Scale

VLoc Bench tests 27 language models at locating vulnerable files in 290 repositories; best system reaches 0.229 File F1 and 38.4% of tasks unsolved.

The Vulnerability Localization Benchmark (VLoc Bench) contains 500 real-world vulnerabilities from 290 repositories across six package ecosystems and 147 CWE categories, pairing pre-fix and post-fix repository snapshots. Agents receive only a CWE description and read-only terminal access to identify affected files, and must confirm absence on patched snapshots. The strongest of 27 language models and four static-analysis tools achieves just 0.229 File F1; 38.4% of tasks receive no correct localization, and effective localizers still report unsupported locations on patched repositories.

arXiv cs.AI / cs.LG / cs.CL · 1d agoAI research

The OWASP Top 10 for LLM Applications 2026: From Model Risks to Agentic Security

Akamai analyzes the OWASP Top 10 for LLM Applications 2026, which shifts focus from model-level risks to agentic AI security.

The OWASP Top 10 for LLM Applications has been updated for 2026, and Akamai published an analysis of the revised list. Per the title, the 2026 edition shifts emphasis from model-level risks toward the security of agentic AI systems, framed as a realistic security model. No article body was available, so the specific ranked risk entries cannot be enumerated.

Akamai Blog · Aug 14, 2026AI safety & security

HelmGuard Raises $7.3 Million for Agentic GRC and Security

Agentic GRC and security startup HelmGuard raised a $7.3 million seed round co-led by Infinity Ventures and Frontline.

HelmGuard, a UK-based startup founded in 2024 by former Palantir executive John Daley (CEO) and Jack Miller (CTO), announced a $7.3 million seed round co-led by Infinity Ventures and Frontline, with participation from FinTech Collective, Stage 2 Capital, and Entrepreneurs First. The company builds agentic governance, risk and compliance (GRC) software that collects risk signals directly from integrated source systems and uses AI agents to automate risk management, assurance, and control gap assessments. It claims the platform cuts assessment cycles to hours by unifying fragmented compliance and security data.

SecurityWeek · 7d agoIndustry

Securing AI agents: Key controls and best practices

Security experts warn AI agents with employee-level privileges outpace human access controls and advise layered enforcement, sandboxing, and approval gates.

CSO reports that enterprises granting AI agents credentials, tools, and network access face risks that human-focused identity controls cannot contain, including machine-speed action chaining and sub-agent spawning. Experts from Strike Graph, Veracode, Delinea, and XBOW recommend treating agents as privileged insiders with hard technical boundaries: egress proxies with allowlists, short-lived brokered tokens, separated read/write rights, and approval for high-risk actions. XBOW describes a layered architecture with a guardian model reviewing agent actions and per-agent audit files. OWASP guidance on excessive agency urges limiting agent functions, permissions, and autonomy with authorization enforced downstream.

CSO Online · 8d agoAI safety & security

CISOs Race to Control AI Agents Without Destroying Their Value

Team8 survey: 78% of CISOs name AI and agent security their biggest pain point as over-privileged agents expand attack surface.

Team8's annual CISO Village survey reports that 78% of security leaders cite AI and agent security as their biggest pain point, twice the second-ranked concern (39%), while 71% are experimenting with or augmenting security tools using AI agents. Team8 CISO Tim Brown warns that employee-built agents created with tools like Claude Code, Cursor and Codex can take unintended harmful actions, such as poking around production systems, because prompt imprecision combines with non-deterministic model behavior. Brown recommends building guardrails into the agent development process to limit where agents can go and what they can do, without destroying business utility. He also urges greater transparency and experience sharing among security leaders facing the same agent security problems.

SecurityWeek · 2d agoAI safety & security

Sequoia doubles down on Cymphony as AI agents create new enterprise security risks

Cymphony emerges with $30M from Sequoia and SMBC to give security teams unified visibility into AI agent and non-human identities.

Cymphony, a New York- and Tel Aviv-based startup, raised a $25 million Series A co-led by Sequoia and SMBC Fin Atlas Beyond Fund, valuing it above $100 million. Its platform builds a "workforce graph" unifying identity, data, and activity signals for employees, AI agents, and other non-human identities. The company says it found roughly 85,000 files exposed to AI tools at one US public company and reached seven-figure ARR in its first year of sales with customers including KKR and Syngenta. Sequoia previously led its undisclosed seed round, betting on Israeli Talpiot program alumni founders.

TechCrunch · Security · 7d agoIndustry

Exaforce extends its AI security tool to monitor more than just Claude

Exaforce AI Security extends beyond Claude to monitor OpenAI, Gemini, and Copilot agents using existing SOC telemetry, no new endpoint agents.

Exaforce expanded its June Claude Compliance API integration into Exaforce AI Security, adding monitoring for OpenAI, Gemini, Microsoft Copilot, and OAuth-connected AI apps. The tool inventories AI agents by correlating EDR, cloud, SaaS, and model-provider logs without new gateways or endpoint agents, and can respond by revoking sessions, deactivating API keys, isolating devices, or killing agent processes via existing controls. Analysts note the agentless approach lowers friction but lacks runtime inspection and inline blocking offered by competitors such as Palo Alto Prisma AIRS, SentinelOne Prompt AI Agent Security, and CrowdStrike Falcon Guardian. A March 2026 Cloud Security Alliance survey found 68% of organizations cannot distinguish human from AI-agent activity and 74% report AI agents receive excessive access.

CSO Online · 1d agoTools

One in four MCP servers opens AI agent security to code execution risk

Noma Security whitepaper finds most popular AI Skills and many MCP servers carry high-risk capabilities, with state changes most prevalent.

Noma Security analyzed hundreds of popular MCP servers and Skills across eight risk categories, finding most widely used Skills carry at least one risky characteristic and a typical enterprise runs well over a hundred high-risk agent tools, with arbitrary code execution common across MCP servers. The most prevalent risk is the ability to change state or data, and named toxic combinations include ContextCrush data leakage, ForcedLeak via poisoned Salesforce CRM records, DockerDash supply-chain compromise, the Replit production database deletion, and the hijacked Amazon Q VS Code extension. Building on OWASP LLM06:2025, the paper proposes the No Excessive CAP framework of capabilities, autonomy, and permissions, recommending allowlisting, MCP version pinning, approval gates on irreversible actions, and user-scoped expiring credentials.

Help Net Security · 23d agoAI safety & security

CONTINUITY: Security-Context Contracts for Composable LLM Agent Controls

Researchers introduce CONTINUITY, a framework of assume-guarantee contracts that preserves LLM agent security context across components, verified across 2,560 attack instances.

The paper identifies security-context discontinuity, where individually sound controls drop, widen, or reinterpret security context as actions cross component boundaries, and proposes CONTINUITY, a framework of assume-guarantee contracts using signed root grants, provenance commitments, role-bound transition receipts, and effect-bound execution permits. It formalizes end-to-end consequence integrity, requiring every external effect to be backed by a valid authorization witness linking principal, task, provenance, and policy state. A reference verifier and cross-layer fault-injection suite covering 32 fault classes showed the full configuration committed no harmful external effect across 2,560 parameterized attack instances while completing all 700 benign tasks and escalating all 200 ambiguous cases.

arXiv cs.CR · 12d agoAI safety & security

Google’s AI security agents found 100+ critical software vulnerabilities in just two days

Google Mandiant's AVDH, a chain of AI agents, found over 100 verified high-severity vulnerabilities and 12 assigned CVEs scanning code for ten months.

Google Mandiant disclosed AVDH (Agentic Vulnerability Discovery Harness), an internal pipeline of chained AI agents built on the Agent Development Kit that hunts vulnerabilities in source code. In a live investigation of stolen corporate repositories it verified more than 100 high-severity flaws in two days; over ten months it scanned tens of millions of lines of code and produced tens of thousands of findings, yielding 12 assigned CVEs including CVE-2026-13242 and CVE-2026-55803, with about a dozen more in active disclosure. Human consultants manually reproduce every confirmed finding before it counts.

EvoSafeHarness: Evolving Model- and Domain-Specific Harnesses for Securing Agents

EvoSafeHarness auto-synthesizes per-model, per-domain safety harnesses, cutting prompt-injection attack success on AgentDojo to 0.0% at 82.8% utility.

EvoSafeHarness is an optimization framework that synthesizes deployable safety harnesses for frozen LLM agents in a target domain, jointly searching natural-language policies and executable code logic guided by model behavior, domain specifications, and adversarial review. On DecodingTrust-Agent it reduces average attack success rate from 45.6% to 10.0% at a 3.3-point utility cost, and on AgentDojo reaches 82.8% utility at 0.0% ASR, twice CaMeL's utility at that operating point. It keeps mean ASR below 20% under adaptive PAIR attacks and transfers unchanged to unseen AgentDyn suites. The analysis finds domain semantics determine required safety relations while model and runtime behavior determine enforcement points.

When an Attacker Meets a Group of Agents: Navigating Amazon Bedrock's Multi

Unit 42 red-teamed Amazon Bedrock multi-agent applications, demonstrating prompt-injection attack chains that leak agent instructions and invoke tools, mitigated by Bedrock Guardrails.

Unit 42 red-teamed Amazon Bedrock Agents' multi-agent collaboration in Supervisor and Supervisor with Routing modes. The demonstrated attack chain detects the operating mode, discovers collaborator agents, delivers attacker-controlled payloads, and can disclose agent instructions and tool schemas and invoke tools with attacker-supplied inputs. No vulnerabilities were found in Bedrock itself, and the built-in prompt attack Guardrail blocked the attacks when properly configured. The researchers collaborated with Amazon's security team and frame the findings as a broader prompt injection risk for LLM-based systems.

Palo Alto Unit 42 · Aug 17, 2026AI safety & security

Dataminr uses agentic AI to predict and verify security threats

Dataminr launches agentic AI capabilities for corporate security, adding automated event corroboration, context, and near-term threat prediction.

Dataminr Advanced for Corporate Security introduces Agentic Corroboration, Agentic Context, and Near-Term Predictive Intelligence, now generally available, moving the company from real-time alerting to what it calls Autonomous Real-Time Intelligence. The product relies on more than 60 fine-tuned task-specific LLMs trained on a 10+ year proprietary event archive rather than general-purpose frontier models. Upcoming releases include ReGenAI Tailored Live Briefs, a Watchlist Agent, Agentic Search, and an Advanced API suite.

Help Net Security · 2d agoIndustry

Exein Secures $270M at $1.7B Valuation for Physical AI Security

IoT security firm Exein raised $270 million at a $1.7 billion valuation to expand runtime protection and physical AI security agents.

Italy-based IoT security startup Exein announced a $270 million oversubscribed round led by Headline, bringing total funding above $600 million and valuing the company at $1.7 billion. Exein builds embedded and kernel-level runtime protection for IoT devices and is developing a proprietary foundation model for physical AI security powering autonomous defense agents. The funding will accelerate expansion, particularly into the US market.

SecurityWeek · 1d agoIndustry

Ping Identity introduces enterprise security for personal AI agents

Ping Identity launched Enterprise Personal Agent Access to discover, authenticate and control personal AI agents like Claude at runtime.

Ping Identity announced Enterprise Personal Agent Access, delivered through PingOne Privilege, to give enterprises visibility and control over personal AI agents such as Claude and Claude Code. The product discovers agents including shadow AI, associates each session with the user and device behind it, and enforces allow, deny, log, human-approval or revocation decisions on agent access at runtime. It enables secretless developer workflows so agents can commit code without long-lived credentials while keeping actions attributable to the agent. Ping cites Gravitee research that 48% of production AI agents run unsecured and says the product is available now and piloting with global enterprises.

Help Net Security · 13d agoAI safety & security

GitLab 19.3 helps enterprises scale agentic development securely

GitLab 19.3 runs its Duo Agent Platform AI Gateway inside Dedicated single-tenant environments and adds Secrets Manager plus agentic SAST remediation.

GitLab 19.3 lets GitLab Dedicated customers run the Duo Agent Platform AI Gateway within the same single-tenant environment and region, with support for bring-your-own inference models. The release adds Secrets Manager in limited availability scoping secrets to environment and branch across Kubernetes, Terraform, and OpenTofu, plus bulk SAST false positive detection and agentic vulnerability resolution generating ready-to-merge fixes. Flow Creator Agent creates automation flows from plain-language descriptions, and GitLab Credits usage caps are now generally available.

Help Net Security · 26d agoAI tools & infra1

Orchid Security targets AI agent risk with drift detection and kill switches

Orchid Security launched identity drift detection and application-level kill switches to govern AI agents that exploit enterprise identity debt.

Orchid Security announced AI readiness controls including agent discovery, continuous drift detection between an agent's intended purpose and observed behavior, and application-level kill switches that revoke credentials, disconnect tools, or suspend agent workflows. The company cites its Identity Gap 2026 finding that 57% of enterprise identity is unseen and unmanaged, which agents can leverage to gain elevated access in seconds to minutes. New integrations include a certified PAM integration for Palo Alto Networks Idira and identity telemetry streaming to Splunk Enterprise Security. The launch follows agentic enhancements to Orchid's Identity Control Plane in May 2026 and cites NIST's draft Cyber AI Profile and DORA as regulatory drivers.

Help Net Security · 7d agoAI safety & security

Securing Claude Code: The New Compliance API, Local Visibility, and Identity Governance

Anthropic's new Compliance API endpoints expose Claude Code local session transcripts, highlighting governance gaps for endpoint AI agents.

Anthropic added local session transcript endpoints to its Compliance API on August 11, 2026, giving security teams visibility into prompts, bash commands, file operations, and MCP commands run by Claude Code harnesses on endpoints. The article argues local harnesses break the classic shared-responsibility model, citing Token Security data that 68.6% of discovered AI agents run on endpoints, and a Cloud Security Alliance survey of 418 IT and security professionals in which 82% found an unknown agent within the past year. It outlines three governance layers: Anthropic managed settings as a policy baseline, the Compliance API for cloud-visible transcripts, and endpoint telemetry to connect agent activity to identity, credentials, and permissions.

The Hacker News · 16d agoAI safety & security1

Why 2026 is the Year to Upgrade to an Agentic AI SOC

Elastic Security Labs argues 2026 is the production inflection point for agentic AI in security operations centers.

Elastic Security Labs argues 2026 is the practical inflection point for agentic AI SOCs, noting nearly two-thirds of organizations are experimenting with AI agents while fewer than one in four have production deployments. The piece outlines operational challenges and recommendations: treat agents as non-human identities with least-privilege tool access, version-control system prompts as code, deploy unified agents with on-demand task packages, and enforce per-agent budgets and rate limits. It stresses explainability via RAG and transparent reasoning traces so analysts can verify and override autonomous decisions.

Elastic Security Labs · 7d agoIndustry

Your AI agent's system prompt is not a security control

AWS and SANS guidance says system prompts are not security controls; enforce user permissions at retrieval time and default-deny every agent tool invocation.

AWS VP Gee Rittenhouse and SANS fellow Eric Johnson, with three AWS security specialists, published agentic AI security guidance for organizations with agents running or under development. They recommend scoping queries to user permissions inside existing RBAC/ABAC systems and filtering results before the model's context window, noting prompts can be bypassed, ignored, or overridden. The guidance warns risk concentrates when one agent holds sensitive data access, external communication, and exposure to untrusted content, the vector for prompt injection, which OWASP ranks as the top AI application threat. It cites IBM 2025 research that ungoverned shadow AI added $670,000 to average breach cost, and prescribes 30-day behavioral baselines, Cedar or Open Policy Agent for default-deny tool invocation, and four-layer containment with automatic circuit breakers.

Help Net Security · 9d agoAI safety & security

Adversarial Testing of Automated Program Repair Agents for Security Vulnerabilities

SWEADV benchmark shows adversarial issue descriptions make LLM program-repair agents write insecure fixes in 51.7% of cases, evading most detection tools.

Researchers built SWEADV, a benchmark of 750 adversarial issue descriptions derived from 150 SWE-bench Verified repair tasks, covering command execution, deserialization, path traversal, denial of service, and weak hashing attack types. Tested on mini_swe agents backed by GPT-5-Mini, MiniMax-M2.5, and DeepSeek-R, adversarial descriptions induced malicious behavior with successful repair in 51.7% of cases. Detection was weak: LLM-as-judge pre-repair screening reached only 62.3% accuracy, and post-repair detection via static analysis and LLM-as-judge achieved just 39.4% and 55.4%.

arXiv cs.CR · 1d agoAI safety & security1

Rubrik MCP gives AI agents controlled access to security intelligence

Rubrik launched MCP support exposing Rubrik Security Cloud APIs to enterprise AI agents with RBAC, configurable permissions, and OWASP MCP Top 10 guardrails.

Rubrik announced Rubrik MCP (Model Context Protocol), giving organizations' AI agents a secure, programmable path to Rubrik's data, identity, and application intelligence via the Rubrik Security Cloud API schema. Teams can save multi-step recovery or compliance workflows as reusable, deterministic tools, with role-based access control parity and OWASP MCP Top 10 aligned guardrails. Rubrik engineered its agent architecture with Anthropic's teams for multi-step reasoning in incident response, and says Rubrik AI is now trusted by one-third of its global customers.

Help Net Security · 6h agoTools1

AI agent authorization risks remain a gap in new NIST-CISA token security guidance

NIST and CISA release IR 8587 guidance on securing signed tokens, but AI agent authorization and delegation risks remain out of scope.

NIST, with CISA support, published 'Protecting Tokens and Assertions from Forgery, Theft, and Misuse' (NIST IR 8587), recommending continuous monitoring and tighter token lifecycle controls for SSO and API access. The guidance does not yet fully address AI agent identity, delegation chains, or prompt injection steering agents with valid tokens, and NIST says new or expanded standards are needed. Experts recommend treating AI agents as low-trust non-human identities, maintaining agent inventories, expiring credentials after task completion, and requiring human approval for high-risk actions. The report references shared-signal mechanisms like CAEP and RISC, and follows a May incident where a CISA contractor GitHub repository exposed AWS and GitHub tokens.

CSO Online · 1h agoAdvisory