Roadmaps Security roadmaps AI and machine learning security

Machine Learning Security

Understand how machine learning models are attacked, through their data, their inputs and their outputs, and how to make them robust and private.

Estimated time: 15–26 months · At about 10 hours a week.

Offensive skills are for authorised testing only: your own lab, a practice platform, or a system whose owner has given you written permission. Testing anything else is a crime in most countries.

Learning path

Click a topic to see what to learn and where. Mark topics as you go; your progress is saved in this browser only.

  • Core topic
  • Optional
  1. Beginner · 2–3 months ML foundations and the AI threat landscape
  2. Intermediate · 3–5 months Attacking and defending models
  3. Advanced · 4–6 months Privacy, robustness at scale and secure pipelines
  4. Expert · 6–12 months Research, standards and leadership

All topics in detail

BeginnerTime: 2–3 months

ML foundations and the AI threat landscape

Skills

  • Draw an ML pipeline and mark where data, code and models can be tampered with.
  • Describe attacks with the NIST and ATLAS vocabulary.
  • Load and share models safely, avoiding untrusted pickle files.

Hands-on projects and labs

  • Train a small image or text classifier in PyTorch or scikit-learn and write a one-page threat model for it.
  • Map two ATLAS case studies to the tactics and techniques they used.
  • Scan a model file with ModelScan or picklescan and explain what it found.

Done when you can…

  • Explain the difference between evasion, poisoning, extraction and inference attacks.
  • Write a threat model for an ML system that names the attacker, their access and their goal.

Beginner

The ML lifecycle and its attack surface

Data collection, labelling, training, evaluation, deployment and monitoring are each a place an attacker can step in. Draw the pipeline first, then ask who can touch each step.

Resources

Beginner

Threat modelling ML systems

Ask what the attacker knows (white box or black box), what they can change (data, inputs, the model file) and what they want (wrong answers, stolen model, private data).

Resources

Beginner

OWASP AI Exchange threat overview

The OWASP AI Exchange lists the threats to AI systems, from input manipulation to model theft, with the controls for each. A good checklist for your first reviews.

Resources

Beginner

Real attacks: ATLAS case studies

ATLAS documents real incidents, such as evading malware classifiers and copying commercial models. Read a few to see that these attacks happen outside the lab.

Resources

Beginner

Unsafe model files (pickle)

Many model files are Python pickles, and loading one can run any code inside it. Prefer safetensors, and scan model files before loading them.

Resources

BeginnerOptional

Measuring a model honestly

Accuracy on clean test data says little about behaviour under attack. Learn precision, recall and calibration, and why you need a separate test for robustness.

Resources

IntermediateTime: 3–5 months

Attacking and defending models

Skills

  • Generate adversarial examples against your own models with ART.
  • Run a poisoning or backdoor attack in a lab and detect it.
  • Run a membership inference test and explain the privacy risk.
  • Compare a model's clean accuracy and its accuracy under attack.

Hands-on projects and labs

  • Attack an MNIST or CIFAR-10 classifier you trained with FGSM and PGD, then retrain it adversarially and compare.
  • Add a backdoor trigger to a small dataset you control, train on it, and show the trigger working.
  • Run membership inference against an overfitted model and a regularised one, and compare the results.

Done when you can…

  • Show, with numbers, how much an attack lowers a model's accuracy and how much a defence restores.
  • Explain to a data scientist why a model trained on scraped data needs provenance checks.

Intermediate

Black-box and transfer attacks

Attackers often see only the model's answers. They can still attack it by querying it many times, or by attacking a copy and transferring the result.

Resources

  • TextAttack ToolFreeQData (University of Virginia)

Intermediate

Data validation and provenance

Know where every dataset came from, check it for outliers and duplicates, and keep hashes so you can prove what a model was trained on.

Resources

AdvancedTime: 4–6 months

Privacy, robustness at scale and secure pipelines

Skills

  • Train a model with differential privacy and explain the accuracy and privacy trade-off.
  • Assess a federated learning design for poisoning and leakage.
  • Secure a training pipeline end to end, from raw data to registered model.

Hands-on projects and labs

  • Train the same model with and without Opacus and compare accuracy and membership inference results.
  • Simulate a federated setup with Flower and one malicious client, then add a robust aggregation rule.
  • Train a simple malware classifier on EMBER features and try to evade it with feature changes.

Done when you can…

  • Choose and justify a privacy budget for a real use case.
  • Write a robustness and privacy test plan that runs before every model release.

Advanced

Federated learning security

Federated learning trains on data that stays on devices, but clients can send poisoned updates and the updates can leak data. Learn secure aggregation and robust aggregation.

Resources

Advanced

Attacks on security models

Malware, spam and fraud classifiers face attackers who adapt. Learn how attackers evade them and why these models need retraining and red teaming.

Resources

Advanced

Securing the training pipeline

Protect datasets, training jobs, experiment trackers and model registries like production systems: access control, audit logs and signed artefacts.

Resources

Advanced

Monitoring models in production

Watch for drift, unusual query patterns and sudden accuracy drops. They can mean the world changed, or that someone is probing or extracting the model.

Resources

  • MLflow ToolFreeLinux Foundation

ExpertTime: 6–12 months

Research, standards and leadership

Skills

  • Design and run an adaptive attack against a proposed defence.
  • Write organisation-wide standards for ML robustness and privacy.
  • Publish or present original ML security research.

Hands-on projects and labs

  • Reproduce a recent adversarial ML paper, then try an adaptive attack on its defence.
  • Report a real vulnerability in an open-source ML library through its disclosure process or huntr.

Done when you can…

  • Have your research, tools or standards used by others.
  • Lead the security review of a high-risk ML system.

Expert

Disclosing ML vulnerabilities

Model flaws do not fit neatly into CVE. Learn how AI vulnerability databases and bug bounties handle them, and how to report responsibly.

Resources

Expert

Standards and assurance

Turn research into requirements: map controls to the NIST AI RMF, ISO/IEC 42001 and the EU AI Act's robustness duties for high-risk systems.

Resources

Expert

Building an ML security programme

Set the rules for every model team: threat models, safe formats, robustness and privacy tests, and a review before release.

Resources

Overview

Machine learning models learn from data, so anyone who can influence the data, the inputs or the outputs can influence the model. Attackers can poison training data, craft inputs that fool a classifier, copy a model through its API, or pull private training records back out of it.

Machine Learning Security is the study of these attacks and the defences against them: robust training, data checks, privacy techniques such as differential privacy, and careful control over what a model reveals. It sits between data science and security, and you need a working knowledge of both.

Why it matters

Models now make decisions about fraud, malware, faces, loans and medical images, and attacks on them are real, documented and catalogued in MITRE ATLAS. Few people understand both ML and security, so the skill is rare and in demand.

Typical job roles

  • EntryML engineer with a security focus Builds models and adds the basic checks: data validation, safe file formats, access control.
  • Mid-levelAdversarial ML researcher Tests models with evasion, poisoning and privacy attacks and measures how robust they are.
  • Mid-levelAI security engineer Designs defences and monitoring for ML systems in production.
  • SeniorPrivacy engineer (ML) Applies differential privacy, federated learning and data minimisation to training pipelines.
  • LeadPrincipal ML security scientist Sets the research agenda and the organisation's standards for model robustness and privacy.

Prerequisites

  • Python, NumPy and one ML framework such as PyTorch or scikit-learn.
  • Basic linear algebra, probability and calculus: gradients, vectors and distributions.
  • How models are trained and evaluated: loss, overfitting, train and test splits.
  • Security basics: threat models, the CIA triad, and how attackers think.

AI and machine learning Cybersecurity

Tools and technologies

  • Adversarial Robustness Toolbox (ART) Open source Attacks, defences and metrics for evasion, poisoning, extraction and inference.
  • TextAttack Open source Adversarial attacks and data augmentation for NLP models.
  • CleverHans Open source Reference implementations of adversarial example attacks.
  • Opacus Open source Train PyTorch models with differential privacy.
  • TensorFlow Privacy Open source Differential privacy and privacy testing for TensorFlow.
  • OpenDP Open source Open-source differential privacy library.
  • Flower Open source Framework for federated learning.
  • ModelScan Open source Scans model files for unsafe code.
  • PyTorch Open source The most common framework for ML research.

Certifications

Take them in roughly this order. Costs and details for the ones marked with a link are on the Certifications page.

  1. Intermediate GIAC Machine Learning Engineer (GMLE) GIACApplied machine learning for security teams.
  2. Intermediate AWS Certified Machine Learning Engineer – Associate Amazon Web ServicesShows you can build and run ML in production.Cost and exam details
  3. Advanced AAISM (AI Security Management) ISACAFor AI security management roles, after CISSP or CISM.Cost and exam details

Resources

Frameworks and standards

  • MITRE ATLAS ATT&CK-style knowledge base of attacks on AI and machine learning systems, with real case studies.
  • NIST AI Risk Management Framework (AI RMF) A voluntary framework to map, measure, manage and govern the risks of AI systems.
  • OWASP GenAI Security Project Home of the OWASP Top 10 for LLM Applications and guidance on securing generative and agentic AI.
  • ISO/IEC 42001 The international standard for an AI management system, the AI counterpart to ISO/IEC 27001.
  • EU AI Act The EU law that regulates AI by risk level, including security and robustness duties for high-risk systems.

All frameworks and standards

Career path

A common progression. Titles vary between companies.

  1. Data scientist, ML engineer or security engineer0–2 years
  2. ML engineer with a security focus2–4 years
  3. AI security engineer or adversarial ML researcher4–7 years
  4. Principal ML security scientist8+ years

Related domains to move into

All security roadmaps Back to top

Last reviewed: . Found a mistake, or want a roadmap written sooner? Contact