Skip to main content
Mallory
← Back to News
cybersecurity-regulationstandards-framework-updateai-platform-security

Policy and Regulatory Push for Software Supply Chain Security and Vendor Liability

Regulatory & Policy · 2 sources · Updated 4mo ago · First seen Nov 25, 2025

Policy and Regulatory Push for Software Supply Chain Security and Vendor Liability

Government and industry leaders are intensifying efforts to address software supply chain security, with a particular focus on the adoption of Software Bills of Materials (SBOMs) and the potential for holding software vendors liable for security failures. In the United States, the push for SBOMs has been driven by federal policy, but private sector adoption remains slow, even as the rapid evolution of AI-assisted coding introduces new complexities and risks. Experts are divided on whether AI will reduce or exacerbate vulnerabilities, but there is consensus that transparency in software components remains critical for managing security risks.

In the United Kingdom, lawmakers are calling for significant regulatory changes, including introducing liability for software developers, incentivizing cyber resilience investments, and mandating incident reporting. These recommendations come in response to a series of high-profile cyber incidents, such as the attack on Jaguar Land Rover, which have underscored the economic and public risks posed by insecure software. The debate continues between industry groups, who warn that liability could stifle innovation, and security leaders, who argue that the current system leaves critical infrastructure and the broader economy exposed to escalating cyber threats.

What this changes for youSee the reporting duties and controls this puts on the clock.
Get the context
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

1 event · Nov 25, 2025
  1. Nov 25, 20251y ago

    Story first reported

    Initial story creation

Do you run this?See what this changes for your reporting obligations and which controls it puts on the clock.
Get the Regulatory Context
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.