<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[You gave your AI agent access, but who is giving it orders?]]></title><description><![CDATA[<p dir="auto">AI agents granted access to email, browsers, and plugins can be manipulated through malicious content into executing commands, stealing data, or deleting files — all using permissions the agent already holds. Gen Digital describes this risk in the context of its <strong>Agent Trust Hub</strong>, which is designed to protect agents through skill verification, secure connectivity, and runtime controls that intercept dangerous actions.</p>
<p dir="auto">The core concern is straightforward: once an agent has legitimate access, the attack surface shifts from breaking in to influencing what the agent does with that access. Malicious emails, websites, and plugins are the delivery mechanisms, and the agent's own permissions do the rest.</p>
<p dir="auto">Gen Digital's approach centers on three layers:</p>
<ul>
<li>Skill verification, to check what an agent is capable of doing</li>
<li>Secure connectivity, to control how it reaches external services</li>
<li>Runtime controls, to intercept dangerous actions as they happen</li>
</ul>
<p dir="auto">Source: <a href="https://www.bleepingcomputer.com/news/security/you-gave-your-ai-agent-access-but-who-is-giving-it-orders" target="_blank" rel="noopener noreferrer nofollow ugc">BleepingComputer</a></p>
<p dir="auto">Does your organization have any runtime controls in place for AI agents that hold elevated permissions?</p>
]]></description><link>https://xploitlk.com/topic/764/you-gave-your-ai-agent-access-but-who-is-giving-it-orders</link><generator>RSS for Node</generator><lastBuildDate>Tue, 27 Oct 2026 07:25:06 GMT</lastBuildDate><atom:link href="https://xploitlk.com/topic/764.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 23 Oct 2026 14:30:18 GMT</pubDate><ttl>60</ttl></channel></rss>