Topic starter
18/08/2026 2:53 pm
TL;DR: NIST’s SSDF needs to change because AI code generation breaks its assumptions about deterministic tools, human-scale review, and passive tooling, according to Sonar. The practical shift is toward mandatory automated verification, layered review, and supply-chain controls that validate outcomes before release.
Editorial analysis by NHI Mgmt Group, based on content published by Sonar: “What NIST should know when updating the SSDF for AI”.
By the numbers:
- Sonar analyzes more than 750 billion lines of code every day across 7 million software developers.
- Sonar's research found that coding models, left unverified, produce roughly 1,200 security issues per million lines of code analyzed.
- Sonar reports that AI-generated PRs modify an average of 14x more code than traditional tools, while agentic workflows correlate with a 3-5x increase in lines added per project.
Key questions
Q: What breaks when AI-generated code is treated like normal developer output?
A: Teams can miss insecure patterns, risky dependencies, and hidden assumptions because the review process assumes human authorship.
Q: Why do AI coding agents increase supply-chain risk?
A: AI coding agents can choose tooling, install packages, and edit lock files in ways that may bypass the controls humans expect in a managed environment.
Q: What are the warning signs that AI code review is failing?
A: Look for large pull requests approved with minimal discussion, reviewers unable to explain the change, repeated exceptions to standards, and security checks treated as ceremonial.
Practitioner guidance
- Mandate deterministic post-generation verification Require every AI-authored change to pass independent static analysis, SCA, and CI checks before merge or release, regardless of who or what produced it.
- Limit repository and pipeline privileges for coding agents Scope AI coding assistants to the smallest set of repositories, build actions, and secrets needed for their task, and separate generation from deployment authority.
- Validate prompts and inputs as untrusted content Treat tickets, file content, retrieved context, and API responses as potentially malicious instructions that can steer agent behaviour.
Bottom line: AI-generated code breaks the SSDF assumption that tools are deterministic and reviewable at human scale.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
18/08/2026 3:36 pm
Outcome verification is now the governing principle for AI-assisted software delivery. The SSDF cannot depend on a model to validate its own work because probabilistic generation breaks the premise of deterministic assurance. That means the control conversation shifts from trusting authorship to proving security and quality before release. Practitioners should treat this as a structural change in software governance, not a tooling preference.
A few things that frame the scale:
- 92% of organisations expose NHIs to third parties, raising concerns about supply chain security, according to the Ultimate Guide to NHIs.
- Breaches involving third parties rose to 48% of all breaches, a 60% increase on the previous year, according to Verizon's 2026 Data Breach Investigations Report.
A question worth separating out:
Q: How should teams govern AI systems that act like privileged insiders?
A: Treat AI systems as governed actors with explicit access scope, strong logging, and containment boundaries. If an AI can influence data or actions at speed, traditional review cycles are too slow to provide meaningful oversight. The control question becomes what it can access and what it can do.
👉 Read our full editorial: SSDF must evolve for AI-generated code and active attack surfaces