How Hackers Can Breach CI/CD Systems - Security Vulnerabilities and Mitigation

How Hackers Can Breach CI/CD Systems - Security Vulnerabilities and Mitigation

OWASP Foundation via YouTube Direct link

CONTINUOUS DELIVERY CONTINUOUS DEPLOYMENT

2 of 33

2 of 33

CONTINUOUS DELIVERY CONTINUOUS DEPLOYMENT

Class Central Classrooms beta

YouTube videos curated by Class Central.

Classroom Contents

How Hackers Can Breach CI/CD Systems - Security Vulnerabilities and Mitigation

Automatically move to the next video in the Classroom when playback concludes

  1. 1 Intro
  2. 2 CONTINUOUS DELIVERY CONTINUOUS DEPLOYMENT
  3. 3 The IDE Leaks!
  4. 4 The BAD ROLE Granularity!
  5. 5 The DEV Machine as only source code se
  6. 6 All Libraries Allowed!
  7. 7 SECRETS & LEAKS
  8. 8 Control Artefacts Repository
  9. 9 The ENVIRONMENT Leak! (1/2)
  10. 10 The ENV Leak! (2/2)
  11. 11 A reverse Shell in the Pipeline
  12. 12 The Evil GitHub Actions!
  13. 13 The mighty CI BOT
  14. 14 The EVIL AGENT (1/3)
  15. 15 The EVIL AGENT (3/3)
  16. 16 The DOCKER HUB Leak!
  17. 17 Keep API Safe!
  18. 18 The SOURCE CODE ransomware!
  19. 19 The Fat DOCKER!
  20. 20 The evil DOCKER twin!
  21. 21 The Greedy Service consumer!
  22. 22 Run FREE Internet!
  23. 23 The Trojan Jar!
  24. 24 The ZIP BOMB (2/4)
  25. 25 The ZIP BOMB (4/4)
  26. 26 Memory BOMB (3/5)
  27. 27 Memory BOMB (5/5)
  28. 28 Fork BOMB! (1/2)
  29. 29 Is your API Honest!? (1/2)
  30. 30 Keep SECRETS safe!
  31. 31 The Evil Alias!
  32. 32 The Shared infra! (1/2)
  33. 33 The TIP Of the iceberg

Never Stop Learning.

Get personalized course recommendations, track subjects and courses with reminders, and more.

Someone learning on their laptop while sitting on the floor.