Study guide

10.4 MITRE ATLAS: Adversarial Threat Landscape for AI Systems

CompTIA SecAI+ CY0-001

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: AI and Machine Learning Foundations

1.1 Core AI/ML Paradigms: Supervised, Unsupervised, and Reinforcement Learning 1.2 Deep Learning Architectures and Neural Network Fundamentals 1.3 Foundation Models, Large Language Models (LLMs), and Tokenization 1.4 Prompting, Data Security, and the AI Lifecycle

2 Chapter 2: Modern AI System Architectures in Security

2.1 Embeddings, Vector Spaces, and Vector Databases 2.2 Retrieval-Augmented Generation (RAG) Architectures and Data Flow 2.3 Autonomous AI Agents, Tool Execution, and Orchestration

3 Chapter 3: Adversarial Machine Learning & Evasion Attacks

3.1 Adversarial Evasion Attacks and Perturbations 3.2 Defenses Against Evasion and Adversarial Robustness 3.3 Data Poisoning and Backdoor Attacks

4 Chapter 4: Model Privacy, Confidentiality & Inversion Attacks

4.1 Model Inversion and Training Data Extraction 4.2 Membership Inference Attacks and Differential Privacy 4.3 Model Theft, Extraction, and IP Protection

5 Chapter 5: LLM Vulnerabilities & CY0-001 OWASP 2023-24 Taxonomy (Part 1)

5.1 CY0-001 / OWASP 2023-24 LLM01: Prompt Injection 5.2 CY0-001 / OWASP 2023-24 LLM02 & LLM07: Output and Plug-ins 5.3 CY0-001 / OWASP 2023-24 LLM03 & LLM05: Poisoning and Supply Chain 5.4 CY0-001 / OWASP 2023-24 LLM04 & LLM06: DoS and Disclosure

6 Chapter 6: CY0-001 OWASP 2023-24 Taxonomy (Part 2) & Secure MLOps

6.1 CY0-001 / OWASP 2023-24 LLM08-LLM10: Agency, Overreliance, and Theft 6.2 Secure MLOps Pipeline Architecture and Hardening 6.3 Runtime AI Monitoring, Guardrails, and Drift Detection 6.4 AI Access, Data, Input, Output, and Audit Controls 6.5 AI Attack Types, Evidence, and Compensating Controls

7 Chapter 7: AI in Threat Detection and SOC Automation

7.1 AI for SOC Alert Triage and Incident Prioritization 7.2 Anomaly Detection and Behavioral Analytics (UEBA) 7.3 AI-Driven Phishing Detection and Email Security

8 Chapter 8: AI in Threat Intelligence, Hunting & Vulnerability Management

8.1 Cyber Threat Intelligence (CTI) Enrichment and Summarization 8.2 AI-Assisted Threat Hunting and Query Generation 8.3 AI in Secure Code Review and Vulnerability Detection 8.4 AI Security Tools, Attack Discovery, and Workflow Automation

9 Chapter 9: Operational Risks and Limitations of AI-Assisted Security

9.1 Hallucinations, Confabulation, and False Positives in SOC AI 9.2 Model Degradation: Data Drift, Concept Drift, and Monitoring Metrics 9.3 Dual-Use Risks: Adversary Exploitation of AI

10 Chapter 10: AI Risk Frameworks, Regulations & Standards

10.1 NIST AI Risk Management Framework (AI RMF 1.0) 10.2 ISO/IEC 42001 and International AI Standards 10.3 The EU AI Act and Global Legal Requirements 10.4 MITRE ATLAS: Adversarial Threat Landscape for AI Systems

11 Chapter 11: AI Red Teaming, Ethics & Enterprise Governance

11.1 AI Red Teaming and Adversarial Probing Methodologies 11.2 Transparency, Model Documentation, and Explainability 11.3 Enterprise AI Governance, Acceptable Use Policies & Data Privacy 11.4 Governance Roles, Risk Taxonomies, and Compliance Operations

10.4 MITRE ATLAS: Adversarial Threat Landscape for AI Systems

Key Takeaways Explain This Topic AI

MITRE ATLAS is a living knowledge base of adversary tactics, techniques, sub-techniques, mitigations, and case studies for AI-enabled systems, organized in a form familiar to MITRE ATT&CK users.

The official ATLAS 2026.08 data contains 16 tactics; counts and identifiers can change, so production mappings must record the ATLAS release or retrieval date.

Current mappings include Evade AI Model (AML.T0015), Training Data Poisoning (AML.T0020), LLM Prompt Injection (AML.T0051), and Exfiltration via AI Inference API (AML.T0024).

Model inversion and extraction are sub-techniques under AML.T0024: Infer Training Data Membership (.000), Invert AI Model (.001), and Extract AI Model (.002).

Current mitigation identifiers use the AML.M0000 series, including Predictive AI Output Obfuscation (AML.M0002), Predictive AI Model Hardening (AML.M0003), query limits (AML.M0004), and access control for models and data at rest (AML.M0005).

Last updated: September 2026

10.4 MITRE ATLAS: Adversarial Threat Landscape for AI Systems

MITRE ATLAS is a living, publicly available knowledge base for adversary behavior involving AI systems. It uses the same basic reasoning pattern as MITRE ATT&CK: a tactic describes why an adversary acts, a technique describes how, a sub-technique supplies more specific behavior, a mitigation describes risk reduction, and a case study records observed or demonstrated activity. ATLAS complements ATT&CK; many incidents need both conventional enterprise techniques and AI-specific techniques.

Version the matrix

ATLAS changes as the field develops. The official ATLAS data release 2026.08 , checked for this review, contains 16 tactics, 178 techniques and sub-techniques, 37 mitigations, and 68 case studies. Treat those counts as a dated snapshot, not permanent exam facts. Record the version or retrieval date in a threat model and look up identifiers in current official data before using them in an incident report.

The 16 current tactics are:

  • Reconnaissance
  • Resource Development
  • Initial Access
  • AI Model Access
  • Execution
  • Persistence
  • Privilege Escalation
  • Defense Evasion
  • Credential Access
  • Discovery
  • Lateral Movement
  • Collection
  • AI Attack Staging
  • Command and Control
  • Exfiltration
  • Impact

These names show how ATLAS combines ordinary intrusion activity with AI-specific objectives. AI Model Access concerns access needed to interact with or acquire a model. AI Attack Staging covers preparation of artifacts or capabilities used against AI. Do not rely on older labels such as “ML Model Access” without recording the historical version.

High-value current mappings

Use the exact current names and hierarchy:

Behavior Current ATLAS mapping Meaning

Search public analysis for AI weaknesses Search Open AI Vulnerability Analysis (AML.T0001) Reconnaissance using public vulnerability analysis; it is not model inversion

  • Craft manipulated input Craft Adversarial Data (AML.T0043) Prepare adversarial data for a target
  • Avoid the intended decision Evade AI Model (AML.T0015) Cause an AI model to misclassify or otherwise evade
  • Manipulate model behavior Manipulate AI Model (AML.T0018) Parent technique; Poison AI Model is AML.T0018.000

Corrupt training data Training Data Poisoning (AML.T0020) Insert or modify training data to influence the trained model

Inject LLM instructions LLM Prompt Injection (AML.T0051) Parent technique with Direct (.000), Indirect (.001), and Triggered (.002) prompt injection

Bypass LLM safeguards LLM Jailbreak (AML.T0054) Evade model safeguards; distinct from the delivery path of prompt injection

Hide a prompt's meaning LLM Prompt Obfuscation (AML.T0068) Obfuscate content to bypass inspection or safeguards

Cause sensitive generation LLM Data Leakage (AML.T0057) Obtain sensitive data through LLM behavior

Abuse an inference interface to remove information Exfiltration via AI Inference API (AML.T0024) Parent technique for inference-based exfiltration

Under AML.T0024, Infer Training Data Membership (AML.T0024.000) estimates whether a record was in training, Invert AI Model (AML.T0024.001) reconstructs information about training data or features, and Extract AI Model (AML.T0024.002) approximates or recovers model functionality. Older material may use AML.T0001 for inversion or use AML.T0024 as model extraction alone; those mappings are obsolete in the current data.

Prompt injection and jailbreaking also differ. Direct or indirect describes where hostile instructions enter. Jailbreaking describes bypassing safeguards. One event may map to AML.T0051.001 for indirect injection and AML.T0054 when the content also bypasses safeguards.

Mitigations

Current ATLAS mitigation identifiers use AML.M0000-series identifiers, not the obsolete AML.M1000 series. Examples include:

AML.M0001 — Limit Model Artifact Release: reduce unnecessary release of weights or artifacts.

AML.M0002 — Predictive AI Output Obfuscation: reduce useful precision or detail exposed by predictive outputs where risk and business need permit.

AML.M0003 — Predictive AI Model Hardening: make predictive models more robust against adversarial use.

AML.M0004 — Limit AI Service Query Volume and Rate: constrain repeated queries used for extraction, inference, or resource abuse.

AML.M0005 — Control Access to AI Models and Data at Rest: restrict and monitor access to stored model artifacts and data.

A mitigation is selected from the actual attack path and system constraints. Output obfuscation may reduce information available for inversion or extraction, but it can reduce legitimate explainability or utility. Query limits slow abuse but do not correct excessive tool permissions. Access control at rest does not validate hostile runtime input. Combine controls and document residual risk.

Threat-modeling workflow

First draw the system: training and evaluation data, artifact registry, deployment, inference APIs, RAG stores, users, agents, tools, logs, and suppliers. Identify entry points and the attacker's required access. Map only behaviors supported by evidence. Then pair mappings with preventive, detective, response, and recovery controls.

For example, a malicious document retrieved by an agent instructs it to query a customer database and send records externally. Evidence supports Indirect LLM Prompt Injection (AML.T0051.001) . If the content bypasses behavioral safeguards, AML.T0054 may also apply. Conventional credential, collection, and exfiltration behaviors may map to ATT&CK, while ATLAS captures the AI-specific path. Controls include isolating untrusted content, least-privilege agent identity, server-side authorization, tool allowlists, destination controls, human confirmation, and complete tool-call logging.

For an inference API that exposes detailed scores, repeated queries could support AML.T0024 sub-techniques. Authentication, AML.M0004 rate limits, anomaly detection, AML.M0002 output obfuscation where acceptable, and contractual controls can reduce risk. Preserve request identity, timestamps, inputs, outputs, model version, and rate-limit decisions for investigation.

Exam method

In a scenario, identify the adversary's objective before choosing the identifier. Reconstructing training information points to inversion; deciding whether a record was present points to membership inference; cloning model behavior points to extraction; changing training examples points to poisoning; and manipulating inference input to avoid detection points to evasion. If a distractor gives a familiar name with an obsolete ID, prefer the current official mapping unless the question explicitly specifies an older ATLAS version.

Loading diagram... MITRE ATLAS AI Attack Lifecycle and Enterprise Defensive Architecture