Draft:NIST Secure Software Development Framework
Submission declined on 2 December 2024 by Ibjaja055 (talk). This submission is not adequately supported by reliable sources. Reliable sources are required so that information can be verified. If you need help with referencing, please see Referencing for beginners and Citing sources.
Where to get help
How to improve a draft
You can also browse Wikipedia:Featured articles and Wikipedia:Good articles to find examples of Wikipedia's best writing on topics similar to your proposed article. Improving your odds of a speedy review To improve your odds of a faster review, tag your draft with relevant WikiProject tags using the button below. This will let reviewers know a new draft has been submitted in their area of interest. For instance, if you wrote about a female astronomer, you would want to add the Biography, Astronomy, and Women scientists tags. Editor resources
|
SSDF was developed by NIST based on US Presidential Executive Order 14028 Section 4 (dated May 12, 2021)[1]. It provides a framework for securely developing software in the wake of software supply chain attacks and the prevalent use of open source software and third-party libraries. A major concept that was made popular by SSDF was the software bill of materials (SBOM) and the need for documenting the provenance (origin and history) of all software used in a system.
The first version of SSDF (NIST SP 800-218) was published in Feb 2022.
In general, any software that ends up being in a system sold to a US federal agency, must have an SSDF self-attestation form submitted by the developer.
References
[edit]- ^ Loehr, Tony (2021-12-13). "Executive Order 14028: NIST SSDF Explained". Cycode. Retrieved 2024-12-07.