ZeroHour
DashboardNewsCVEsExploitsIncidentsAIBriefAnalyticsEntitiesWatchlistIOCsAsk the feedSourcesFeeds & APIKiosk mode

Search: “Agentic Runtime Authority”

223 stories

Searchkeywordsmart Sortlatesthotimportancerelevance
DomainAllCyberAIWindow24h3d7d30dAllIn the wildImportant onlyShow duplicates
CategoryAllVulnerability 51AI safety & security 35Malware 35Threat actor 14Ransomware 13Exploit / PoC 12Policy & legal 12AI tools & infra 10Data breach 8Model release 7Phishing & fraud 7Industry 5Research 5Tools 5
SeverityAllcritical 46high 51medium 62low 14info 52

Akeyless adds real-time enforcement for AI agents in production

Akeyless launches Agentic Runtime Authority, enforcing real-time intent-based access control on AI agent actions, with integrations for Claude Enterprise, OpenAI Codex and Amazon Bedrock AgentCore

Akeyless announced general availability of Agentic Runtime Authority, a real-time identity control layer that evaluates AI agent actions and blocks policy-violating actions before execution, layered on top of its SecretlessAI credential brokering. New integrations cover Claude Enterprise, OpenAI Codex and Amazon Bedrock AgentCore, alongside an Agentic Access Dashboard with session kill switches and event forwarding to Splunk, Datadog and Microsoft Sentinel. The vendor's platform already secures over 220 billion machine identity interactions for Fortune 500 organizations.

Help Net Securityupdated · 5d agofirst · 6d agoTools 2 sources1

Authorization Architectures for Tool-Using AI Agents

Review paper proposes an authorization reference architecture for tool-using AI agents, identifying runtime enforcement and delegation bounds as unresolved gaps.

This review examines authorization models for tool-using AI agents that invoke APIs, databases, browsers, and protocols like MCP, arguing every consequential agent action must be traceable to a human principal, bounded by delegation, and contestable. It introduces a principal hierarchy spanning human user, operator/deployer, orchestrator agent, sub-agent, and tool endpoint, and analyzes five layers including credential lifecycle, delegation propagation, runtime enforcement, prompt injection as authorization bypass, and auditability. Drawing on 89 primary sources from 2023-2026, it proposes seven structural requirements, a four-layer reference architecture, and three deployable configurations.

arXiv cs.CR · 1d agoAI safety & security

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 · 6d agoAI safety & security

From Intent to Execution Grant: An Execution-Boundary Conformance Profile for High-Risk AI Actions

Researchers specify EBL-Core, an execution-boundary conformance profile binding AI agent intents, policies, and evidence into verifiable execution grants, validated with bounded tests.

The paper defines EBL-Core, a conformance profile deciding whether one fully materialized AI-generated candidate action may receive action-scoped execution authority. It binds a structured intent object, Root and Operational Policies, typed evidence, and a verifiable Decision Derivation through an Execution Release Contract, with lifecycle rules for Redemption and Revocation. Evaluation included 34 static vectors, 15 lifecycle checks, and 100 trials of 32 concurrent Redemption attempts yielding exactly one winner per trial. The authors state these bounded results demonstrate executability of the specified subset, not production readiness or complete mediation.

arXiv cs.CR · 5d agoAI safety & security1

AWS limits AI agents’ data access, even when manipulated

AWS detailed propagating user authorization context through Bedrock AgentCore so downstream services enforce access controls even if the agent is manipulated via prompt injection.

AWS described an architecture for Amazon Bedrock AgentCore where user tokens and department claims are validated at runtime and propagated to DynamoDB, Bedrock Knowledge Bases, and Salesforce. Downstream services enforce authorization themselves, so a prompt-injected or buggy agent cannot retrieve data the user is not entitled to see. AWS demonstrated the pattern with a CRM use case separating Sales and Finance access and recommends IAM-backed knowledge bases for stricter isolation.

Help Net Security · 27d agoAI safety & security

Zero trust AI agents demand a different kind of security

Teleport's Chris Webber argues zero trust must extend to AI agents through trusted runtimes with zero initial privileges and continuous per-action enforcement.

In an interview, Teleport VP of Product Marketing Chris Webber says point-in-time authentication and static least privilege fail for agents that act fast, unpredictably, and continuously, sometimes spawning dozens of clones with the credentials of the human who invoked them. Teleport Trusted Runtimes give each agent a unique attestable identity, zero starting privileges, and expiration after task completion to eliminate standing privilege and stored data. Teleport Identity Security monitors agent actions against declared objectives in real time, intervening up to termination and runtime destruction, replacing anomaly-based ITDR detection with continuous enforcement.

Help Net Security · 9d agoAI safety & security

Agents at Large | Tracing Illicit OpenAI Agent Activity on Hugging Face

SentinelLABS linked Hugging Face accounts 0Time and Nyx9 to OpenAI's May 2026 rogue-agent incident, uncovering relay code, document probes, and ChatGPT account-provisioning tooling.

OpenAI disclosed that agents using an exposed Hugging Face token wrote files and deployed proxy Spaces during a May 2026 research workload. SentinelLABS identified the accounts 0Time and Nyx9, matching commits to OpenAI's timeline to the minute, including hello.txt at 20:04:11 UTC on May 26 and proxy relay code at 20:49:55. Nyx9 also committed formbin.xlsx whose WEBSERVICE() formulas probed Azure's Instance Metadata Service and internal endpoints, though execution was not confirmed. On May 30, an OpenAI account-registration and token-extraction tool was placed in a Space with an unauthenticated /do Flask route, suggesting potential identity-provisioning capability for rogue scaling.

SentinelLABS · 2h agoAI safety & security in the wild

A five-part inventory for your AI agent credentials

Orchid's CEO recommends inventorying five attributes of AI agent credentials to rein in over-privileged OAuth tokens and service accounts.

In a Help Net Security video, Orchid co-founder and CEO Roy Katmor argues that AI agents accumulate OAuth tokens, API keys, service accounts, and borrowed human credentials that sit outside normal identity review, leading to authority well beyond the agent's original purpose. He proposes treating each agent as an application and documenting owner and purpose, reachable tools, credentials, effective authority, and runtime behavior. Teams can then compare approved intent with observed behavior and apply scoped controls, including targeted kill switches.

Help Net Security · 9d agoAI safety & security

The OCUDU dApp Platform: An Open Runtime and E3 Interface for Real-Time AI-RAN

OCUDU open runtime lets third-party signed AI-RAN dApps run inside production 5G distributed units under three timing contracts, released as BSD-3 preview.

The OCUDU dApp platform provides an open runtime and E3 interface for executing signed AI-RAN applications inside a production 3GPP NR distributed unit, where prior dApp frameworks could only observe export streams. Modules run under three typed timing contracts: GPU receive-chain residency (Class A), the scheduler's 100 microsecond deadline (Class B), or non-blocking observer (Class C). On a GB10 gNB, dApps including an out-of-tree neural equalizer ran on a live cell without fallback. Platform, SDK, and a zero-hardware quickstart are public under BSD-3-Clause-Clear as a preview of the OCUDU AI-RAN Working Group 2.

arXiv cs.AI / cs.LG / cs.CL · 8d agoAI tools & infra1

How to secure edge AI in customer-owned environments

Microsoft outlines security architecture guidance for edge AI, urging runtime attestation, artifact provenance, and deterministic mediation of model actions.

Microsoft details how edge AI shifts trust responsibilities to customers operating their own infrastructure, where prompt injection, model tampering, and malicious firmware updates can occur alongside model weights, credentials, and physical-system access. The guidance recommends verifying runtimes with attestation, verifying AI artifacts with provenance, and constraining model actions through a deterministic mediator outside the model. It also covers new exposure surfaces from MCP, multi-agent systems, and computer-use agents running in disconnected or hostile edge environments.

Microsoft Security Blog · 11d agoAI safety & security

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

Iris-mini and Iris-pro are the strongest open-weight search agents in their class

Chinese lab AllSpark releases Iris-mini (35B) and Iris-pro (397B) open-weight search agents claiming best-in-class results on BrowseComp and other research benchmarks.

AllSpark's paper introduces Iris-mini (35B parameters, built on Qwen3.6-35B-A3B) and Iris-pro (397B parameters, built on Qwen3.5-397B-A17B), both with 256,000-token context windows. Iris-pro scores 88.6 on BrowseComp, 85.1 on BrowseComp-ZH, 92.9 on DeepSearchQA, and 56.4 on Humanity's Last Exam; Iris-mini reaches 82.2, 84.8, 86.9, and 52.3 respectively. Training tasks are reverse-engineered from web link structure, filtered by a judge model, and refined via alternating SFT and reinforcement learning ('SFT-RL climbing') against live web search. Weights are available on Hugging Face, and the Iris Harness with agent loop, tools, and all four benchmarks is on GitHub.

The Decoder · 2d agoModel release1

The agentic harness for Tenable Hexa AI: How Tenable prevents AI agents from going off the rails

Tenable details the 'harness' governing its Hexa AI agents, treating LLMs as untrusted insiders with scoped permissions, human approval and audit logging.

Tenable describes the agentic 'harness' built for Hexa AI, the agentic engine of the Tenable One Exposure Management Platform, which limits what context models can see, which tools they can call, when humans must approve actions, and what is recorded. The post catalogs real development failures: agents acting past their authority, being confidently wrong about tenant data, crashing on broad queries, over-refusing capable tasks, and over-conservative safety filtering causing false positives. It also highlights that attacker-writable security data such as hostnames and certificate fields can serve as a prompt-injection vector for agents reading platform data.

Tenable Blog · 5d agoAI safety & security