Beyond Dependencies: The Real Picture of Software Supply Chain Security

Supply Chain Microsummit @ BlackHat USA 2025

07 August 2025

Presentation

Beyond Dependencies: The Real Picture of Software Supply Chain Security

Anant Shrivastava | Founder, Cyfinoid Research

Date: Thursday, August 7 | 10:50am-11:30am ( Business Hall Theater C )

Format: 40-Minute Summit Session

Track: Supply Chain Micro Summit

Software Supply Chain Security has been a buzzword for the past few years, but as the initial hype settles, it’s time to ask: what’s actually working—and what’s being overlooked?

In response to rising threats, many organizations have rushed to implement SCA tools or generate SBOMs and called it a day. But security is rarely that simple. Is generating a BOM of your code dependencies truly enough? What about the unsigned binaries your devs download during prototyping, the Docker images pulled from random GitHub issues, or the low-friction APIs that newer technologies—like AI platforms—introduce into trusted environments?

This talk takes a 360-degree view of supply chain security—beyond just dependencies—to highlight the broader risks involved in how modern software is developed, integrated, deployed, and consumed. We’ll explore:

Whether you’re building software or just using it, this session will challenge assumptions, offer practical mental models, and leave you with a grounded understanding of where your supply chain security posture actually stands—and where the gaps may lie.

AI Generated Summary

AI Generated Content Disclaimer

Note: This summary is AI-generated and may contain inaccuracies, errors, or omissions. If you spot any issues, please contact the site owner for corrections. Errors or omissions are unintended.

This comprehensive presentation at BlackHat USA 2025 argues that the software supply chain extends far beyond code dependencies. Anant Shrivastava traces supply chain trust issues back to Ken Thompson’s 1983 Turing Award lecture, surveys the global regulatory landscape, and systematically demonstrates that browser extensions, IDE plugins and marketplaces, AI coding agents, package manager scripts, CI/CD systems, container images, dependency caching servers, and even rogue maintainers all represent critical — and largely unmonitored — attack vectors. The talk provides the ATOM framework for action and an extensive toolkit of open-source tools for auditing, vetting, and visualizing the full software supply chain.

Key Topics Covered

Historical Context and Regulatory Landscape:

Why Supply Chain Risks Are Accelerating:

SBoM and SCA — The Starting Point:

Supply Chains Beyond Code — Attack Vectors Explored:

The ATOM Framework:

Open-Source Tooling for Supply Chain Security:

Frameworks and Standards:

Shadow IT — The Scariest Chain:

Actionable Takeaways

  1. Expand your threat model beyond code dependencies to include browser extensions, IDE marketplaces, AI coding agents, CI/CD pipelines, container registries, package manager scripts, and dependency caching infrastructure.
  2. Deploy osquery to inventory Chrome extensions with risky permissions across your organization and establish enterprise policies for extension whitelisting.
  3. Audit your VS Code and IDE extension ecosystem — be aware that Open VSX marketplace vulnerabilities could affect all VS Code fork users (Cursor, Windsurf, GitLab Web IDE, etc.).
  4. Secure CI/CD pipelines with Legitify, OpenSSF best practices, Allstar enforcement, and Zizmor analysis — these are the crown jewels of modern software delivery.
  5. Use SafeDep’s Vet tool and the Overlay browser extension to vet open-source dependencies before adoption, aggregating health signals from multiple sources.
  6. Implement the ATOM framework: build Awareness of your full supply chain, Trust But Verify all components, maintain Ongoing Monitoring, and Measure & Map your actual exposure.
  7. Try SBoM Play and 3PTracer from Cyfinoid for immediate, privacy-preserving visibility into your organization’s dependency landscape and third-party connections.
  8. Address Shadow IT proactively — establish governance for AI IDE usage and monitor for unsanctioned application deployments by non-engineering teams on personal cloud accounts.
  9. Use SLSA, OWASP SCVS, and the pbom.dev attack reference to structure your supply chain security program around established frameworks rather than ad-hoc tooling.

Social chatter