AML.T0018.000
Manipulate AI Model: Poison AI Model
Adversaries may poison a model by directly manipulating its weights, training the model on poisoned data, further fine-tuning the model, or otherwise interfering with its training process.
- Tactic AI Attack Adaptation
- Tactic Persistence
- Maturity: Demonstrated
- Predictive AI
- Generative AI
- Agentic AI
- Control Access to AI Models and Data at RestAML.M0005
Establish access controls on internal model registries and limit internal access to production models. Limit access to training data only to approved users.
Policy
- Sanitize Training DataAML.M0007
Detect, quarantine, and remove or remediate poisoned data before it is used to train an AI model. Apply screening when datasets are acquired or updated, and before new data is incorporated into active learning workflows.
Technical - AI
- Validate AI ModelAML.M0008
Evaluate AI models against defined functional requirements before deployment and throughout their operational lifecycle. Validate newly trained or acquired models and repeat evaluation after fine-tuning, model updates, or changes to the conditions in which the model is used.
Technical - AI
- Code SigningAML.M0013
Enforce binary and application integrity with digital signature verification to prevent untrusted code from executing. Adversaries can embed malicious code in AI software or models. Developers should also cryptographically sign SBOM and AIBOM components that track model or data provenance.
Technical - Cyber
- Verify AI ArtifactsAML.M0014
Verify the integrity and authenticity of AI artifacts before importing, loading, or deploying them. Artifacts may include model weights and checkpoints, datasets, tokenizers, model configurations, prompt templates, and agent configuration files.
Technical - Cyber
- Maintain an AI Bill of MaterialsAML.M0023
Create and maintain an AI Bill of Materials (AI BOM) that identifies the components and dependencies used to build, evaluate, and operate an AI-enabled system. Include models and checkpoints, datasets, software packages, inference runtimes, container images, and agent configurations including system instructions and connected tools and data sources.
Policy
- Maintain AI Dataset ProvenanceAML.M0025
Maintain a detailed history of datasets used for AI applications. The history should include information about the dataset's source as well as a complete record of any modifications.
Technical - AI
- AI Red TeamAML.M0035
Establish an AI red team responsible for conducting recurring, authorized, and threat-informed red-teaming exercises to identify and remediate vulnerabilities in AI-enabled systems before deployment and throughout operation.
Policy · Technical - AI · Technical - Cyber
From MITRE ATLAS 2026.10, Copyright 2021-2026 MITRE, Apache License 2.0.