Continuous Assurance and Software Supply Chain Security

This is the second in a series of articles examining the new NIST SP 800-218 guidelines, with our recommendations for best practices to achieve compliance.

As we discussed in our previous article, guidelines established by the US National Institute of Standards and Technology (NIST) will dramatically alter the way in which software products and services are supplied to the United States government.

Specifically, NIST SP 800-218 establishes a set of high-level, secure software development practices that are to be integrated into every Software Development Life Cycle (SDLC). The incorporation of these practices throughout the software supply chain is expected to promote more secure products and services for delivery not only to the US government, but, ultimately, across industries and around the globe.

In this article, we examine the role of Continuous Assurance (CA) in meeting these requirements and its implementation in your SDLC. First, we take a broad look at Continuous Assurance, why it is needed, and how it works. Then, we provide some examples and recommendations for collecting evidence and explore how this evidence can be used to verify the security of your products.

Download the article to find out how you can use CA to improve your security posture and trust in the software supply chain in general.

All Resources

Last Resources

Mitigation strategies for dealing with GitHub security breaches In late September news came out that GitHub repositories were hit by password-stealing commits that were disguised…
Gain valuable insights and strategies to fortify your software development process  Dr. Zero Trust shares essential tips on securing your software supply chain If you…
The adoption of software supply chain security best practices is currently in a watershed moment similar to the publication of the PCI compliance requirements in…