Topic starter
01/08/2026 8:58 pm
TL;DR: AI-generated code produces 1.7x more vulnerabilities than human-written code, while most organisations cannot inventory embedded models, MCP servers, agent frameworks, datasets, or prompts, according to Checkmarx. The governance problem is no longer just code volume but unseen AI components that create new supply chain attack paths and audit gaps.
Editorial analysis by NHI Mgmt Group, based on content published by Checkmarx: “You’re Securing Your Code. But Are You Securing the AI Inside It?”.
Key questions
Q: What breaks when AI components are invisible to AppSec inventory controls?
A: When AI components are invisible, teams cannot tell which models, agents, datasets, or prompts are actually in use, so policy, risk review, and exception handling all become incomplete.
Q: Why do AI supply chain risks create governance exposure even when code scans are clean?
A: Code scans only cover software defects, not model behaviour, runtime prompts, third-party terms, or tool access.
Q: What are the signs that shadow AI controls are failing in practice?
A: Shadow AI controls are failing when sensitive data moves through copy-paste, uploads, or API calls outside sanctioned workflows, yet the organisation has no alerting or enforcement at the point of transfer.
Practitioner guidance
- Implement code-first AI asset discovery Inventory models, agent frameworks, MCP servers, datasets, embeddings, and prompt files directly from source and configuration instead of relying on dependency manifests alone.
- Add AI intake policy gates Require approved model lists, framework allowlists, version pinning, and review of dataset references before AI components are merged into production paths.
- Extend AppSec workflows to AI artefacts Surface AI findings in the same pull request, CI/CD, and dashboard workflows used for SAST and SCA so teams do not create a parallel review process.
Bottom line: AI-enabled software now includes assets that traditional AppSec inventory controls were never designed to see, which creates a governance gap before a vulnerability even exists.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
01/08/2026 9:05 pm
Shadow AI is now a supply chain governance problem, not just an AppSec extension. The article shows that the asset boundary has expanded beyond code and packages to models, prompts, datasets, agent frameworks, and MCP servers. That means the control question is no longer only whether a build passed scan, but whether the organisation can inventory the actual components that shape runtime behaviour. Practitioners should treat AI component discovery as part of core software governance.
A few things that frame the scale:
- AI-related credential leaks surged 81.5% year-over-year in 2025, with the surrounding AI infrastructure leaking 5x faster than core LLM providers, according to the State of Secrets Sprawl 2026.
- 96% of security operations teams report critical blind spots, most commonly in cloud infrastructure (74%) and identity and access behaviour (67%).
A question worth separating out:
Q: How should security teams include AI applications in software supply chain security programs?
A: Security teams should treat AI applications as part of the software supply chain, not as a separate innovation track. That means enforcing secure development practices, validating data provenance, reviewing third-party models and libraries, and monitoring deployments continuously. The goal is to reduce exposure from tampering, malicious inputs, and ungoverned dependencies before AI systems reach production.
👉 Read our full editorial: Shadow AI in the software supply chain is breaking AppSec visibility