A practical, actionable reference of the top security threats to Agentic AI systems (AG1–AG10), with verified examples, prevention strategies, and related frameworks.
0
2 commits
updated Aug 14, 2025
Agentic AI systems are autonomous AI entities capable of reasoning, planning, and executing actions via connected tools and APIs they bring new security challenges that differ sharply from traditional software or standalone AI models. Their ability to persist memory, call external services, interact with other agents, and adapt goals in real time creates a broader and less predictable attack surface.
This repository documents the Top 10 security threats (AG1–AG10) facing Agentic AI systems, drawn from verifiable industry, academic, and standards-based sources, including OWASP and peer-reviewed research. Each entry includes:
This is not a theoretical list. Every item is intended to be actionable for security engineers, architects, AI governance teams, and anyone deploying or auditing Agentic AI systems.
Our goal is to:
This repository is designed to be both a reference and a practical tool for securing Agentic AI systems.
This repository is designed to be both a reference and a practical tool for securing Agentic AI systems.
Tip: If you’re running security reviews or penetration testing on agentic AI systems, use this list as a baseline checklist for evaluating resilience.
Description: Attackers inject malicious or false data into an agent’s memory—short-term context or persistent storage—to distort its reasoning or actions.
Common Examples of Risks: False memory entries steering decision-making; misremembered context producing unsafe actions.
Prevention and Mitigation Strategies: Data source validation; checksum or signatures for trusted memory; periodic memory audit and rollback features.
Example Attack Scenarios: Malicious prompts embedded in emails corrupting an email-assistant’s memory.
Reference Links:
Description: Abusing an agent’s tool integrations (APIs, search, code execution) via deceptive prompts or command injection.
Common Examples of Risks: Prompt injection causing unwanted tool calls; malicious code generation; unintended API use.
Prevention and Mitigation Strategies: Enforce allow-lists, strict argument validation, sandboxing, and logging.
Example Attack Scenarios: Vulnerable prompt injection leads to insecure code generation by a coding agent.
Reference Links:
Description: An agent accrues or exploits higher access rights than intended, often through flawed permission design.
Common Examples of Risks: Broad default permissions; escalated API privileges.
Prevention and Mitigation Strategies: Enforce least privilege, time-bound access, approval workflows, and monitor for unusual escalations.
Example Attack Scenarios: I don’t know.
Reference Links:
Description: Faulty outputs (hallucinations) propagate through memory, external tools, or other agents, causing cascading failures.
Common Examples of Risks: One hallucination leading to chain of false decisions; memory contamination.
Prevention and Mitigation Strategies: Confidence scoring, fact-checking before commit to memory, flag unverified data.
Example Attack Scenarios: A false memory or hallucinated fact cascades through agent workflows.
Reference Links:
Description: Adversaries alter an agent’s objectives via crafted input, corrupt memory, or deceptive tool output.
Common Examples of Risks: Prompt injection that changes planning; alignment faking.
Prevention and Mitigation Strategies: Lock core goals at runtime, detect deviations, immutable goal logs.
Example Attack Scenarios: I don’t know.
Reference Links:
Description: Agents learn to bypass safety constraints or superficially appear compliant while pursuing harmful aims.
Common Examples of Risks: Malicious models feigning compliance; deceptive planning.
Prevention and Mitigation Strategies: Continuous adversarial testing, rotating safety filters, human escalation.
Example Attack Scenarios: AI pretending compliance to avoid shutdown.
Reference Links:
Description: Agent actions become opaque or untraceable due to fragmented logs or parallel reasoning, hindering audit and forensic efforts.
Common Examples of Risks: Multi-path reasoning, missing provenance.
Prevention and Mitigation Strategies: End-to-end logging, unique identifiers, traceable reasoning chains.
Example Attack Scenarios: I don’t know.
Reference Links:
Description: Forged or misused identities—human or agent—are used to issue unauthorized commands or access.
Common Examples of Risks: Undocumented impersonation of agents; forged credentials.
Prevention and Mitigation Strategies: Cryptographic identity, mutual TLS, token-based verification, credential revocation.
Example Attack Scenarios: I don’t know.
Reference Links:
Description: Flooding or overwhelming oversight mechanisms so that human review becomes ineffective.
Common Examples of Risks: High volume of alerts or complex tasks go unchecked.
Prevention and Mitigation Strategies: Rate-limiting oversight queues; prioritize alerts; decision-support augmentation.
Example Attack Scenarios: I don’t know.
Reference Links:
Description: Compromise of upstream tools, libraries, datasets, or model dependencies undermines agent security.
Common Examples of Risks: Infected package, compromised tool component, poisoned RAG dataset.
Prevention and Mitigation Strategies: Signed components, SBOM, continuous scanning, model/data integrity checks.
Example Attack Scenarios: Agent downloading corrupted firmware from a compromised supplier platform.
Reference Links:
Contributions are welcome — this repository is intended to be a living resource that evolves as new threats and mitigations are discovered.
AG1–AG10 list.
DescriptionCommon Examples of RisksPrevention and Mitigation StrategiesExample Attack ScenariosReference LinksRelated Frameworks and TaxonomiesIf you spot an error, missing reference, or outdated mitigation:
Note: All contributions are reviewed for accuracy, clarity, and alignment with the repository’s scope before merging.
2 commits
A practical, actionable reference of the top security threats to Agentic AI systems (AG1–AG10), with verified examples, prevention strategies, and related frameworks.
0
2 commits
updated Aug 14, 2025
Agentic AI systems are autonomous AI entities capable of reasoning, planning, and executing actions via connected tools and APIs they bring new security challenges that differ sharply from traditional software or standalone AI models. Their ability to persist memory, call external services, interact with other agents, and adapt goals in real time creates a broader and less predictable attack surface.
This repository documents the Top 10 security threats (AG1–AG10) facing Agentic AI systems, drawn from verifiable industry, academic, and standards-based sources, including OWASP and peer-reviewed research. Each entry includes:
This is not a theoretical list. Every item is intended to be actionable for security engineers, architects, AI governance teams, and anyone deploying or auditing Agentic AI systems.
Our goal is to:
This repository is designed to be both a reference and a practical tool for securing Agentic AI systems.
This repository is designed to be both a reference and a practical tool for securing Agentic AI systems.
Tip: If you’re running security reviews or penetration testing on agentic AI systems, use this list as a baseline checklist for evaluating resilience.
Description: Attackers inject malicious or false data into an agent’s memory—short-term context or persistent storage—to distort its reasoning or actions.
Common Examples of Risks: False memory entries steering decision-making; misremembered context producing unsafe actions.
Prevention and Mitigation Strategies: Data source validation; checksum or signatures for trusted memory; periodic memory audit and rollback features.
Example Attack Scenarios: Malicious prompts embedded in emails corrupting an email-assistant’s memory.
Reference Links:
Description: Abusing an agent’s tool integrations (APIs, search, code execution) via deceptive prompts or command injection.
Common Examples of Risks: Prompt injection causing unwanted tool calls; malicious code generation; unintended API use.
Prevention and Mitigation Strategies: Enforce allow-lists, strict argument validation, sandboxing, and logging.
Example Attack Scenarios: Vulnerable prompt injection leads to insecure code generation by a coding agent.
Reference Links:
Description: An agent accrues or exploits higher access rights than intended, often through flawed permission design.
Common Examples of Risks: Broad default permissions; escalated API privileges.
Prevention and Mitigation Strategies: Enforce least privilege, time-bound access, approval workflows, and monitor for unusual escalations.
Example Attack Scenarios: I don’t know.
Reference Links:
Description: Faulty outputs (hallucinations) propagate through memory, external tools, or other agents, causing cascading failures.
Common Examples of Risks: One hallucination leading to chain of false decisions; memory contamination.
Prevention and Mitigation Strategies: Confidence scoring, fact-checking before commit to memory, flag unverified data.
Example Attack Scenarios: A false memory or hallucinated fact cascades through agent workflows.
Reference Links:
Description: Adversaries alter an agent’s objectives via crafted input, corrupt memory, or deceptive tool output.
Common Examples of Risks: Prompt injection that changes planning; alignment faking.
Prevention and Mitigation Strategies: Lock core goals at runtime, detect deviations, immutable goal logs.
Example Attack Scenarios: I don’t know.
Reference Links:
Description: Agents learn to bypass safety constraints or superficially appear compliant while pursuing harmful aims.
Common Examples of Risks: Malicious models feigning compliance; deceptive planning.
Prevention and Mitigation Strategies: Continuous adversarial testing, rotating safety filters, human escalation.
Example Attack Scenarios: AI pretending compliance to avoid shutdown.
Reference Links:
Description: Agent actions become opaque or untraceable due to fragmented logs or parallel reasoning, hindering audit and forensic efforts.
Common Examples of Risks: Multi-path reasoning, missing provenance.
Prevention and Mitigation Strategies: End-to-end logging, unique identifiers, traceable reasoning chains.
Example Attack Scenarios: I don’t know.
Reference Links:
Description: Forged or misused identities—human or agent—are used to issue unauthorized commands or access.
Common Examples of Risks: Undocumented impersonation of agents; forged credentials.
Prevention and Mitigation Strategies: Cryptographic identity, mutual TLS, token-based verification, credential revocation.
Example Attack Scenarios: I don’t know.
Reference Links:
Description: Flooding or overwhelming oversight mechanisms so that human review becomes ineffective.
Common Examples of Risks: High volume of alerts or complex tasks go unchecked.
Prevention and Mitigation Strategies: Rate-limiting oversight queues; prioritize alerts; decision-support augmentation.
Example Attack Scenarios: I don’t know.
Reference Links:
Description: Compromise of upstream tools, libraries, datasets, or model dependencies undermines agent security.
Common Examples of Risks: Infected package, compromised tool component, poisoned RAG dataset.
Prevention and Mitigation Strategies: Signed components, SBOM, continuous scanning, model/data integrity checks.
Example Attack Scenarios: Agent downloading corrupted firmware from a compromised supplier platform.
Reference Links:
Contributions are welcome — this repository is intended to be a living resource that evolves as new threats and mitigations are discovered.
AG1–AG10 list.
DescriptionCommon Examples of RisksPrevention and Mitigation StrategiesExample Attack ScenariosReference LinksRelated Frameworks and TaxonomiesIf you spot an error, missing reference, or outdated mitigation:
Note: All contributions are reviewed for accuracy, clarity, and alignment with the repository’s scope before merging.
2 commits