The federal government is on a roll. They continue to show they are going all out to prove they can work with and help private industry prevent various forms of cyberattacks.

The latest effort has a joint agency partnership releasing the “Securing the Software Supply Chain Recommended Practices Guide for Suppliers.”

The move is an effort to shore up the software supply chain to help avoid and protect against supply chain attacks like the SolarWinds incident a few years ago or like the Kaseya attack shortly thereafter or defend against exploits that take advantage of vulnerabilities such as Log4j.

That is why the Cybersecurity and Infrastructure Security Agency (CISA), the National Security Agency (NSA), and the Office of the Director of National Intelligence (ODNI) partnered with industry and government experts under the Enduring Security Framework (ESF) to release the supply chain guide.

Software suppliers/vendors act as a liaison between the customer and the software development team; ensuring software is developed in a secure environment and delivered via secure channels. To ensure a more secure software supply chain, Suppliers should seek to identify threats that could compromise the organization, software development, software itself, and software delivery (i.e. on-premise or Software-as-a-Service (SaaS)) environments and implement associated mitigations.

Schneider Bold

There is now an increased need for software supply chain security awareness and cognizance regarding the potential for software supply chains to be weaponized by nation state adversaries using similar tactics, techniques, and procedures.

A new, less conspicuous method of compromise threatens software supply chains and undermines trust in the patching systems themselves that are critical to guarding against legacy attacks. Rather than waiting for public vulnerability disclosures, threat actors proactively inject malicious code into products legitimately distributed downstream through the global software supply chain. Over the last few years, these next-gen software supply chain compromises have significantly increased for both open source and commercial software products.

This guidance has been created by the Critical Infrastructure Partnership Advisory Council (CIPAC) Cross Sector Enduring Security Framework Working Group, a public-private working group that provides cybersecurity guidance addressing high-priority cyber threats to the nation’s critical infrastructure. In line with industry best practices and principles, software suppliers are encouraged to review and reference this new guidance.

This guidance can serve as a compendium of suggested practices for developers, suppliers, and customer stakeholders to help ensure a more secure software supply chain.

This guidance for suppliers is the second in a three-part series on “Securing the Software Supply Chain.” This is Part 2 of the series which focuses on the software supplier. Part 1 of the series focused on software developers and Part 3 of the series will focus on the software customer.

In September, the first part for developers was published; the third and final segment will be for software customers, such as those who acquire software for the federal government.

Click here to view the series.

Pin It on Pinterest

Share This