A secure software supply chain all comes down to users trusting where and who they are getting their product from.

Once that trust is violated, it can be very difficult to gain it back. Just ask any of the victims of various supply chain attacks from the past.

To that end, the Cybersecurity and Infrastructure Security Agency (CISA), the National Security Agency (NSA), and the Office of the Director of National Intelligence (ODNI), published their third installment of a three-part series on securing the software supply chain: “Securing Software Supply Chain Series – Recommended Practices Guide for Customers.”

This publication follows the August release of guidance for developers and October 2022 release of guidance for suppliers.

The guidance provides recommended practices for software customers to ensure the integrity and security of software during the procuring and deployment phases.

Schneider Bold

The following are best practices users can review to ensure a more secure supply chain:

  • Require and verify attestation for the product (SBOMS)
  • Perform security, environmental, and functionality tests on the software product
  • Check integrity mechanisms during deployment
  • Require notification from supplier for changes in ownership/control, geo location, third parties to software product; cyber incidents and investigations, and mitigations/impacts to product or development environment of the product at time of delivery
  • Require attestation of cybersecurity hygiene of the vendor/supplier development process and the infrastructure supporting the development of their product to inform the risk management determination by the user organization
  • Continuous security monitoring of product as part of security operations

The Securing Software Supply Chain Series is an output of the Enduring Security Framework (ESF), a public-private cross-sector working group led by NSA and CISA. This series complements other U.S. government efforts underway to help the software ecosystem secure the supply chain, such as the software bill of materials (SBOM) community.

Click here to review the guidance.

Pin It on Pinterest

Share This