16 controls
0 frameworks share controls with it
United States
verified against its source document
Every control below is one this framework asks for. The right hand column counts how
many other frameworks in our corpus carry the same control, which is the difference between
doing this work once and doing it again for the next standard.
There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.
What you already have
Frameworks whose controls overlap this one, most first. If you run any of them, the
count is roughly what you have already evidenced.
No measured overlap with another framework in the corpus.
Every control
| Code | Control | Also in |
1 | Charge, scope and how verification fits | 0 |
2.1 | Threat model early and use it to focus verification | 0 |
2.10 | Run a web application scanner where the software is a web application | 0 |
2.11 | Verify included software components and monitor them for known vulnerabilities | 0 |
2.2 | Automate verification | 0 |
2.3 | Run static (code-based) analysis | 0 |
2.4 | Review the code for hardcoded secrets | 0 |
2.5 | Run with language-provided checks and protection | 0 |
2.6 | Create black box test cases | 0 |
2.7 | Create code-based (structural) test cases and reach 80 percent statement coverage | 0 |
2.8 | Keep and rerun historical test cases | 0 |
2.9 | Fuzz the software | 0 |
3 | Background on the techniques (informative) | 0 |
4.1 | Place verification inside good software development practice | 0 |
4.2 | Ship secure defaults, verify all valid settings and keep supply chain integrity | 0 |
4.3 | Additional software assurance technology (informative) | 0 |
Tell me when NIST IR 8397 Guidelines on Minimum Standards for Developer Verification of Software files something new
One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.
What this page is
A control-level reference for NIST IR 8397 Guidelines on Minimum Standards for Developer Verification of Software, drawn from our framework corpus. Control codes and
titles are references to the standard, not reproductions of it. The overlap counts and the
auditor artefacts are our own work and are the part you will not find elsewhere.
Measure this against what you already run ·
All frameworks · Today's edition