Why attack a thousand customers when you can attack one build system
Reframes the CI/CD pipeline itself as an attack target and walks the SolarWinds build-system compromise as the canonical example.
Speaker notes
- Reframe the whole module's premise clearly: everything before this module focused on securing the application — its code, dependencies, containers, secrets. This module asks a different question: what if the attacker doesn't target your application at all, but the machinery that builds and deploys it?
- Walk why this is such a high-leverage attack for a real adversary: compromising one popular library's build process or one company's CI/CD pipeline means the attacker doesn't need to individually breach each of thousands of downstream customers — those customers voluntarily and trustingly pull in the poisoned artifact themselves, believing it's legitimate.
- SolarWinds (disclosed December 2020) is the canonical, board-level example worth citing by name: attackers compromised the build system itself, injected malicious code into a legitimate, validly-signed update, and roughly 18,000 organizations — including US government agencies and Fortune 500 companies — installed it trusting it completely. The core lesson: the attackers never needed a bug in SolarWinds' product code, because they compromised the process that builds and signs the product instead.
Deck map
01
Make security everyone's job
02
Six modules, one continuous defense
03
Security stops being a gate at the end
04
Shift-left: catch it while it's still cheap
05
Think like an attacker, on purpose
06
The cloud secures the cloud, you secure what's inside it
07
Turn the policy PDF into an enforced rule
08
Tooling alone doesn't make you DevSecOps
09
SAST, DAST, SCA: three different questions
10
SAST reads your code without ever running it
11
DAST attacks the running app like a real attacker would
12
The vulnerability three packages deep
13
CVSS tells you how bad, not whether it can reach you
14
No single tool covers the whole OWASP Top 10
15
A container image is more than your app
16
One image scan doesn't see your whole cluster
17
Five changes separate a throwaway image from a liability
18
A container is not a lightweight VM
19
What's inside the image isn't how it's run
20
Kubernetes adds a new set of who-can-do-what questions
21
Kubernetes trusts every pod by default
22
Enforce it automatically, then watch for what slips through
23
Two more names worth knowing: Kyverno and kube-bench
24
One leaked secret bypasses every other control
25
Catch it before the commit, know what to do if it leaks anyway
26
Why environment variables aren't a secrets manager
27
Every app instance gets its own credential, and it expires on its own
28
Not every secret needs a Vault server
29
Long-lived keys are a secret you have to store somewhere
30
Something has to be the first credential
31
Why attack a thousand customers when you can attack one build system
32
A misconfigured trigger can hand your secrets to a stranger's fork
33
A mutable version tag is a promise the maintainer can break
34
Scan the infrastructure definition before it's ever provisioned
35
Know exactly what's inside, prove exactly where it came from
36
One diagram, every module, in the order it runs
37
Passing an audit is not the same as being secure
38
Turn the compliance checklist into a real, running scan
39
Five functions, and which framework to start with
40
ISO 27001 asks for a system, PCI-DSS asks for specific controls
41
Compliance is largely DevSecOps, formalized
42
Every tool from this course, in one place
43
Sixty seconds before the interview
44
What you should be able to explain now