Episode 189 | OWASP Top 10 Part 3: Software Supply Chain Failures — From SolarWinds to Vibe Coding
Streams straight from the publisher. podnod never proxies or re-hosts episode audio.
Almost no one writes an application from scratch anymore, and that's exactly the problem. In Part 3 of our OWASP Top 10 series, Brad Causey and Jordan Natter break down A03: Software Supply Chain Failures, the category that climbed to #3 and topped OWASP's own community survey as the vulnerability organizations worry about most. If your team pulls in third-party libraries, buys SaaS, or lets anyone "vibe code" a project, this episode is for you.
Brad and Jordan cover both sides of supply chain risk: the trusted third-party applications you deploy (SolarWinds being the case that put this category on the map) and the open-source components you pull into your own code without always knowing what's inside. They explain why AI and vibe coding are accelerating the problem, why jQuery is the modern-day Flash, and why "just upgrade the package" is rarely that simple.
From there it gets practical:
- What a Software Bill of Materials (SBOM) is and why you need one
- Transitive dependencies — the packages hiding beneath your packages
- Building security checks into your CI/CD pipeline and shifting left
- Why a flaw caught in static analysis can cost ~$200, while the same flaw found in a pen test can cost $20,000+
- Why a pen test should validate your controls, not be your first line of defense
- How SecurIT360's Project Lantern and ChainGarde automate SBOM analysis against known and actively-exploited vulnerabilities
- A playbook for vetting vendors, writing accountability into contracts, and holding third parties responsible for actually fixing findings
The takeaway: whether you're writing software or buying it, you need a way to inventory your components, check them against known vulnerabilities, and hold your vendors accountable — and most of it you can do with tools and teams you already have.
Part 1 — Broken Access Control, IDOR & CORS: https://youtu.be/BwYJ-kZ3XaY
Part 2 — Security Misconfigurations: https://youtu.be/Po8H140BijE
Need a web app pen test? SecurIT360 | Cybersecurity From Every Angle
More content: https://offsec.blog
Blog: https://offsec.blog/
Youtube: https://www.youtube.com/@cyberthreatpov
Twitter: https://x.com/cyberthreatpov
Follow Spencer on social ⬇
Spencer's Links: https://spenceralessi.com
Work with Us: https://securit360.com | Find vulnerabilities that matter, learn about how we do internal pentesting here.
https://youtu.be/BwYJ-kZ3XaY
youtu.behttps://youtu.be/Po8H140BijE
youtu.beSecurIT360 | Cybersecurity From Every Angle
securit360.comhttps://offsec.blog
offsec.bloghttps://offsec.blog/
offsec.bloghttps://www.youtube.com/@cyberthreatpov
youtube.comhttps://spenceralessi.com
spenceralessi.comhttps://securit360.com
securit360.cominternal pentesting here
offsec.blog
- 0:00Part 3: Software Supply Chain Failures (A03)
- 1:16Why supply chain topped the OWASP survey
- 4:31Why almost no one writes code from scratch anymore
- 5:55Two kinds of supply chain risk: whole apps vs. components
- 6:59The SolarWinds breach
- 9:57How AI and vibe coding make it worse
- 10:37What is an SBOM?
- 11:46Security checks in your CI/CD pipeline
- 13:47Shift-left: why a flaw found late costs 100x more
- 15:27The cake analogy
- 16:11Transitive dependencies
- 16:56Project Lantern & ChainGarde
- 18:19Pen testing as validation, not discovery
- 20:44Testing third-party apps and going straight to the vendor
- 21:40Be the hammer you beat your vendor with
- 22:53Vetting vendors: who ran the pen test matters
- 24:22Holding vendors accountable to fix findings
- 24:51Contracts, SLAs, and tools you already own
- 26:16Risks you can't fix — and why awareness still matters