id string | text string | doc_id string | doc_title string | revision string | pub_date string | tier int32 | chunk_type string | control_id string | section_path string | source_url string | sha256_source string |
|---|---|---|---|---|---|---|---|---|---|---|---|
SP-800-218/section/waltermire-da-scarfone-ka-casipe-m-2011-specification-for-the-open | PCISSLC: 2.6, 4.2
SCFPSSD: Secure Development Lifecycle Feedback
[BSAFSS]
BSA (2020) The BSA Framework for Secure Software: A New Approach to
Securing the Software Lifecycle, Version 1.1. Available at
https://www.bsa.org/files/reports/bsa_framework_secure_software_update
Migues S, Erlikhman E, Ewers J, Nassery K ... | SP-800-218 | Secure Software Development Framework (SSDF) Version 1.1 | 1.1 | 2022-02 | 2 | section | null | Waltermire DA, Scarfone KA, Casipe M (2011) Specification for the Open | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf | 617746e553a9e2da49bfbd4eef0dfc3094758a39b869314e4173ac36605cde22 |
SP-800-218/ssdf_practice/po.1.1 | PO.1.1: Identify and document all security requirements for the organization's software development infrastructures and processes, and maintain the requirements over time. Example 1: Define policies for securing software development infrastructures and their components, including development endpoints, throughout the S... | SP-800-218 | Secure Software Development Framework (SSDF) Version 1.1 | 1.1 | 2022-02 | 2 | ssdf_practice | null | SSDF Practices > PO > PO.1 > PO.1.1 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf | 617746e553a9e2da49bfbd4eef0dfc3094758a39b869314e4173ac36605cde22 |
SP-800-218/ssdf_practice/po.1.2 | PO.1.2: Identify and document all security requirements for organization-developed software to meet, and maintain the requirements over time. Example 1: Define policies that specify risk-based software architecture and design requirements, such as making code modular to facilitate code reuse and updates; isolating secu... | SP-800-218 | Secure Software Development Framework (SSDF) Version 1.1 | 1.1 | 2022-02 | 2 | ssdf_practice | null | SSDF Practices > PO > PO.1 > PO.1.2 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf | 617746e553a9e2da49bfbd4eef0dfc3094758a39b869314e4173ac36605cde22 |
SP-800-218/ssdf_practice/po.1.3 | PO.1.3: Communicate requirements to all third parties who will provide commercial software components to the organization for reuse by the organization's own software. [Formerly PW.3.1] Example 1: Define a core set of security requirements for software components, and include it in acquisition documents, software contr... | SP-800-218 | Secure Software Development Framework (SSDF) Version 1.1 | 1.1 | 2022-02 | 2 | ssdf_practice | null | SSDF Practices > PO > PO.1 > PO.1.3 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf | 617746e553a9e2da49bfbd4eef0dfc3094758a39b869314e4173ac36605cde22 |
SP-800-218/ssdf_practice/po.2.1 | PO.2.1: Create new roles and alter responsibilities for existing roles as needed to encompass all parts of the SDLC. Periodically review and maintain the defined roles and responsibilities, updating them as needed. Example 1: Define SDLC-related roles and responsibilities for all members of the software development tea... | SP-800-218 | Secure Software Development Framework (SSDF) Version 1.1 | 1.1 | 2022-02 | 2 | ssdf_practice | null | SSDF Practices > PO > PO.2 > PO.2.1 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf | 617746e553a9e2da49bfbd4eef0dfc3094758a39b869314e4173ac36605cde22 |
SP-800-218/ssdf_practice/po.2.2 | PO.2.2: Provide role-based training for all personnel with responsibilities that contribute to secure development. Periodically review personnel proficiency and role-based training, and update the training as needed. Example 1: Document the desired outcomes of training for each role. Example 2: Define the type of train... | SP-800-218 | Secure Software Development Framework (SSDF) Version 1.1 | 1.1 | 2022-02 | 2 | ssdf_practice | null | SSDF Practices > PO > PO.2 > PO.2.2 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf | 617746e553a9e2da49bfbd4eef0dfc3094758a39b869314e4173ac36605cde22 |
SP-800-218/ssdf_practice/po.2.3 | PO.2.3: Obtain upper management or authorizing official commitment to secure development, and convey that commitment to all with development-related roles and responsibilities. Example 1: Appoint a single leader or leadership team to be responsible for the entire secure software development process, including being acc... | SP-800-218 | Secure Software Development Framework (SSDF) Version 1.1 | 1.1 | 2022-02 | 2 | ssdf_practice | null | SSDF Practices > PO > PO.2 > PO.2.3 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf | 617746e553a9e2da49bfbd4eef0dfc3094758a39b869314e4173ac36605cde22 |
SP-800-218/ssdf_practice/po.3.1 | PO.3.1: Specify which tools or tool types must or should be included in each toolchain to mitigate identified risks, as well as how the toolchain components are to be integrated with each other. Example 1: Define categories of toolchains, and specify the mandatory tools or tool types to be used for each category. Examp... | SP-800-218 | Secure Software Development Framework (SSDF) Version 1.1 | 1.1 | 2022-02 | 2 | ssdf_practice | null | SSDF Practices > PO > PO.3 > PO.3.1 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf | 617746e553a9e2da49bfbd4eef0dfc3094758a39b869314e4173ac36605cde22 |
SP-800-218/ssdf_practice/po.3.2 | PO.3.2: Follow recommended security practices to deploy, operate, and maintain tools and toolchains. Example 1: Evaluate, select, and acquire tools, and assess the security of each tool. Example 2: Integrate tools with other tools and existing software development processes and workflows. Example 3: Use code-based conf... | SP-800-218 | Secure Software Development Framework (SSDF) Version 1.1 | 1.1 | 2022-02 | 2 | ssdf_practice | null | SSDF Practices > PO > PO.3 > PO.3.2 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf | 617746e553a9e2da49bfbd4eef0dfc3094758a39b869314e4173ac36605cde22 |
SP-800-218/ssdf_practice/po.3.3 | PO.3.3: Configure tools to generate artifacts6 of their support of secure software development practices as defined by the organization. Example 1: Use existing tooling (e.g., workflow tracking, issue tracking, value stream mapping) to create an audit trail of the secure development-related actions that are performed f... | SP-800-218 | Secure Software Development Framework (SSDF) Version 1.1 | 1.1 | 2022-02 | 2 | ssdf_practice | null | SSDF Practices > PO > PO.3 > PO.3.3 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf | 617746e553a9e2da49bfbd4eef0dfc3094758a39b869314e4173ac36605cde22 |
SP-800-218/ssdf_practice/po.4.1 | PO.4.1: Define criteria for software security checks and track throughout the SDLC. Example 1: Ensure that the criteria adequately indicate how effectively security risk is being managed. Example 2: Define key performance indicators (KPIs), key risk indicators (KRIs), vulnerability severity scores, and other measures f... | SP-800-218 | Secure Software Development Framework (SSDF) Version 1.1 | 1.1 | 2022-02 | 2 | ssdf_practice | null | SSDF Practices > PO > PO.4 > PO.4.1 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf | 617746e553a9e2da49bfbd4eef0dfc3094758a39b869314e4173ac36605cde22 |
SP-800-218/ssdf_practice/po.4.2 | PO.4.2: Implement processes, mechanisms, etc. to gather and safeguard the necessary information in support of the criteria. Example 1: Use the toolchain to automatically gather information that informs security decision-making. Example 2: Deploy additional tools if needed to support the generation and collection of inf... | SP-800-218 | Secure Software Development Framework (SSDF) Version 1.1 | 1.1 | 2022-02 | 2 | ssdf_practice | null | SSDF Practices > PO > PO.4 > PO.4.2 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf | 617746e553a9e2da49bfbd4eef0dfc3094758a39b869314e4173ac36605cde22 |
SP-800-218/ssdf_practice/po.5.1 | PO.5.1: Separate and protect each environment involved in software development. Example 1: Use multi-factor, risk-based authentication and conditional access for each environment. Example 2: Use network segmentation and access controls to separate the environments from each other and from production environments, and t... | SP-800-218 | Secure Software Development Framework (SSDF) Version 1.1 | 1.1 | 2022-02 | 2 | ssdf_practice | null | SSDF Practices > PO > PO.5 > PO.5.1 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf | 617746e553a9e2da49bfbd4eef0dfc3094758a39b869314e4173ac36605cde22 |
SP-800-218/ssdf_practice/po.5.2 | PO.5.2: Secure and harden development endpoints (i.e., endpoints for software designers, developers, testers, builders, etc.) to perform development-related tasks using a risk-based approach. Example 1: Configure each development endpoint based on approved hardening guides, checklists, etc.; for example, enable FIPS-co... | SP-800-218 | Secure Software Development Framework (SSDF) Version 1.1 | 1.1 | 2022-02 | 2 | ssdf_practice | null | SSDF Practices > PO > PO.5 > PO.5.2 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf | 617746e553a9e2da49bfbd4eef0dfc3094758a39b869314e4173ac36605cde22 |
SP-800-218/ssdf_practice/ps.1.1 | PS.1.1: Store all forms of code - including source code, executable code, and configuration-as-code - based on the principle of least privilege so that only authorized personnel, tools, services, etc. have access. Example 1: Store all source code and configuration-as-code in a code repository, and restrict access to it... | SP-800-218 | Secure Software Development Framework (SSDF) Version 1.1 | 1.1 | 2022-02 | 2 | ssdf_practice | null | SSDF Practices > PS > PS.1 > PS.1.1 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf | 617746e553a9e2da49bfbd4eef0dfc3094758a39b869314e4173ac36605cde22 |
SP-800-218/ssdf_practice/ps.2.1 | PS.2.1: Make software integrity verification information available to software acquirers. Example 1: Post cryptographic hashes for release files on a well-secured website. Example 2: Use an established certificate authority for code signing so that consumers' operating systems or other tools and services can confirm th... | SP-800-218 | Secure Software Development Framework (SSDF) Version 1.1 | 1.1 | 2022-02 | 2 | ssdf_practice | null | SSDF Practices > PS > PS.2 > PS.2.1 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf | 617746e553a9e2da49bfbd4eef0dfc3094758a39b869314e4173ac36605cde22 |
SP-800-218/ssdf_practice/ps.3.1 | PS.3.1: Securely archive the necessary files and supporting data (e.g., integrity verification information, provenance data) to be retained for each software release. Example 1: Store the release files, associated images, etc. in repositories following the organization's established policy. Allow read-only access to th... | SP-800-218 | Secure Software Development Framework (SSDF) Version 1.1 | 1.1 | 2022-02 | 2 | ssdf_practice | null | SSDF Practices > PS > PS.3 > PS.3.1 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf | 617746e553a9e2da49bfbd4eef0dfc3094758a39b869314e4173ac36605cde22 |
SP-800-218/ssdf_practice/ps.3.2 | PS.3.2: Collect, safeguard, maintain, and share provenance data for all components of each software release (e.g., in a software bill of materials [SBOM]). Example 1: Make the provenance data available to software acquirers in accordance with the organization's policies, preferably using standards-based formats. Exampl... | SP-800-218 | Secure Software Development Framework (SSDF) Version 1.1 | 1.1 | 2022-02 | 2 | ssdf_practice | null | SSDF Practices > PS > PS.3 > PS.3.2 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf | 617746e553a9e2da49bfbd4eef0dfc3094758a39b869314e4173ac36605cde22 |
SP-800-218/ssdf_practice/pw.1.1 | PW.1.1: Use forms of risk modeling - such as threat modeling, attack modeling, or attack surface mapping - to help assess the security risk for the software. Example 1: Train the development team (security champions, in particular) or collaborate with a risk modeling expert to create models and analyze how to use a ris... | SP-800-218 | Secure Software Development Framework (SSDF) Version 1.1 | 1.1 | 2022-02 | 2 | ssdf_practice | null | SSDF Practices > PW > PW.1 > PW.1.1 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf | 617746e553a9e2da49bfbd4eef0dfc3094758a39b869314e4173ac36605cde22 |
SP-800-218/ssdf_practice/pw.1.2 | PW.1.2: Track and maintain the software's security requirements, risks, and design decisions. Example 1: Record the response to each risk, including how mitigations are to be achieved and what the rationales are for any approved exceptions to the security requirements. Add any mitigations to the software's security req... | SP-800-218 | Secure Software Development Framework (SSDF) Version 1.1 | 1.1 | 2022-02 | 2 | ssdf_practice | null | SSDF Practices > PW > PW.1 > PW.1.2 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf | 617746e553a9e2da49bfbd4eef0dfc3094758a39b869314e4173ac36605cde22 |
SP-800-218/ssdf_practice/pw.1.3 | PW.1.3: Where appropriate, build in support for using standardized security features and services (e.g., enabling software to integrate with existing log management, identity management, access control, and vulnerability management systems) instead of creating proprietary implementations of security features and servic... | SP-800-218 | Secure Software Development Framework (SSDF) Version 1.1 | 1.1 | 2022-02 | 2 | ssdf_practice | null | SSDF Practices > PW > PW.1 > PW.1.3 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf | 617746e553a9e2da49bfbd4eef0dfc3094758a39b869314e4173ac36605cde22 |
SP-800-218/ssdf_practice/pw.2.1 | PW.2.1: Have 1) a qualified person (or people) who were not involved with the design and/or 2) automated processes instantiated in the toolchain review the software design to confirm and enforce that it meets all of the security requirements and satisfactorily addresses the identified risk information. Example 1: Revie... | SP-800-218 | Secure Software Development Framework (SSDF) Version 1.1 | 1.1 | 2022-02 | 2 | ssdf_practice | null | SSDF Practices > PW > PW.2 > PW.2.1 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf | 617746e553a9e2da49bfbd4eef0dfc3094758a39b869314e4173ac36605cde22 |
SP-800-218/ssdf_practice/pw.3.2 | PW.3.2: Moved to PW.4.4 Reuse Existing, Well-Secured Software When Feasible Instead of Duplicating Functionality (PW.4): Lower the costs of software development, expedite software development, and decrease the likelihood of introducing additional security vulnerabilities into the software by reusing software modules an... | SP-800-218 | Secure Software Development Framework (SSDF) Version 1.1 | 1.1 | 2022-02 | 2 | ssdf_practice | null | SSDF Practices > PW > PW.3 > PW.3.2 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf | 617746e553a9e2da49bfbd4eef0dfc3094758a39b869314e4173ac36605cde22 |
SP-800-218/ssdf_practice/pw.4.1 | PW.4.1: Acquire and maintain well-secured software components (e.g., software libraries, modules, middleware, frameworks) from commercial, open-source, and other third-party developers for use by the organization's software. Example 1: Review and evaluate third-party software components in the context of their expected... | SP-800-218 | Secure Software Development Framework (SSDF) Version 1.1 | 1.1 | 2022-02 | 2 | ssdf_practice | null | SSDF Practices > PW > PW.4 > PW.4.1 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf | 617746e553a9e2da49bfbd4eef0dfc3094758a39b869314e4173ac36605cde22 |
SP-800-218/ssdf_practice/pw.4.2 | PW.4.2: Create and maintain well-secured software components in-house following SDLC processes to meet common internal software development needs that cannot be better met by third-party software components. Example 1: Follow organization-established security practices for secure software development when creating and ... | SP-800-218 | Secure Software Development Framework (SSDF) Version 1.1 | 1.1 | 2022-02 | 2 | ssdf_practice | null | SSDF Practices > PW > PW.4 > PW.4.2 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf | 617746e553a9e2da49bfbd4eef0dfc3094758a39b869314e4173ac36605cde22 |
SP-800-218/ssdf_practice/pw.4.3 | PW.4.3: Moved to PW.1.3 Practices Tasks Notional Implementation Examples References | SP-800-218 | Secure Software Development Framework (SSDF) Version 1.1 | 1.1 | 2022-02 | 2 | ssdf_practice | null | SSDF Practices > PW > PW.4 > PW.4.3 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf | 617746e553a9e2da49bfbd4eef0dfc3094758a39b869314e4173ac36605cde22 |
SP-800-218/ssdf_practice/pw.4.4 | PW.4.4: Verify that acquired commercial, open-source, and all other third-party software components comply with the requirements, as defined by the organization, throughout their life cycles. Example 1: Regularly check whether there are publicly known vulnerabilities in the software modules and services that vendors ha... | SP-800-218 | Secure Software Development Framework (SSDF) Version 1.1 | 1.1 | 2022-02 | 2 | ssdf_practice | null | SSDF Practices > PW > PW.4 > PW.4.4 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf | 617746e553a9e2da49bfbd4eef0dfc3094758a39b869314e4173ac36605cde22 |
SP-800-218/ssdf_practice/pw.4.5 | PW.4.5: Moved to PW.4.1 and PW.4.4 Create Source Code by Adhering to Secure Coding Practices (PW.5): Decrease the number of security vulnerabilities in the software, and reduce costs by minimizing vulnerabilities introduced during source code creation that meet or exceed organization-defined vulnerability severity crit... | SP-800-218 | Secure Software Development Framework (SSDF) Version 1.1 | 1.1 | 2022-02 | 2 | ssdf_practice | null | SSDF Practices > PW > PW.4 > PW.4.5 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf | 617746e553a9e2da49bfbd4eef0dfc3094758a39b869314e4173ac36605cde22 |
SP-800-218/ssdf_practice/pw.5.1 | PW.5.1: Follow all secure coding practices that are appropriate to the development languages and environment to meet the organization's requirements. Example 1: Validate all inputs, and validate and properly encode all outputs. Example 2: Avoid using unsafe functions and calls. Example 3: Detect errors, and handle them... | SP-800-218 | Secure Software Development Framework (SSDF) Version 1.1 | 1.1 | 2022-02 | 2 | ssdf_practice | null | SSDF Practices > PW > PW.5 > PW.5.1 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf | 617746e553a9e2da49bfbd4eef0dfc3094758a39b869314e4173ac36605cde22 |
SP-800-218/ssdf_practice/pw.5.2 | PW.5.2: Moved to PW.5.1 as example Practices Tasks Notional Implementation Examples References Configure the Compilation, Interpreter, and Build Processes to Improve Executable Security (PW.6): Decrease the number of security vulnerabilities in the software and reduce costs by eliminating vulnerabilities before testing... | SP-800-218 | Secure Software Development Framework (SSDF) Version 1.1 | 1.1 | 2022-02 | 2 | ssdf_practice | null | SSDF Practices > PW > PW.5 > PW.5.2 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf | 617746e553a9e2da49bfbd4eef0dfc3094758a39b869314e4173ac36605cde22 |
SP-800-218/ssdf_practice/pw.6.1 | PW.6.1: Use compiler, interpreter, and build tools that offer features to improve executable security. Example 1: Use up-to-date versions of compiler, interpreter, and build tools. Example 2: Follow change management processes when deploying or updating compiler, interpreter, and build tools, and audit all unexpected c... | SP-800-218 | Secure Software Development Framework (SSDF) Version 1.1 | 1.1 | 2022-02 | 2 | ssdf_practice | null | SSDF Practices > PW > PW.6 > PW.6.1 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf | 617746e553a9e2da49bfbd4eef0dfc3094758a39b869314e4173ac36605cde22 |
SP-800-218/ssdf_practice/pw.6.2 | PW.6.2: Determine which compiler, interpreter, and build tool features should be used and how each should be configured, then implement and use the approved configurations. Example 1: Enable compiler features that produce warnings for poorly secured code during the compilation process. Example 2: Implement the "clean b... | SP-800-218 | Secure Software Development Framework (SSDF) Version 1.1 | 1.1 | 2022-02 | 2 | ssdf_practice | null | SSDF Practices > PW > PW.6 > PW.6.2 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf | 617746e553a9e2da49bfbd4eef0dfc3094758a39b869314e4173ac36605cde22 |
SP-800-218/ssdf_practice/pw.7.1 | PW.7.1: Determine whether code review (a person looks directly at the code to find issues) and/or code analysis (tools are used to find issues in code, either in a fully automated way or in conjunction with a person) should be used, as defined by the organization. Example 1: Follow the organization's policies or guidel... | SP-800-218 | Secure Software Development Framework (SSDF) Version 1.1 | 1.1 | 2022-02 | 2 | ssdf_practice | null | SSDF Practices > PW > PW.7 > PW.7.1 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf | 617746e553a9e2da49bfbd4eef0dfc3094758a39b869314e4173ac36605cde22 |
SP-800-218/ssdf_practice/pw.7.2 | PW.7.2: Perform the code review and/or code analysis based on the organization's secure coding standards, and record and triage all discovered issues and recommended remediations in the development team's workflow or issue tracking system. Example 1: Perform peer review of code, and review any existing code review, ana... | SP-800-218 | Secure Software Development Framework (SSDF) Version 1.1 | 1.1 | 2022-02 | 2 | ssdf_practice | null | SSDF Practices > PW > PW.7 > PW.7.2 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf | 617746e553a9e2da49bfbd4eef0dfc3094758a39b869314e4173ac36605cde22 |
SP-800-218/ssdf_practice/pw.8.1 | PW.8.1: Determine whether executable code testing should be performed to find vulnerabilities not identified by previous reviews, analysis, or testing and, if so, which types of testing should be used. Example 1: Follow the organization's policies or guidelines for when code testing should be performed and how it shoul... | SP-800-218 | Secure Software Development Framework (SSDF) Version 1.1 | 1.1 | 2022-02 | 2 | ssdf_practice | null | SSDF Practices > PW > PW.8 > PW.8.1 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf | 617746e553a9e2da49bfbd4eef0dfc3094758a39b869314e4173ac36605cde22 |
SP-800-218/ssdf_practice/pw.8.2 | PW.8.2: Scope the testing, design the tests, perform the testing, and document the results, including recording and triaging all discovered issues and recommended remediations in the development team's workflow or issue tracking system. Example 1: Perform robust functional testing of security features. Example 2: Integ... | SP-800-218 | Secure Software Development Framework (SSDF) Version 1.1 | 1.1 | 2022-02 | 2 | ssdf_practice | null | SSDF Practices > PW > PW.8 > PW.8.2 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf | 617746e553a9e2da49bfbd4eef0dfc3094758a39b869314e4173ac36605cde22 |
SP-800-218/ssdf_practice/pw.9.1 | PW.9.1: Define a secure baseline by determining how to configure each setting that has an effect on security or a security-related setting so that the default settings are secure and do not weaken the security functions provided by the platform, network infrastructure, or services. Example 1: Conduct testing to ensure ... | SP-800-218 | Secure Software Development Framework (SSDF) Version 1.1 | 1.1 | 2022-02 | 2 | ssdf_practice | null | SSDF Practices > PW > PW.9 > PW.9.1 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf | 617746e553a9e2da49bfbd4eef0dfc3094758a39b869314e4173ac36605cde22 |
SP-800-218/ssdf_practice/pw.9.2 | PW.9.2: Implement the default settings (or groups of default settings, if applicable), and document each setting for software administrators. Example 1: Verify that the approved configuration is in place for the software. Example 2: Document each setting's purpose, options, default value, security relevance, potential ... | SP-800-218 | Secure Software Development Framework (SSDF) Version 1.1 | 1.1 | 2022-02 | 2 | ssdf_practice | null | SSDF Practices > PW > PW.9 > PW.9.2 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf | 617746e553a9e2da49bfbd4eef0dfc3094758a39b869314e4173ac36605cde22 |
SP-800-218/ssdf_practice/rv.1.1 | RV.1.1: Gather information from software acquirers, users, and public sources on potential vulnerabilities in the software and third-party components that the software uses, and investigate all credible reports. Example 1: Monitor vulnerability databases9, security mailing lists, and other sources of vulnerability repo... | SP-800-218 | Secure Software Development Framework (SSDF) Version 1.1 | 1.1 | 2022-02 | 2 | ssdf_practice | null | SSDF Practices > RV > RV.1 > RV.1.1 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf | 617746e553a9e2da49bfbd4eef0dfc3094758a39b869314e4173ac36605cde22 |
SP-800-218/ssdf_practice/rv.1.2 | RV.1.2: Review, analyze, and/or test the software's code to identify or confirm the presence of previously undetected vulnerabilities. Example 1: Configure the toolchain to perform automated code analysis and testing on a regular or continuous basis for all supported releases. Example 2: See PW.7 and PW.8. BSAFSS: VM.1... | SP-800-218 | Secure Software Development Framework (SSDF) Version 1.1 | 1.1 | 2022-02 | 2 | ssdf_practice | null | SSDF Practices > RV > RV.1 > RV.1.2 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf | 617746e553a9e2da49bfbd4eef0dfc3094758a39b869314e4173ac36605cde22 |
SP-800-218/ssdf_practice/rv.1.3 | RV.1.3: Have a policy that addresses vulnerability disclosure and remediation, and implement the roles, responsibilities, and processes needed to support that policy. Example 1: Establish a vulnerability disclosure program, and make it easy for security researchers to learn about your program and report possible vulner... | SP-800-218 | Secure Software Development Framework (SSDF) Version 1.1 | 1.1 | 2022-02 | 2 | ssdf_practice | null | SSDF Practices > RV > RV.1 > RV.1.3 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf | 617746e553a9e2da49bfbd4eef0dfc3094758a39b869314e4173ac36605cde22 |
SP-800-218/ssdf_practice/rv.2.1 | RV.2.1: Analyze each vulnerability to gather sufficient information about risk to plan its remediation or other risk response. Example 1: Use existing issue tracking software to record each vulnerability. Example 2: Perform risk calculations for each vulnerability based on estimates of its exploitability, the potential... | SP-800-218 | Secure Software Development Framework (SSDF) Version 1.1 | 1.1 | 2022-02 | 2 | ssdf_practice | null | SSDF Practices > RV > RV.2 > RV.2.1 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf | 617746e553a9e2da49bfbd4eef0dfc3094758a39b869314e4173ac36605cde22 |
SP-800-218/ssdf_practice/rv.2.2 | RV.2.2: Plan and implement risk responses for vulnerabilities. Example 1: Make a risk-based decision as to whether each vulnerability will be remediated or if the risk will be addressed through other means (e.g., risk acceptance, risk transference), and prioritize any actions to be taken. Example 2: If a permanent miti... | SP-800-218 | Secure Software Development Framework (SSDF) Version 1.1 | 1.1 | 2022-02 | 2 | ssdf_practice | null | SSDF Practices > RV > RV.2 > RV.2.2 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf | 617746e553a9e2da49bfbd4eef0dfc3094758a39b869314e4173ac36605cde22 |
SP-800-218/ssdf_practice/rv.3.1 | RV.3.1: Analyze identified vulnerabilities to determine their root causes. Example 1: Record the root cause of discovered issues. Example 2: Record lessons learned through root cause analysis in a wiki that developers can access and search. BSAFSS: VM.2-1 BSIMM: CMVM3.1, CMVM3.2 EO14028: 4e(ix) IEC62443: DM-3 ISO30111:... | SP-800-218 | Secure Software Development Framework (SSDF) Version 1.1 | 1.1 | 2022-02 | 2 | ssdf_practice | null | SSDF Practices > RV > RV.3 > RV.3.1 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf | 617746e553a9e2da49bfbd4eef0dfc3094758a39b869314e4173ac36605cde22 |
SP-800-218/ssdf_practice/rv.3.2 | RV.3.2: Analyze the root causes over time to identify patterns, such as a particular secure coding practice not being followed consistently. Example 1: Record lessons learned through root cause analysis in a wiki that developers can access and search. Example 2: Add mechanisms to the toolchain to automatically detect f... | SP-800-218 | Secure Software Development Framework (SSDF) Version 1.1 | 1.1 | 2022-02 | 2 | ssdf_practice | null | SSDF Practices > RV > RV.3 > RV.3.2 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf | 617746e553a9e2da49bfbd4eef0dfc3094758a39b869314e4173ac36605cde22 |
SP-800-218/ssdf_practice/rv.3.3 | RV.3.3: Review the software for similar vulnerabilities to eradicate a class of vulnerabilities, and proactively fix them rather than waiting for external reports. Example 1: See PW.7 and PW.8. BSAFSS: VM.2 BSIMM: CR3.3, CMVM3.1 EO14028: 4e(iv), 4e(viii), 4e(ix) IEC62443: SI-1, DM-3, DM-4 ISO30111: 7.1.4 PCISSLC: 4.2 S... | SP-800-218 | Secure Software Development Framework (SSDF) Version 1.1 | 1.1 | 2022-02 | 2 | ssdf_practice | null | SSDF Practices > RV > RV.3 > RV.3.3 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf | 617746e553a9e2da49bfbd4eef0dfc3094758a39b869314e4173ac36605cde22 |
SP-800-218/ssdf_practice/rv.3.4 | RV.3.4: Review the SDLC process, and update it if appropriate to prevent (or reduce the likelihood of) the root cause recurring in updates to the software or in new software that is created. Example 1: Record lessons learned through root cause analysis in a wiki that developers can access and search. Example 2: Plan an... | SP-800-218 | Secure Software Development Framework (SSDF) Version 1.1 | 1.1 | 2022-02 | 2 | ssdf_practice | null | SSDF Practices > RV > RV.3 > RV.3.4 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf | 617746e553a9e2da49bfbd4eef0dfc3094758a39b869314e4173ac36605cde22 |
SP-800-218A/section/2.-using-the-ssdf-community-profile | 2. Using the SSDF Community Profile
AI model producers, AI system producers, AI system acquirers, and others can use the SSDF to
foster their communications regarding secure AI model development throughout the software
development life cycle.2 Following SSDF practices should help AI model producers reduce the
number o... | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | section | null | Section 4.1.a of Executive Order (EO) 14110, Safe, Secure, and Trustworthy Development and > 2. Using the SSDF Community Profile | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/section/2.0-8-security-and-privacy-controls-for-information-systems-and-organizations-9-and | 2.0 [8], Security and Privacy Controls for Information Systems and Organizations [9], and
Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations
[10].
• AI model developers, AI researchers, AI system developers, and secure software | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | section | null | Section 4.1.a of Executive Order (EO) 14110, Safe, Secure, and Trustworthy Development and > 2.0 [8], Security and Privacy Controls for Information Systems and Organizations [9], and | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/section/4 | 2e2023. https://doi.org/10.6028/NIST.AI.100-2e2023
[4]
Schwartz R, Vassilev A, Greene K, Perine L, Burt A, Hall P (2022) Towards a Standard for
Identifying and Managing Bias in Artificial Intelligence. (National Institute of Standards
and Technology, Gaithersburg, MD), NIST Special Publication (SP) 1270. | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | section | null | Section 4.1.a of Executive Order (EO) 14110, Safe, Secure, and Trustworthy Development and > [4] | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/section/9 | MD.) Available at https://pages.nist.gov/dioptra/
Souppaya MP, Scarfone KA, Dodson DF (2022) Secure Software Development
Framework (SSDF) Version 1.1: Recommendations for Mitigating the Risk of Software
NIST Special Publication (SP) 800-218. https://doi.org/10.6028/NIST.SP.800-218
[7]
Executive Order 14028 (2021) ... | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | section | null | Section 4.1.a of Executive Order (EO) 14110, Safe, Secure, and Trustworthy Development and > [9] | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/section/abstract | Abstract
This document augments the secure software development practices and tasks defined in
Secure Software Development Framework (SSDF) version 1.1 by adding practices, tasks,
recommendations, considerations, notes, and informative references that are specific to AI
model development throughout the software develo... | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | section | null | Abstract | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/section/artificial-intelligence-model | Available at https://ieeexplore.ieee.org/book/9562694
artificial intelligence
A machine-based system that can, for a given set of human-defined objectives, make predictions,
recommendations, or decisions influencing real or virtual environments. [1]
artificial intelligence model
A component of an information system... | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | section | null | Appendix A. Glossary > artificial intelligence model | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/section/https-airc.nist.gov-ai-rmf-knowledge-base-playbook | Supply Chain Risk Management Practices for Systems and Organizations. (National
Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP)
800-161r1. https://doi.org/10.6028/NIST.SP.800-161r1
https://airc.nist.gov/AI_RMF_Knowledge_Base/Playbook
Management Framework: Generative Artificia... | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | section | null | Section 4.1.a of Executive Order (EO) 14110, Safe, Secure, and Trustworthy Development and > https://airc.nist.gov/AI_RMF_Knowledge_Base/Playbook | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/section/intelligence-risk-management-framework-ai-rmf-1.0-2-adversarial-machine | This document leverages and integrates numerous sources of expertise, including:
• NIST research and publications on trustworthy and responsible AI, including the Artificial
Intelligence Risk Management Framework (AI RMF 1.0) [2], Adversarial Machine
Learning: A Taxonomy and Terminology of Attacks and Mitigations [3... | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | section | null | Section 4.1.a of Executive Order (EO) 14110, Safe, Secure, and Trustworthy Development and > Intelligence Risk Management Framework (AI RMF 1.0) [2], Adversarial Machine | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/section/o-n-note-additional-information-besides-recommendations-and-considerations | Each item has an ID starting with one of the following:
o "R" (recommendation: something the organization should do)
o "C" (consideration: something the organization should consider doing)
o "N" (note: additional information besides recommendations and considerations)
An R, C, or N designation and its number can be... | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | section | null | Section 4.1.a of Executive Order (EO) 14110, Safe, Secure, and Trustworthy Development and > o “N” (note: additional information besides recommendations and considerations) | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/section/purpose | Purpose
The SSDF provides a common language for describing secure software development practices
throughout the software development life cycle. This document augments the practices and
tasks defined in SSDF version 1.1 by adding recommendations, considerations, notes, and
informative references that are specific to g... | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | section | null | Section 4.1.a of Executive Order (EO) 14110, Safe, Secure, and Trustworthy Development and > Purpose | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/section/scope | Scope
This Profile's scope is AI model development, which includes data sourcing for, designing,
training, fine-tuning, and evaluating AI models, as well as incorporating and integrating AI
models into other software. Consistent with SSDF version 1.1 and EO 14110, practices for the
deployment and operation of AI syste... | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | section | null | Section 4.1.a of Executive Order (EO) 14110, Safe, Secure, and Trustworthy Development and > Scope | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/section/section-4.1.a-of-executive-order-eo-14110-safe-secure-and-trustworthy-development-and | Section 4.1.a of Executive Order (EO) 14110, Safe, Secure, and Trustworthy Development and
Use of Artificial Intelligence [1], tasked NIST with "developing a companion resource to the
Secure Software Development Framework to incorporate secure development practices for
generative AI and for dual-use foundation models.... | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | section | null | Section 4.1.a of Executive Order (EO) 14110, Safe, Secure, and Trustworthy Development and | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/ssdf_practice/po.1.1 | PO.1.1: Identify and document all security requirements for the organization's software development infrastructures and processes, and maintain the requirements over time. High R1: Include AI model development in the security requirements for software development infrastructure and processes. R2: Identify and select ap... | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | ssdf_practice | null | SSDF Practices > PO > PO.1 > PO.1.1 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/ssdf_practice/po.1.2 | PO.1.2: Identify and document all security requirements for organization-developed software to meet, and maintain the requirements over time. High R1: Organizational policies should support all current requirements specific to AI model development security for organization-developed software. These requirements should ... | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | ssdf_practice | null | SSDF Practices > PO > PO.1 > PO.1.2 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/ssdf_practice/po.1.3 | PO.1.3: Communicate requirements to all third parties who will provide commercial software components to the organization for use by the organization's own software. [Modified from SSDF 1.1] Medium R1: Include AI model development security in the requirements being communicated for third-party software components. AI R... | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | ssdf_practice | null | SSDF Practices > PO > PO.1 > PO.1.3 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/ssdf_practice/po.2.1 | PO.2.1: Create new roles and alter responsibilities for existing roles as needed to encompass all parts of the SDLC. Periodically review and maintain the defined roles and responsibilities, updating them as needed. High R1: Include AI model development security in SDLC-related roles and responsibilities throughout the ... | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | ssdf_practice | null | SSDF Practices > PO > PO.2 > PO.2.1 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/ssdf_practice/po.2.2 | PO.2.2: Provide role-based training for all personnel with responsibilities that contribute to secure development. Periodically review personnel proficiency and role-based training, and update the training as needed. High R1: Role-based training should include understanding cybersecurity vulnerabilities and threats to ... | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | ssdf_practice | null | SSDF Practices > PO > PO.2 > PO.2.2 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/ssdf_practice/po.2.3 | PO.2.3: Obtain upper management or authorizing official commitment to secure development, and convey that commitment to all with developmentrelated roles and responsibilities. Medium R1: Leadership should commit to secure development practices involving AI models. AI RMF: Govern 2.3 Implement Supporting Toolchains (PO.... | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | ssdf_practice | null | SSDF Practices > PO > PO.2 > PO.2.3 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/ssdf_practice/po.3.1 | PO.3.1: Specify which tools or tool types must or should be included in each toolchain to mitigate identified risks, as well as how the toolchain components are to be integrated with each other. High R1: Plan to develop and implement automated toolchains that secure AI model development and reduce human effort, especia... | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | ssdf_practice | null | SSDF Practices > PO > PO.3 > PO.3.1 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/ssdf_practice/po.3.2 | PO.3.2: Follow recommended security practices to deploy, operate, and maintain tools and toolchains. High R1: Execute the plan to develop and implement automated toolchains that secure AI model development and reduce human effort, especially at the scale often used by AI models. R2: Verify the security of toolchains at... | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | ssdf_practice | null | SSDF Practices > PO > PO.3 > PO.3.2 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/ssdf_practice/po.3.3 | PO.3.3: Configure tools to generate artifacts of their support of secure software development practices as defined by the organization. Medium N1: An artifact is "a piece of evidence" [16]. Evidence is "grounds for belief or disbelief; data on which to base proof or to establish truth or falsehood" [17]. Artifacts prov... | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | ssdf_practice | null | SSDF Practices > PO > PO.3 > PO.3.3 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/ssdf_practice/po.4.1 | PO.4.1: Define criteria for software security checks and track throughout the SDLC. Medium R1: Implement guardrails and other controls throughout the AI development life cycle, extending beyond the traditional SDLC. C1: Consider requiring review and approval from a human-in-the-loop for software security checks beyond ... | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | ssdf_practice | null | SSDF Practices > PO > PO.4 > PO.4.1 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/ssdf_practice/po.4.2 | PO.4.2: Implement processes, mechanisms, etc. to gather and safeguard the necessary information in support of the criteria. Low No additions to SSDF 1.1 AI RMF: Measure 2.3, 2.7; Manage 1.1 OWASP: LLM01-2 Implement and Maintain Secure Environments for Software Development (PO.5): Ensure that all components of the envir... | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | ssdf_practice | null | SSDF Practices > PO > PO.4 > PO.4.2 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/ssdf_practice/po.5.1 | PO.5.1: Separate and protect each environment involved in software development. High C1: Consider separating execution environments from each other to the extent feasible, such as through isolation, segmentation, containment, access via APIs, or other means. R1: Monitor, track, and limit resource usage and rates for AI... | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | ssdf_practice | null | SSDF Practices > PO > PO.5 > PO.5.1 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/ssdf_practice/po.5.2 | PO.5.2: Secure and harden development endpoints (endpoints for software designers, developers, testers, builders, etc.) to perform development tasks using a risk-based approach. Medium No additions to SSDF 1.1 OWASP: LLM01-1, LLM05-3, LLM05-9, | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | ssdf_practice | null | SSDF Practices > PO > PO.5 > PO.5.2 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/ssdf_practice/po.5.3 | PO.5.3: Continuously monitor software execution performance and behavior in software development environments to identify potential suspicious activity and other issues. [Not part of SSDF 1.1] High R1: Perform continuous security monitoring for all development environment components that host an AI model or related res... | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | ssdf_practice | null | SSDF Practices > PO > PO.5 > PO.5.3 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/ssdf_practice/ps.1.1 | PS.1.1: Store all forms of code - including source code, executable code, and configuration-as-code - based on the principle of least privilege so that only authorized personnel, tools, services, etc. have access. High R1: Secure code storage should include AI models, model weights, pipelines, reward models, and any ot... | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | ssdf_practice | null | SSDF Practices > PS > PS.1 > PS.1.1 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/ssdf_practice/ps.1.2 | PS.1.2: Protect all training, testing, fine-tuning, and aligning data from unauthorized access and modification. [Not part of SSDF 1.1] High R1: Continuously monitor the confidentiality (for non-public data only) and integrity of training, testing, fine-tuning, and aligning data. C1: Consider securely storing training,... | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | ssdf_practice | null | SSDF Practices > PS > PS.1 > PS.1.2 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/ssdf_practice/ps.1.3 | PS.1.3: Protect all model weights and configuration parameter data from unauthorized access and modification. [Not part of SSDF 1.1] High R1: Keep model weights and configuration parameters separate from training, testing, fine-tuning, and aligning data. R2: Continuously monitor the confidentiality (for closed models o... | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | ssdf_practice | null | SSDF Practices > PS > PS.1 > PS.1.3 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/ssdf_practice/ps.2.1 | PS.2.1: Make software integrity verification information available to software acquirers. Medium R1: Generate and provide cryptographic hashes or digital signatures for an AI model and its components, artifacts, and documentation. R2: Provide digital signatures for AI model changes. OWASP: LLM05-6 Archive and Protect E... | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | ssdf_practice | null | SSDF Practices > PS > PS.2 > PS.2.1 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/ssdf_practice/ps.3.1 | PS.3.1: Securely archive the necessary files and supporting data (e.g., integrity Low R1: Perform versioning and tracking for infrastructure tools (e.g., pre-processing, OWASP: LLM10 Practice Task Priority Recommendations [R], Considerations [C], and Notes [N] Specific to AI Model Development Informative References hel... | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | ssdf_practice | null | SSDF Practices > PS > PS.3 > PS.3.1 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/ssdf_practice/ps.3.2 | PS.3.2: Collect, safeguard, maintain, and share provenance data for all components of each software release (e.g., in a software bill of materials [SBOM], through Supply-chain Levels for Software Artifacts [SLSA]). [Modified from SSDF 1.1] Medium R1: Track the provenance of an AI model and its components and derivative... | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | ssdf_practice | null | SSDF Practices > PS > PS.3 > PS.3.2 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/ssdf_practice/pw.1.1 | PW.1.1: Use forms of risk modeling - such as threat modeling, attack modeling, or attack surface mapping - to help assess the security risk for the software. High R1: Incorporate relevant AI model-specific vulnerability and threat types in risk modeling. Examples of these vulnerability and threat types include poisonin... | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | ssdf_practice | null | SSDF Practices > PW > PW.1 > PW.1.1 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/ssdf_practice/pw.1.2 | PW.1.2: Track and maintain the software's security requirements, risks, and design decisions. Medium No additions to SSDF 1.1 AI RMF: Govern 4.1, 4.2; Map 2.1, 2.2, 2.3, 3.2, 3.3, 4.1, 4.2, 5.2; Manage 1.2, 1.3, 1.4 | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | ssdf_practice | null | SSDF Practices > PW > PW.1 > PW.1.2 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/ssdf_practice/pw.1.3 | PW.1.3: Where appropriate, build in support for using standardized security features and services (e.g., enabling software to integrate with existing log management, identity management, access control, and vulnerability management systems) instead of creating proprietary implementations of security features and servic... | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | ssdf_practice | null | SSDF Practices > PW > PW.1 > PW.1.3 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/ssdf_practice/pw.2.1 | PW.2.1: Have 1) a qualified person (or people) who were not involved with the design and 2) automated processes instantiated in the toolchain review the software design to confirm and enforce that it meets all of the security requirements and satisfactorily addresses the identified risk information. [Modified from SSDF... | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | ssdf_practice | null | SSDF Practices > PW > PW.2 > PW.2.1 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/ssdf_practice/pw.3.1 | PW.3.1: Analyze data for signs of data poisoning, bias, homogeneity, and tampering before using it for AI model training, testing, fine-tuning, or aligning High R1: Verify the provenance (when known) and integrity of training, testing, fine-tuning, and aligning data before use. AI RMF: Measure 2.1; Manage 1.2, 1.3 Prac... | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | ssdf_practice | null | SSDF Practices > PW > PW.3 > PW.3.1 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/ssdf_practice/pw.3.2 | PW.3.2: Track the provenance, when known, of all training, testing, fine-tuning, and aligning data used for an AI model, and document which data do not have known provenance. [Not part of SSDF 1.1] Medium N1: Provenance verification is not possible in all cases because provenance is not always known. However, it is sti... | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | ssdf_practice | null | SSDF Practices > PW > PW.3 > PW.3.2 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/ssdf_practice/pw.3.3 | PW.3.3: Include adversarial samples in the training and testing data to improve attack prevention. [Not part of SSDF 1.1] Medium R1: Use a process and corresponding controls to test the adversarial samples and put appropriate guardrails on training and testing use. OWASP: LLM03-6, LLM05-7 Adv ML Reuse Existing, Well-Se... | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | ssdf_practice | null | SSDF Practices > PW > PW.3 > PW.3.3 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/ssdf_practice/pw.4.1 | PW.4.1: Acquire and maintain well-secured software components (e.g., software libraries, modules, middleware, frameworks) from commercial, open-source, and other third-party developers for use by the organization's software. Medium C1: Consider using an existing AI model instead of creating a new one. OWASP: LLM05 | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | ssdf_practice | null | SSDF Practices > PW > PW.4 > PW.4.1 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/ssdf_practice/pw.4.2 | PW.4.2: Create and maintain well-secured software components in-house following SDLC processes to meet common internal software development needs that cannot be better met by third-party software components. Low No additions to SSDF 1.1 | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | ssdf_practice | null | SSDF Practices > PW > PW.4 > PW.4.2 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/ssdf_practice/pw.4.4 | PW.4.4: Verify that acquired commercial, open-source, and all other third-party software components comply with the High R1: Verify the integrity, provenance, and security of an existing AI model or any other acquired AI components - including training, testing, fine-tuning, and aligning datasets; OWASP: LLM05-2, LLM05... | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | ssdf_practice | null | SSDF Practices > PW > PW.4 > PW.4.4 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/ssdf_practice/pw.5.1 | PW.5.1: Follow all secure coding practices that are appropriate to the development languages and environment to meet the organization's requirements. High R1: Expand secure coding practices to include AI technology-specific considerations. R2: Code the handling of inputs (including prompts and user data) and outputs ca... | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | ssdf_practice | null | SSDF Practices > PW > PW.5 > PW.5.1 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/ssdf_practice/pw.6.1 | PW.6.1: Use compiler, interpreter, and build tools that offer features to improve executable security. Low C1: Consider using secure model serialization mechanisms that reduce or eliminate vectors for the introduction of malicious content. | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | ssdf_practice | null | SSDF Practices > PW > PW.6 > PW.6.1 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/ssdf_practice/pw.6.2 | PW.6.2: Determine which compiler, interpreter, and build tool features should be used and how each should be configured, then implement and use the approved configurations. Low C1: Consider capturing compiler, interpreter, and build tool versions and features as part of the provenance tracking. Review and/or Analyze Hu... | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | ssdf_practice | null | SSDF Practices > PW > PW.6 > PW.6.2 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/ssdf_practice/pw.7.1 | PW.7.1: Determine whether code review (a person looks directly at the code to find issues) and/or code analysis (tools are used to find issues in code, either in a fully automated way or in conjunction with a person) should be used, as defined by the organization. Medium R1: Code review and analysis policies or guideli... | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | ssdf_practice | null | SSDF Practices > PW > PW.7 > PW.7.1 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/ssdf_practice/pw.7.2 | PW.7.2: Perform the code review and/or code analysis based on the organization's secure coding standards, and record and triage all discovered issues and recommended remediations in the High R1: Scan all AI models for malware, vulnerabilities, backdoors, and other security issues in accordance with the organization's c... | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | ssdf_practice | null | SSDF Practices > PW > PW.7 > PW.7.2 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/ssdf_practice/pw.8.1 | PW.8.1: Determine whether executable code testing should be performed to find vulnerabilities not identified by previous reviews, analysis, or testing and, if so, which types of testing should be used. High R1: Include AI models in code testing policies and guidelines. Several forms of code testing can be used for AI m... | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | ssdf_practice | null | SSDF Practices > PW > PW.8 > PW.8.1 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/ssdf_practice/pw.8.2 | PW.8.2: Scope the testing, design the tests, perform the testing, and document the results, including recording and triaging all discovered issues and recommended remediations in the development team's workflow or issue tracking system. High R1: Test all AI models for vulnerabilities in accordance with the organization... | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | ssdf_practice | null | SSDF Practices > PW > PW.8 > PW.8.2 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/ssdf_practice/pw.9.1 | PW.9.1: Define a secure baseline by determining how to configure each setting that has an effect on security or a security-related setting so that the default settings are secure and do not weaken the security functions provided by the platform, network infrastructure, or services. Medium No additions to SSDF 1.1 AI RM... | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | ssdf_practice | null | SSDF Practices > PW > PW.9 > PW.9.1 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/ssdf_practice/pw.9.2 | PW.9.2: Implement the default settings (or groups of default settings, if applicable), and document each setting for software administrators. Medium N1: Documenting settings can be performed earlier in the process, such as when defining a secure baseline (see PW.9.1). AI RMF: Measure 2.7; Manage 1.2, 1.3, 1.4 Respond t... | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | ssdf_practice | null | SSDF Practices > PW > PW.9 > PW.9.2 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/ssdf_practice/rv.1.1 | RV.1.1: Gather information from software acquirers, users, and public sources on potential vulnerabilities in the software High R1: Log, monitor, and analyze all inputs and outputs for AI models to detect possible security and performance issues (see PO.5.3). AI RMF: Govern 4.3, 5.1, 6.1, 6.2; Practice Task Priority Re... | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | ssdf_practice | null | SSDF Practices > RV > RV.1 > RV.1.1 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
SP-800-218A/ssdf_practice/rv.1.2 | RV.1.2: Review, analyze, and/or test the software's code to identify or confirm the presence of previously undetected vulnerabilities. Medium R1: Scan and test AI models frequently to identify previously undetected vulnerabilities. R2: Rely mainly on automation for ongoing scanning and testing, and involve a human-inth... | SP-800-218A | Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile | Initial | 2024-07 | 2 | ssdf_practice | null | SSDF Practices > RV > RV.1 > RV.1.2 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218A.pdf | e088c8bc75716824dae7c36a987f408364638561d381ed001b5c12254a7b10d8 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.