Risk · R-073 · Adversarial ML & Model Integrity
Model inversion and training data extraction
An attacker reconstructs training records, or close likenesses of them, from a model's outputs or its weights.
- Severity
- High
- Audience
- Heads-of · Practitioner
- Frameworks
- AML.T0137.002 · AML.T0137.003 · Data Privacy · Article 32
- Responsible AI domain
- Lifecycle stage
- Reviewed
- 2026-11-10
What it is
Models retain more of their training data than is commonly assumed. Inversion reconstructs representative inputs for a given output, such as a recognisable face for a named identity. Extraction recovers records the model has memorised, by prompting it in ways that cause it to reproduce them. This entry concerns deliberate recovery by an adversary. Reproduction of training data in ordinary use, with no attack, is covered under Data Protection & Privacy.
How it happens
- A generative model is prompted with the start of a memorised record and completes it.
- Outputs are optimised step by step toward a target class to reveal what the model associates with it.
- An attacker with the weights analyses them directly.
- Rare or repeated items in training data are memorised and are the easiest to recover.
Why it matters
The model becomes a copy of part of its training data, held outside the controls on that data and possibly distributed to customers or the public. Recovery of personal data is a breach with the duties that follow, and it cannot be remedied without retraining.
Warning signs
- The model was trained on raw personal or confidential records.
- Outputs occasionally contain verbatim text nobody supplied.
- Fine-tuning used a small dataset for many passes.
- The weights are shared with parties who may not see the training data.
Who owns it
The data owner is accountable for what was used in training. The model owner is accountable for testing what can be recovered. The data protection officer assesses the risk before personal data is used.
In practice
A firm fine-tunes a language model on its complaint correspondence to draft replies. A user of the drafting tool finds that beginning a prompt with a common opening line causes the model to continue with another customer's name, address and account details. The same pattern generalises to any model trained on records that should not be disclosed to its users.
Mitigating controls
Primary controls
- Personal data redaction and pseudonymisation Preventive
- Removes personal data before training so there is less to extract. Personal data is removed, masked or pseudonymised before data is used for training, evaluation or logging, unless it is needed and the need is recorded, and the result is tested.
- Privacy-preserving training techniques Preventive
- Reduces memorisation of individual training records. Where training data is personal or confidential, techniques that limit how much a model retains about any single record are applied, and the remaining exposure is measured.
Supporting controls
- AI red teaming Detective
- Attempts extraction before release. People skilled in attacking AI systems try to make the system fail as an adversary would, before release and periodically, and their findings are tracked to closure.
Compensating controls
- Output validation and guardrails Preventive
- Where retraining is impractical, filters outputs that reproduce sensitive records. Every model output is validated against a schema and sanitised by deterministic code before any downstream system, tool or user interface acts on it.
Framework and clause references
| Framework | Clause | Title |
|---|---|---|
| MITRE ATLAS | AML.T0137.002 | Training Data Information from AI Models: Invert AI Model The corresponding technique. |
| MITRE ATLAS | AML.T0137.003 | Training Data Information from AI Models: Extract Memorized Data Extraction of memorised training data. |
| NIST Generative AI Profile (NIST AI 600-1) | Data Privacy | Data Privacy The data privacy risk. |
| UK General Data Protection Regulation | Article 32 | Security of processing Security of processing. |
Sources
- NIST Generative AI Profile NIST · framework
- MITRE ATLAS MITRE · framework
Related terms
How to cite
Axiom Verity (2026). Model inversion and training data extraction. Reference Library, R-073. https://axiom-verity.com/risks/model-inversion-and-training-data-extraction. Reviewed 2026-11-10.
Found an error or a better source? Report a correction.