Visiting KubeCon North America? See us at Booth # 752
Visiting KubeCon North America? See us at Booth # 752
Visiting KubeCon North America? See us at Booth # 752
Visiting KubeCon North America? See us at Booth # 752
Visiting KubeCon North America? See us at Booth # 752
Visiting KubeCon North America? See us at Booth # 752
Visiting KubeCon North America? See us at Booth # 752
Visiting KubeCon North America? See us at Booth # 752
Back

As 2025 Ends, One Reality Has Become Unavoidable

December 12, 2025
This is some text inside of a div block.

“Supply Chain Security Is Now a Business Variable”

“AI Will Accelerate Both Risk and Competitive Advantage in 2026”

As we close 2025 and plan for the year ahead, I believe we are entering a new phase in how technology risk influences the business. Software vulnerabilities no longer appear only at the perimeter. They move quietly through dependencies, build pipelines and container images. They travel inside the same systems we rely on to deliver software faster.

Across the United States and Europe, the most impactful incidents over the past two years did not begin with an external breach. They entered through trusted components. What was once a technical concern has become a commercial concern. Supply chain integrity now affects delivery timelines, contract eligibility, renewal rates and customer confidence.

I believe 2026 will be shaped by how we respond to this shift. AI will accelerate progress and risk at the same time and neither side is slowing down.

What 2024 and 2025 Actually Taught Us

The attack surface moved upstream

Threat campaigns across npm, PyPI and Docker Hub were structured, not random. In one attack called Shai-Hulud, malicious code was inserted into GitHub Actions to extract cloud credentials directly from CI pipelines. The breach did not start at production. It started at the source.

Trusted components were not enough

The XZ Utils backdoor almost shipped into major Linux distributions and official Docker images. Several companies halted deployments because they could not verify the safety of their base images. Trust and verification have become very different things.

Financial impact became visible

Several vendors and SaaS providers across the US and Europe reported direct business consequences. Recovery costs ranged from 3.5M to 8M USD in enterprise incidents. Delivery delays led to customer churn and penalty clauses under SLAs. Reputational recovery took weeks or months.

Regulation began shaping procurement

In the United States, Executive Order 14028 and related guidance on SBOMs now influence federal software procurement. In Europe, NIS2 and the Cyber Resilience Act place liability on software producers for insecure components. In both regions, supply chain transparency is moving from security practice to commercial criterion.

AI changed the timeline

AI tools can analyze code, assess dependencies and generate variants faster than manual approaches. The same capabilities can be used to identify vulnerabilities or exploit them. The difference will depend on how AI is governed.

What Will Change in 2026

I expect enterprise strategies to shift in the following way:

Phase 

Common Practice Today 

Expected in 2026 

Business Risk 

Source 

Scan dependencies 

Vet, mirror and track components 

Blind trust in upstream code 

Build 

Scan CI output 

Harden and attest builds 

Compromise before signing 

Registry 

Store container images 

Enforce signatures and provenance 

Unknown components in production 

Deploy 

Scan post deployment 

Apply policy-based admission control 

Compliance and SLA gaps 

Runtime 

Detect incidents 

Autonomous containment 

Extended downtime 

Response 

Patch manually 

Use SBOM and provenance for rapid traceability 

Revenue and retention impact 

This shift is not driven by tools. It is driven by business continuity and responsibility.

How AI Will Influence Both Risk and Resilience

AI Impact 

Opportunity 

Threat 

Code generation 

Faster delivery cycles 

Faster exploit generation 

Dependency research 

Forecasting and risk scoring 

Rapid malicious variants 

Build intelligence 

Automated SBOM and provenance 

Secret extraction from CI containers 

Runtime analytics 

Isolation and rollback 

AI-guided lateral movement 

AI is creating a divide between organizations that automate resilience and organizations that accelerate risk without realizing it.

The Question I Believe Will Define 2026

“If a popular dependency is compromised tomorrow can we identify every affected container image across every environment and rebuild or revoke it within one hour not one week”

If the answer is uncertain, exposure already exists even without a breach.

A Readiness Scale I Now Use with Leadership Teams

Level 

Description 

Outcome 

Level 1 

Reactive scanning 

Long recovery windows 

Level 2 

Basic policy enforcement 

Partial coverage 

Level 3 

Verified builds and signed images 

Confidence in core systems 

Level 4 

Searchable SBOM across environments 

Fast incident response 

Level 5 

Continuous attestation and AI-supported validation 

Operational resilience at scale 

This is gradually becoming a dimension used by investors, auditors and procurement teams.

Closing Thought

The perimeter is no longer the frontline. The pipeline is now part of it. Every dependency used inside a container is an assumption and every assumption now creates measurable cost.

2025 has made the direction clear.

2026 will likely require evidence.

Those who prepare early will gain room to innovate.

Those who wait will respond under pressure.

Supply chain integrity will become a key differentiator in the year ahead. Not only for security, but for business continuity and long-term trust.


Nilesh Jain

Co-founder & CEO

This is some text inside of a div block.
This is some text inside of a div block.
Share