MITRE ATLAS 2026.09 / technique reference
AML.T0085.000
RAG Databases
MITRE source definition
Adversaries may prompt the AI service to retrieve data from a RAG database. This can include the majority of an organization's internal documents.
Source modified 2026-05-27. Reproduced from the pinned ATLAS release; inline technique links resolve to local reference pages.
Parent, sub-techniques and ATT&CK references
Source-backed defensive context
MITRE mitigations
- AML.M0024 AI Telemetry Logging
- AML.M0026 Privileged AI Agent Permissions Configuration
- AML.M0027 Single-User AI Agent Permissions Configuration
- AML.M0032 Segmentation of AI Agent Components
MITRE case studies
- AML.CS0037 Data Exfiltration via Agent Tools in Copilot Studio · Exercise
- AML.CS0059 EchoLeak: Zero-Click Prompt Injection Targeting M365 Copilot for Data Exfiltration · Exercise
These are explicit source relationships, not independently reproduced incidents or validated detection coverage.
Simulation and telemetry boundary
This is a technique reference page, not a runnable simulation. No ATLAS-specific telemetry mapping, local attack execution or detector validation is asserted. MITRE maturity describes its source evidence, not a 1200km lab result.
For broader context—not technique-specific control mappings—see AI Security, AI Security Course, and detection-validation methodology.
Provenance and attribution
Immutable MITRE ATLAS source · Import provenance · Attribution and transformation notice · Apache License 2.0
Copyright 2021-2026 MITRE. Source text and explicit relationships are retained; navigation, formatting and local links are provided by 1200km.
No explicit relationship in this pinned source.