惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

人人都是产品经理
人人都是产品经理
有赞技术团队
有赞技术团队
WordPress大学
WordPress大学
月光博客
月光博客
T
Tailwind CSS Blog
阮一峰的网络日志
阮一峰的网络日志
小众软件
小众软件
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
Last Week in AI
Last Week in AI
大猫的无限游戏
大猫的无限游戏
S
SegmentFault 最新的问题
罗磊的独立博客
Jina AI
Jina AI
酷 壳 – CoolShell
酷 壳 – CoolShell
宝玉的分享
宝玉的分享
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
博客园 - 三生石上(FineUI控件)
量子位
雷峰网
雷峰网
Apple Machine Learning Research
Apple Machine Learning Research
美团技术团队
博客园 - 聂微东
V
V2EX

2024 Sonatype Blog

Reduce AI Token Waste by Getting Decisions Right Earlier Optimising Out the Waste in Open Source Publishing The CRA Reporting Deadline Is Almost Here Hugging Face Security Incident: A New Class of Threat Is Here The AI Productivity Paradox: More Code, Not More Delivery A Reported Log4j RCE Is More Complicated Than It Looks Why Financial Services Is the Canary in the Code Mine 91 Spring CVEs: The AI Vulnerability Consumption Problem An Air Gap Doesn Securing Software at the Speed of AI: What Four Years of Data Reveal Major Themes at Black Hat 2026 Six npm Packages Use Ethereum Transactions to Retrieve Malicious Payloads Flooding Dropper Hits npm With 850 Malicious Packages Mini Shai-Hulud npm Attack: More Than 2,200 Components Impacted 5 Reasons Developers Still Download Malicious Packages Defining Community Open Source Is Harder Than It Looks Walking the Walk on Package Registry Sustainability The Hugging Face Incident Changes the Vulnerability Equation What Is Grounding? Why AI Coding Assistants Need Better Intelligence Open Source, Open Infrastructure, and the Space Between Request for Comments: CARE and Maven Central Q2 2026 Open Source Malware Index AI Is Forcing a New Open Source Security Model Vulnerability Prioritization Is Missing the AI-Era Point The Hidden National Security Threat Inside AI-Driven Software Miasma Returns: Leo Platform Compromise in npm The Rise of Collective Defense for Open Source Signal Over Noise: Reachability Analysis Is the Reality Check SCA Has Been Missing Software Security Has to Start at Assembly easy-day-js Targets Mastra, Dependency Attacks Grow
AI Changes the Software Supply Chain and How We Secure It
Aaron Linskens · 2026-07-28 · via 2024 Sonatype Blog

Artificial intelligence is expanding the software supply chain beyond traditional software components, introducing new dependencies that require security leaders to rethink how software is governed.

Modern AI applications increasingly depend on foundation models, training datasets, vector databases, AI agents, orchestration frameworks, and third-party AI services. These assets have become just as critical to software delivery as open source.

That shift has created an entirely new supply chain — one that traditional software security programs were never designed to govern.

Many organizations have spent years strengthening software supply chain security through software composition analysis (SCA), software bills of materials (SBOMs), and policy-driven governance. Although these traditional capabilities remain critical, AI brings new attack vectors that challenge security leaders to expand their focus past standard software components.

AI Has Expanded the Software Supply Chain

For years, software supply chain security focused primarily on components developers intentionally added to applications:

  • Open source packages

  • Containers

  • Third-party libraries

  • Build pipelines

AI dramatically expands that list.

Today's AI-enabled applications may rely on pretrained foundation models, externally sourced datasets, retrieval systems, agent frameworks, model orchestration platforms, and external AI APIs. Each introduces its own trust assumptions, provenance questions, and security risks.

AI assets are becoming another category of third-party dependency. But unlike software components, they often cannot be inspected, validated, or remediated using existing security tooling.

Prevention Matters More Than Ever

AI changes the economics of remediation. With traditional software, vulnerable dependencies can often be upgraded or replaced.

AI doesn't always work that way.

Security leaders have long focused on detecting and fixing vulnerabilities after software enters development. But when compromised datasets or poisoned models become embedded into AI systems, remediation can become dramatically more expensive and disruptive.

The further upstream organizations can establish trust in models, datasets, and AI services, the less likely they are to inherit risks that become difficult or impossible to unwind later.

AI Supply Chain Security Requires Lifecycle Governance

AI security cannot be treated as a point-in-time exercise. Traditional software security often emphasizes scanning artifacts before deployment. AI introduces assets that evolve continuously.

Models are updated. Datasets change. Agents dynamically invoke external tools. Runtime behavior can differ from development-time expectations.

Security leaders need governance that extends across the entire AI lifecycle, including:

  • Discovering and inventorying AI assets.

  • Establishing provenance for models and datasets.

  • Validating model integrity before adoption.

  • Managing runtime behavior for AI agents.

  • Continuously monitoring AI systems after deployment.

This represents a broader governance challenge rather than simply another category of application security.

Securing the Next Software Supply Chain

AI is changing more than how software is built. It's changing what organizations need to trust.

Software supply chains no longer end with open source packages, containers, and libraries. They now extend to models, datasets, AI agents, orchestration frameworks, and external AI services. As these assets become foundational to modern applications, they require the same level of visibility, governance, and security that organizations already apply to traditional software components.

For security leaders, the challenge is no longer simply securing software. It's securing an increasingly complex ecosystem of software and AI dependencies. Organizations need to establish trust before AI assets enter development, continuously govern them throughout their lifecycle, and monitor them as they evolve.

To learn more about this evolving challenge, download the Gartner® report "5 Steps to Secure Your AI Supply Chain." It explores why AI should be managed as an end-to-end supply chain and provides five practical recommendations for strengthening governance, improving visibility, and reducing risk across the AI lifecycle.

24 March 2026, Gartner, 5 Steps to Secure Your AI Supply Chain, Angela Zhao, Deepti Gopal, Esraa ElTahawy, Rahul Balakrishnan

GARTNER is a registered trademark and service mark of Gartner, Inc. and/or its affiliates in the U.S. and internationally and is used herein with permission. All rights reserved.

Tags

analyst report Gartner