Patrick Smyth of Chainguard outlines defenses for AI-accelerated software attacks in this 22-minute AI Engineer talk.

Four surfaces, four different problems

  • Malicious packages: a dependency can contain an attack even when scanners report no known vulnerabilities.
  • Known vulnerabilities: published CVEs, the catalogued security flaws, give attackers a ready-made target list.
  • Zero days: previously unknown flaws require discovery, coordinated repair and smaller exposed systems.
  • Side doors: build pipelines, developer laptops and agent skills can undermine otherwise well-protected production code.

Slow package intake; speed up security fixes

  • Use a cooldown before adopting newly published packages, giving defenders time to detect malicious releases.
  • Accelerate fixes for exposed vulnerabilities; a routine 30-day queue can leave time for exploitation.
  • Apply controls on developer machines as well as production, or dependencies can bypass the protected path.
  • Finish containerization and repeatable builds so urgent fixes have a reliable route into production.

Verify each handoff

  • Sign artifacts with tools such as Sigstore, and check signatures when another system receives them.
  • Attach build provenance using SLSA, a framework for documenting how software was produced.
  • Rebuilding clean upstream source can bypass compromised distribution steps; source review remains a separate responsibility.
  • Treat third-party agent skills as software dependencies that need review and controlled distribution.

Where the vendor pitch begins

  • Chainguard maps its containers, rebuilt libraries, Athena consortium, hardened actions and skills onto these surfaces.
  • Smyth describes rapid rebuilds and remediation commitments; these are vendor service claims.
  • His exploit-timing chart and malicious-skill estimates lack enough methodology in the talk to support universal rates.
  • Caveat: authenticated provenance establishes an artifact’s origin and build history; its behavior still needs security review.

“Whenever an artifact is created, sign it and then pass it off, then check that signature on the other end.” — Patrick Smyth, 17:13