Welcome to the WGU BSAISEC E178 Implementing Adversarial Training - Section 2 hands-on lab!
A classifier that performs well on ordinary inputs can still be pushed into the wrong answer by an attacker who perturbs those inputs deliberately. There is more than one way to defend it, and the three in this lab act in three different places: on the model's weights, on the traffic reaching the model, and on the data the model was trained from.
Adversarial training generates the attacker's examples, labels them with the answer the model should have given, and retrains on them. The detail that makes it a defense rather than an attack is the label: attach the label the attack was trying to force and the same procedure becomes clean-label poisoning. A detection-based defense leaves the model alone and puts a detector in front of it, flagging a suspicious transaction and stopping it before the model decides. Defensive data augmentation uses a pre-trained GAN to expand a training set that has too few examples of the class the model most needs to recognize, provided the synthetic examples survive validation against real data.
Each one is cheap to claim and harder to justify. This lab asks you to act as a defender for a financial services fraud detection classifier, build all three against the same system and the same attack, and report honestly on what each is worth, what it costs, and what it fails to cover.
You will work in a Jupyter notebook environment with the Adversarial Robustness Toolbox (ART), PyTorch, and standard data science libraries preinstalled, together with a preconfigured fraud detection dataset, a trained baseline classifier, and a pre-trained GAN.
By completing this lab you will:
Cardinal Trust Financial's fraud detection classifier is the system under test. The dataset, the baseline classifier, and the pre-trained GAN supplied in the lab environment are preloaded; refer to the task notebook for details on each and for the instructions for every section.
Submit the executed notebook, including:
Your submission should include the executed notebook and exported reports, along with any supporting evidence generated in the lab environment, such as figures and metrics tables.