AML.T0002
Acquire Public AI Artifacts

MITRE source definition

Adversaries may search public sources, including cloud storage, public-facing services, and software or data repositories, to identify AI artifacts. These AI artifacts may include the software stack used to train and deploy models, training and testing data, model configurations and parameters. An adversary will be particularly interested in artifacts hosted by or associated with the victim organization as they may represent what that organization uses in a production environment. Adversaries may identify artifact repositories via other resources associated with the victim organization (e.g. [Search Victim-Owned Websites](/techniques/AML.T0003) or [Search Open Technical Databases](/techniques/AML.T0000)). These AI artifacts often provide adversaries with details of the AI task and approach.

AI artifacts can aid in an adversary's ability to [Create Proxy AI Model](/techniques/AML.T0005). If these artifacts include pieces of the actual model in production, they can be used to directly [Craft Adversarial Data](/techniques/AML.T0043). Acquiring some artifacts requires registration (providing user details such as an email address or name), AWS keys, or written requests, and may require the adversary to [Establish Accounts](/techniques/AML.T0021).

Artifacts might be hosted on victim-controlled infrastructure, providing the victim with some information on who has accessed that data.

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

• AML.T0002.000 Datasets
• AML.T0002.001 Models
• AML.T0002.002 AI Agent Configuration

Source-backed defensive context

MITRE mitigations

• AML.M0000 Limit Public Release of Information

MITRE case studies

• AML.CS0001 Botnet Domain Generation Algorithm (DGA) Detection Evasion · Exercise
• AML.CS0006 ClearviewAI Misconfiguration · Incident
• AML.CS0011 Microsoft Edge AI Evasion · 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.