Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

Inspired by ESG's Scope 3, which assesses supplier impact, building secure AI requires preemptively vetting the entire software supply chain. Companies must treat open-source packages and dependencies as suppliers, ensuring every component is secure from the start, rather than reactively scanning for flaws.

Related Insights

The attack on the widely used LightLLM package demonstrates a major software supply chain vulnerability. Malicious code inserted into a routine update silently stole credentials from countless AI tools, a risk that will be amplified by autonomous AI agents.

Open-source packages are executed with full system access by default, a stark contrast to mobile apps which require explicit user permission for sensitive actions. This "blind trust" model, where developers run unvetted code from strangers, is the fundamental vulnerability of the entire software supply chain.

While AI can be used to create exploits, its greater impact is on security. AI tools empower a vastly larger pool of contributors to scrutinize open codebases, identify flaws, and submit patches, strengthening the ecosystem faster than is possible in a closed environment.

AI agents prioritize speed and functionality, pulling code from repositories without vetting them. This behavior massively scales up existing software supply chain vulnerabilities, risking a collapse of trust as compromised code spreads uncontrollably through automated systems.

AI tools that automatically write applications often pull assets from open-source libraries. This creates a massive security risk, as these agents must be explicitly directed to use secure, vetted repositories to avoid introducing vulnerabilities at scale without human oversight.

The massive increase in AI-generated code is simultaneously creating more software dependencies and vulnerabilities. This dynamic, described as 'more code, more problems,' significantly expands the attack surface for bad actors and creates new challenges for software supply chain security.

Anthropic's AI found thousands of vulnerabilities in supposedly well-vetted open-source code. Because this code is widely copied and embedded in countless enterprise systems, these flaws represent a massive, previously unknown attack surface across global digital infrastructure.

The plummeting cost of finding exploits via AI models means enterprises cannot simply patch vulnerabilities reactively. The necessary strategic shift is to build foundational security controls for each asset class, including a new, dedicated security layer specifically for the AI stack.

AI models are better at finding bad code than writing good code. This capability will rapidly uncover vulnerabilities in open-source, custom, and vendor software that would have otherwise taken 10 years to find. This creates an urgent, large-scale need for patching across all industries.

The goal for trustworthy AI isn't simply open-source code, but verifiability. This means having mathematical proof, like attestations from secure enclaves, that the code running on a server exactly matches the public, auditable code, ensuring no hidden manipulation.

Securing AI Requires a "Scope 3" Approach to Your Code Supply Chain | RiffOn