Guidelines on Minimum Standards for Developer Verification of Software
Paul E. Black, Barbara Guttman, and Vadim Okun (National Institute of, Standards, Technology)

TL;DR
This paper outlines eleven recommended minimum standards for software verification techniques to enhance cybersecurity, including threat modeling, automated testing, static analysis, fuzzing, and web app scanning, developed by NIST and NSA.
Contribution
It provides a standardized set of broadly applicable software verification techniques as minimum cybersecurity standards, based on expert consultation.
Findings
11 recommended verification techniques for software security
Guidelines developed by NIST and NSA with industry input
Focus on minimum standards for broad applicability
Abstract
Executive Order (EO) 14028, "Improving the Nation's Cybersecurity", 12 May 2021, directs the National Institute of Standards and Technology (NIST) to recommend minimum standards for software testing within 60 days. This document describes eleven recommendations for software verification techniques as well as providing supplemental information about the techniques and references for further information. It recommends the following techniques: Threat modeling to look for design-level security issues Automated testing for consistency and to minimize human effort Static code scanning to look for top bugs Heuristic tools to look for possible hardcoded secrets Use of built-in checks and protections "Black box" test cases Code-based structural test cases Historical test cases Fuzzing Web app scanners, if applicable Address included code (libraries, packages, services)…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
