AI security guide · MITRE ATLAS

Cross-system agent lateral movement and execution boundaries

How can an AI agent become a bridge between systems for an attacker? Agents connected to email, tickets, code, chat and cloud become bridges: influence gained in one system can be carried into another through the agent’s tools.

ATLAS v2026.10Last updated
1. Reconnaissance12. Resource Development23. AI Attack Adaptation (this technique)34. Initial Access45. AI Model Access56. Execution (this technique)67. Persistence78. Privilege Escalation (this technique)89. Defense Evasion910. Credential Access1011. Discovery1112. Lateral Movement (this technique)1213. Collection1314. Command and Control1415. Exfiltration1516. Impact16ATLAS4 OF 16 TACTICS
3. AI Attack Adaptation6. Execution8. Privilege Escalation12. Lateral Movement

Why it matters

Traditional segmentation assumes systems talk through defined integrations. A broadly connected agent is an integration with every system at once, driven by natural language.

How it works

  • Influence the agent in a low-trust system (for example a public ticket).
  • Agent carries instructions into a high-trust system (cloud, code repository).
  • Multi-agent setups can propagate prompts between agents.

Curated agent example

Fictional example: an engineering productivity agent

  1. The agent reads public issues and can open pull requests and run CI.
  2. A crafted issue instructs it to add a dependency from an attacker-controlled source.
  3. The agent opens a PR; CI runs with deployment credentials.
  4. Mitigation: separate agents per trust zone; no write to code from agents reading public content; human review of agent PRs.

Fictional and simplified for education.

On AWS: architecture notes

  • Separate agent runtimes and roles per trust zone (public-facing vs internal).
  • Contain agent execution in isolated compute (separate accounts or VPCs) with restricted egress.
  • Restrict which agents may call which other agents.
AWS IAM review bounds what a manipulated agent can do. It does not prove that the agent resists prompt injection.

MITRE ATLAS techniques

  • AML.T0053 AI Agent Tool Invocation

    Execution · Privilege Escalation · Lateral Movement · Maturity: Demonstrated

    Adversaries may use their access to an AI agent to invoke tools the agent has access to. LLMs are often connected to other services or resources via tools to increase their capabilities. Tools may include integrations with other applications, access to public or private data sources, and the ability to execute code.

  • AML.T0118 Autonomous AI Agent Communication

    AI Attack Adaptation · Maturity: Realized

    Autonomous AI agents may exchange operational information with other AI agents, sub-agents, or independent agent runs. Exchanged information may include discoveries, objectives, tasking, capabilities, credentials, constraints, operating rules, task state, targeting information, instructions, or results. Communication enables autonomous AI agents to coordinate activities, share discoveries, delegate work, request assistance, validate results, or revise future actions without requiring a human operator to direct each interaction.

  • AML.T0143 LLM Prompt Propagation

    Lateral Movement · Maturity: Demonstrated

    Adversaries may cause malicious instructions already introduced into an AI-enabled environment to be transferred onward to additional storage locations, agents, applications, or resources where they can influence subsequent AI activity. This extends the attack beyond its initial point of introduction and may allow adversaries to influence additional targets without directly delivering a malicious prompt payload to each one.

  • AML.T0105 Escape to Host

    Privilege Escalation · Maturity: Realized

    Adversaries may break out of a container or virtualized environment to gain access to the underlying host. This can allow an adversary access to other containerized or virtualized resources from the host level or to the host itself. In principle, containerized / virtualized resources should provide a clear separation of application functionality and be isolated from the host environment.

ATLAS mitigations

  • AML.M0032 Segmentation of AI Agent Components

    Define enforceable security boundaries around AI agent tools, data sources, identities, and execution environments. Mediate access through authenticated APIs, isolate code execution via containers or virtual machines, restrict filesystem and network access, and limit tool invocation rates. Build execution environments from clean base images for each run, and do not carry forward any operational state.

  • AML.M0037 AI Agent Authority Expansion Controls

    Limit an AI agent's ability to autonomously acquire additional authorities that expand its effective permissions during execution. The maximum authority available to the agent should be explicitly granted prior to runtime. Additional resources, identities, services, and targets discovered during execution should be treated as outside the authorized boundary unless they are independently validated and added to scope.

  • AML.M0038 AI Agent Scope Drift Detection

    Continuously evaluate whether an AI Agent's planned actions remain consistent with its current authorized objective throughout execution. As autonomous agents interact within a dynamic environment, they may discover or generate intermediate objectives or adapt their strategy based on environment feedback.

Related Enterprise ATT&CK techniques

Controls to prioritize

Cloud Control Explorer →

Common misconceptions

“One powerful agent is simpler and safer to manage.”
Concentrating connections concentrates risk; several narrow agents are easier to bound.

Checklist

  • Map which systems each agent connects
  • Split agents by trust zone
  • Isolate agent execution environments

Run the AI Agent Security Self-Assessment

Related attack scenarios

More AI security guides

References

MITRE ATT&CK® and ATT&CK® are registered trademarks of The MITRE Corporation. ATT&CK data © 2026 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation (ATT&CK v20.1). MITRE ATLAS™ data (v2026.10) © MITRE, used under the Apache License 2.0. Securitain is not affiliated with or endorsed by MITRE. Explanations, scenarios and control mappings on this page are Securitain’s own analysis. Sources and licensing

Stay in the loop

Cloud security insights, early access & compliance updates

Weekly InsightsEarly AccessExpert Content
No spam, everUnsubscribe anytimeWeekly updates
Chat with Securitain