|
Technique Class |
Technique |
Description & Reference to Recommended Minimums Document |
|
If the software might be connected to the Internet, run a web app scanner. |
Section 2.10. If there is a network interface, use a dynamic security testing tool (e.g., web application scanner) to detect vulnerabilities. |
|
|
Check included software |
Use similar techniques to gain assurance that included libraries, packages, services, etc. are no less secure than your code. |
Section 2.11. Use the verification techniques recommended in this section to gain assurance that included code is at least as secure as code developed locally. The components of your software must be continually monitored against databases of known vulnerabilities; a new vulnerability in existing code may be reported at any time. |
|
Fix bugs |
Fix critical bugs that are uncovered. |
Correct critical bugs as soon as possible and make process improvements necessary to prevent such bugs in the future, or to at least catch them earlier in the development process. |
Regulatory Compliance Standards and Frameworks
EXECUTIVE ORDER 14028, IMPROVING THE NATION'S CYBERSECURITY - NIST Content - Continued
- Details
- Written by: NIST
- Parent Category: Resources
- Category: Regulatory Compliance Standards and Frameworks
Article Index
- Hits: 1613

Whether you're preparing for Cybersecurity certification, working with government standards, or simply starting your career in compliance, these are the NIST Federal Information Processing Standards (FIPS), Special Publication (SP), and Interagency Report (IR) topics