![\"\"](\"https:\/\/www.adminbyrequest.com\/en\/wp-content\/uploads\/2025\/10\/inline-1-4-1024x574.png\")
<\/figure>\n\n\n\nWhen AI Agents Run Commands with Your Privileges<\/h2>\n\n\n\n
An attacker doesn’t need to compromise your systems directly, they can just embed hidden instructions in a document that an AI agent processes. The agent follows these instructions while appearing to handle the employee’s legitimate request. The employee sees helpful output and runs the generated commands without realizing they’re malicious.<\/p>\n\n\n\n
Here’s how a typical attack unfolds:<\/p>\n\n\n\n
Step 1: Injection<\/strong> Step 2: Processing<\/strong> Step 3: Execution<\/strong> Step 4: Compromise<\/strong> Research from organizations like Microsoft’s Security Response Center<\/a> has demonstrated prompt injections that exfiltrate data, modify system settings, and execute unauthorized commands. The attacks work because AI agents can’t reliably distinguish between instructions from trusted users and instructions hidden in untrusted content.<\/p>\n\n\n\n Admin By Request’s EPM solution<\/a> helps here by removing standing admin rights and requiring approval for privilege elevation. When an employee wants to run an AI-generated script that needs elevated permissions, the request goes through a workflow that creates visibility and an audit trail. Someone can review what’s about to execute before it runs with admin rights.<\/p>\n\n\n\n AI agents often need authentication to do useful work. An agent that interacts with your cloud infrastructure needs API keys. One that modifies databases needs connection strings with passwords, while one that sends emails needs SMTP credentials.<\/p>\n\n\n\n Employees provide these credentials to make the AI agent functional. Those secrets end up stored in:<\/p>\n\n\n\n These credentials rarely get rotated because nobody thinks of the AI agent as a place where secrets are stored. An attacker who compromises an employee’s AI account doesn’t just get access to that account, they get access to every system that employee authenticated the AI agent with.<\/p>\n\n\n\n IT departments can spend ages dealing with shadow IT<\/a>, but Shadow AI moves even faster because AI tools require minimal setup and deliver immediate value. An employee can start using an AI agent in under a minute without installing anything or requesting access.<\/p>\n\n\n\n Your security team can’t monitor what they don’t know exists. Traditional network monitoring might catch some AI traffic, but many agents use standard HTTPS connections that look like regular web browsing. Data loss prevention tools might flag obvious data transfers, but they struggle with the contextual, conversational nature of AI interactions.<\/p>\n\n\n\n Writing a policy about acceptable AI use won’t stop employees from using unauthorized tools when those tools make their jobs easier. You need technical controls that work regardless of which AI service someone chooses.<\/p>\n\n\n\n The typical response to new security risks is writing policies and hoping employees follow them. With AI agents, that approach fails because the tools are too useful and too easy to access. You need technical controls that limit damage even when employees use unauthorized AI tools.<\/p>\n\n\n\n Implement just-in-time privilege elevation<\/a> with approval workflows. AI-generated commands can’t automatically run with elevated privileges, even if an employee trusts the output without reviewing it. Every privileged action requires explicit approval and gets logged.<\/p>\n\n\n\n Your most sensitive systems, databases, and file shares should require additional authentication that can’t be automated through an AI agent’s session. An AI agent working through an employee’s context shouldn’t be able to reach everything that employee technically has access to.<\/p>\n\n\n\n Track when elevated privileges are used and what processes run during those sessions. If an employee is constantly requesting elevation to run scripts, that pattern should be visible to your security team for review.<\/p>\n\n\n\n Implement code review requirements that treat AI-generated code the same way you’d treat code from someone who doesn’t understand your security standards. Static analysis tools can catch common vulnerabilities before that code reaches production.<\/p>\n\n\n\n If employees are using AI agents to interact with internal systems, assume those credentials could be compromised through the AI platform. Regular rotation limits the window of exposure if an AI account gets breached.<\/p>\n\n\n\n Agentic AI capabilities are expanding quickly. Today’s agents can read files and execute scripts. Future versions may have persistent access to your systems, make autonomous decisions about infrastructure changes, and coordinate with other AI agents to complete complex workflows.<\/p>\n\n\n\n Organizations that wait to address these security issues will find themselves playing catch-up after employees have already established insecure patterns that are difficult to reverse. The solution isn’t banning AI tools (employees will use them anyway, they’ll just hide it better). Build security controls that account for AI as another type of user that needs managed access, monitoring, and restrictions based on what it can do to your systems.<\/p>\n\n\n\n Controlling privilege escalation protects your systems whether the threat comes from AI agents, malware, or compromised accounts. Admin By Request EPM implements the just-in-time elevation and approval workflows that prevent unauthorized commands from running with admin rights. Try our free plan<\/a> for up to 25 endpoints, or book a demo<\/a> to walk through how it works.<\/p>\n\n\n\n <\/p>\n","protected":false},"excerpt":{"rendered":" Agentic AI tools boost productivity but open serious security gaps. Unauthorized access, prompt injections, and data leaks are now everyday risks.<\/p>\n","protected":false},"author":16,"featured_media":28434,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[36],"tags":[44,148,67,68,528,470],"ppma_author":[428],"class_list":["post-28430","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blogs","tag-ai","tag-cybersecurity","tag-pam","tag-privileged-access-management","tag-shadow-ai","tag-shadow-it","entry","has-media"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t
Attacker embeds malicious instructions in a document, email, or website that looks legitimate.<\/p>\n\n\n\n
Employee asks their AI agent to summarize the document or help with related work. The agent reads the hidden instructions.<\/p>\n\n\n\n
AI agent generates commands that follow the attacker’s instructions. Employee trusts the output and runs it.<\/p>\n\n\n\n
Malicious commands execute with the employee’s privileges, potentially with admin rights.<\/p>\n\n\n\nCredentials End Up in Unexpected Places<\/h2>\n\n\n\n
\n
Shadow AI Moves Faster Than Shadow IT<\/h2>\n\n\n\n
![\"\"](\"https:\/\/www.adminbyrequest.com\/en\/wp-content\/uploads\/2025\/10\/inline-2-4-1024x574.png\")
<\/figure>\n\n\n\nWhat You Can Do About It<\/h2>\n\n\n\n
1. Remove standing admin rights<\/h3>\n\n\n\n
2. Segment your network<\/h3>\n\n\n\n
3. Monitor privileged activity<\/h3>\n\n\n\n
4. Treat AI-generated code like untrusted input<\/h3>\n\n\n\n
5. Rotate credentials that might be exposed<\/h3>\n\n\n\n
This Isn’t Getting Simpler<\/h2>\n\n\n\n