ezesecops/rmf-ato-core huggingface dataset:
Security and Privacy Controls for Information Systems and Organizations
SA > SA-10 > SA-10(4)

SA-10(4) Developer Configuration Management | Trusted Generation
Family: System and Services Acquisition (SA) > SA-10 Developer Configuration Management

Require the developer of the system, system component, or system service to employ tools for comparing newly generated versions of security-relevant hardware descriptions, source code, and object code with previous versions.
Security and Privacy Controls for Information Systems and Organizations
SA > SA-10 > SA-10(5) > Discussion

SA-10(5) Mapping Integrity for Version Control - Discussion
Family: System and Services Acquisition (SA) > SA-10 Developer Configuration Management

Mapping integrity for version control addresses changes to hardware, software, and firmware components during both initial development and system development life cycle updates. Maintaining the integrity between the master copies of security-relevant hardware, software, and firmware (including designs, hardware drawings, source code) and the equivalent data in master copies in operational environments is essential to ensuring the availability of organizational systems that support critical mission and business functions.
Security and Privacy Controls for Information Systems and Organizations
SA > SA-10 > SA-10(5)

SA-10(5) Developer Configuration Management | Mapping Integrity for Version Control
Family: System and Services Acquisition (SA) > SA-10 Developer Configuration Management

Require the developer of the system, system component, or system service to maintain the integrity of the mapping between the master build data describing the current version of security-relevant hardware, software, and firmware and the on-site master copy of the data for the current version.
Security and Privacy Controls for Information Systems and Organizations
SA > SA-10 > SA-10(6) > Discussion

SA-10(6) Trusted Distribution - Discussion
Family: System and Services Acquisition (SA) > SA-10 Developer Configuration Management

The trusted distribution of security-relevant hardware, software, and firmware updates help to ensure that the updates are correct representations of the master copies maintained by the developer and have not been tampered with during distribution.
Security and Privacy Controls for Information Systems and Organizations
SA > SA-10 > SA-10(6)

SA-10(6) Developer Configuration Management | Trusted Distribution
Family: System and Services Acquisition (SA) > SA-10 Developer Configuration Management

Require the developer of the system, system component, or system service to execute procedures for ensuring that security-relevant hardware, software, and firmware updates distributed to the organization are exactly as specified by the master copies.
Security and Privacy Controls for Information Systems and Organizations
SA > SA-10 > SA-10(7) > Discussion

SA-10(7) Security and Privacy Representatives - Discussion
Family: System and Services Acquisition (SA) > SA-10 Developer Configuration Management

Information security and privacy representatives can include system security officers, senior agency information security officers, senior agency officials for privacy, and system privacy officers. Representation by personnel with information security and privacy expertise is important because changes to system configurations can have unintended side effects, some of which may be security- or privacy-relevant. Detecting such changes early in the process can help avoid unintended, negative consequences that could ultimately affect the security and privacy posture of systems. The configuration change management and control process in this control enhancement refers to the change management and control process defined by organizations in [SA-10b](#sa-10_smt.b).
Security and Privacy Controls for Information Systems and Organizations
SA > SA-10 > SA-10(7)

SA-10(7) Developer Configuration Management | Security and Privacy Representatives
Family: System and Services Acquisition (SA) > SA-10 Developer Configuration Management

Require [Assignment: organization-defined organization-defined security and privacy representatives] to be included in the [Assignment: organization-defined organization-defined configuration change management and control process].
Security and Privacy Controls for Information Systems and Organizations
SA > SA-11

SA-11 Developer Testing and Evaluation
Family: System and Services Acquisition (SA)

Require the developer of the system, system component, or system service, at all post-design stages of the system development life cycle, to:
a. Develop and implement a plan for ongoing security and privacy control assessments;
b. Perform [Selection; one or more: unit; integration; system; regression] testing/evaluation [Assignment: organization-defined frequency to conduct] at [Assignment: organization-defined depth and coverage];
c. Produce evidence of the execution of the assessment plan and the results of the testing and evaluation;
d. Implement a verifiable flaw remediation process; and
e. Correct flaws identified during testing and evaluation.
Security and Privacy Controls for Information Systems and Organizations
SA > SA-11 > Discussion

SA-11 Developer Testing and Evaluation - Discussion
Family: System and Services Acquisition (SA)

Developmental testing and evaluation confirms that the required controls are implemented correctly, operating as intended, enforcing the desired security and privacy policies, and meeting established security and privacy requirements. Security properties of systems and the privacy of individuals may be affected by the interconnection of system components or changes to those components. The interconnections or changes-including upgrading or replacing applications, operating systems, and firmware-may adversely affect previously implemented controls. Ongoing assessment during development allows for additional types of testing and evaluation that developers can conduct to reduce or eliminate potential flaws. Testing custom software applications may require approaches such as manual code review, security architecture review, and penetration testing, as well as and static analysis, dynamic analysis, binary analysis, or a hybrid of the three analysis approaches.

Developers can use the analysis approaches, along with security instrumentation and fuzzing, in a variety of tools and in source code reviews. The security and privacy assessment plans include the specific activities that developers plan to carry out, including the types of analyses, testing, evaluation, and reviews of software and firmware components; the degree of rigor to be applied; the frequency of the ongoing testing and evaluation; and the types of artifacts produced during those processes. The depth of testing and evaluation refers to the rigor and level of detail associated with the assessment process. The coverage of testing and evaluation refers to the scope (i.e., number and type) of the artifacts included in the assessment process. Contracts specify the acceptance criteria for security and privacy assessment plans, flaw remediation processes, and the evidence that the plans and processes have been diligently applied. Methods for reviewing and protecting assessment plans, evidence, and documentation are commensurate with the security category or classification level of the system. Contracts may specify protection requirements for documentation.
Security and Privacy Controls for Information Systems and Organizations
SA > SA-11 > SA-11(1) > Discussion

SA-11(1) Static Code Analysis - Discussion
Family: System and Services Acquisition (SA) > SA-11 Developer Testing and Evaluation

Static code analysis provides a technology and methodology for security reviews and includes checking for weaknesses in the code as well as for the incorporation of libraries or other included code with known vulnerabilities or that are out-of-date and not supported. Static code analysis can be used to identify vulnerabilities and enforce secure coding practices. It is most effective when used early in the development process, when each code change can automatically be scanned for potential weaknesses. Static code analysis can provide clear remediation guidance and identify defects for developers to fix. Evidence of the correct implementation of static analysis can include aggregate defect density for critical defect types, evidence that defects were inspected by developers or security professionals, and evidence that defects were remediated. A high density of ignored findings, commonly referred to as false positives, indicates a potential problem with the analysis process or the analysis tool. In such cases, organizations weigh the validity of the evidence against evidence from other sources.
Security and Privacy Controls for Information Systems and Organizations
SA > SA-11 > SA-11(1)

SA-11(1) Developer Testing and Evaluation | Static Code Analysis
Family: System and Services Acquisition (SA) > SA-11 Developer Testing and Evaluation

Require the developer of the system, system component, or system service to employ static code analysis tools to identify common flaws and document the results of the analysis.
Security and Privacy Controls for Information Systems and Organizations
SA > SA-11 > SA-11(2) > Discussion

SA-11(2) Threat Modeling and Vulnerability Analyses - Discussion
Family: System and Services Acquisition (SA) > SA-11 Developer Testing and Evaluation

Systems, system components, and system services may deviate significantly from the functional and design specifications created during the requirements and design stages of the system development life cycle. Therefore, updates to threat modeling and vulnerability analyses of those systems, system components, and system services during development and prior to delivery are critical to the effective operation of those systems, components, and services. Threat modeling and vulnerability analyses at this stage of the system development life cycle ensure that design and implementation changes have been accounted for and that vulnerabilities created because of those changes have been reviewed and mitigated.
Security and Privacy Controls for Information Systems and Organizations
SA > SA-11 > SA-11(2)

SA-11(2) Developer Testing and Evaluation | Threat Modeling and Vulnerability Analyses
Family: System and Services Acquisition (SA) > SA-11 Developer Testing and Evaluation

Require the developer of the system, system component, or system service to perform threat modeling and vulnerability analyses during development and the subsequent testing and evaluation of the system, component, or service that:
(a) Uses the following contextual information: [Assignment: organization-defined information];
(b) Employs the following tools and methods: [Assignment: organization-defined tools and methods];
(c) Conducts the modeling and analyses at the following level of rigor: [Assignment: organization-defined organization-defined breadth and depth of modeling and analyses] ; and
(d) Produces evidence that meets the following acceptance criteria: [Assignment: organization-defined organization-defined acceptance criteria].
Security and Privacy Controls for Information Systems and Organizations
SA > SA-11 > SA-11(3) > Discussion

SA-11(3) Independent Verification of Assessment Plans and Evidence - Discussion
Family: System and Services Acquisition (SA) > SA-11 Developer Testing and Evaluation

Independent agents have the qualifications-including the expertise, skills, training, certifications, and experience-to verify the correct implementation of developer security and privacy assessment plans.
Security and Privacy Controls for Information Systems and Organizations
SA > SA-11 > SA-11(3)

SA-11(3) Developer Testing and Evaluation | Independent Verification of Assessment Plans and Evidence
Family: System and Services Acquisition (SA) > SA-11 Developer Testing and Evaluation

(a) Require an independent agent satisfying [Assignment: organization-defined independence criteria] to verify the correct implementation of the developer security and privacy assessment plans and the evidence produced during testing and evaluation; and
(b) Verify that the independent agent is provided with sufficient information to complete the verification process or granted the authority to obtain such information.
Security and Privacy Controls for Information Systems and Organizations
SA > SA-11 > SA-11(4) > Discussion

SA-11(4) Manual Code Reviews - Discussion
Family: System and Services Acquisition (SA) > SA-11 Developer Testing and Evaluation

Manual code reviews are usually reserved for the critical software and firmware components of systems. Manual code reviews are effective at identifying weaknesses that require knowledge of the application's requirements or context that, in most cases, is unavailable to automated analytic tools and techniques, such as static and dynamic analysis. The benefits of manual code review include the ability to verify access control matrices against application controls and review detailed aspects of cryptographic implementations and controls.
Security and Privacy Controls for Information Systems and Organizations
SA > SA-11 > SA-11(4)

SA-11(4) Developer Testing and Evaluation | Manual Code Reviews
Family: System and Services Acquisition (SA) > SA-11 Developer Testing and Evaluation

Require the developer of the system, system component, or system service to perform a manual code review of [Assignment: organization-defined specific code] using the following processes, procedures, and/or techniques: [Assignment: organization-defined processes, procedures, and/or techniques].
Security and Privacy Controls for Information Systems and Organizations
SA > SA-11 > SA-11(5) > Discussion

SA-11(5) Penetration Testing - Discussion
Family: System and Services Acquisition (SA) > SA-11 Developer Testing and Evaluation

Penetration testing is an assessment methodology in which assessors, using all available information technology product or system documentation and working under specific constraints, attempt to circumvent the implemented security and privacy features of information technology products and systems. Useful information for assessors who conduct penetration testing includes product and system design specifications, source code, and administrator and operator manuals. Penetration testing can include white-box, gray-box, or black-box testing with analyses performed by skilled professionals who simulate adversary actions. The objective of penetration testing is to discover vulnerabilities in systems, system components, and services that result from implementation errors, configuration faults, or other operational weaknesses or deficiencies. Penetration tests can be performed in conjunction with automated and manual code reviews to provide a greater level of analysis than would ordinarily be possible. When user session information and other personally identifiable information is captured or recorded during penetration testing, such information is handled appropriately to protect privacy.
Security and Privacy Controls for Information Systems and Organizations
SA > SA-11 > SA-11(5)

SA-11(5) Developer Testing and Evaluation | Penetration Testing
Family: System and Services Acquisition (SA) > SA-11 Developer Testing and Evaluation

Require the developer of the system, system component, or system service to perform penetration testing:
(a) At the following level of rigor: [Assignment: organization-defined organization-defined breadth and depth of testing] ; and
(b) Under the following constraints: [Assignment: organization-defined constraints].
Security and Privacy Controls for Information Systems and Organizations
SA > SA-11 > SA-11(6) > Discussion

SA-11(6) Attack Surface Reviews - Discussion
Family: System and Services Acquisition (SA) > SA-11 Developer Testing and Evaluation

Attack surfaces of systems and system components are exposed areas that make those systems more vulnerable to attacks. Attack surfaces include any accessible areas where weaknesses or deficiencies in the hardware, software, and firmware components provide opportunities for adversaries to exploit vulnerabilities. Attack surface reviews ensure that developers analyze the design and implementation changes to systems and mitigate attack vectors generated as a result of the changes. The correction of identified flaws includes deprecation of unsafe functions.
Security and Privacy Controls for Information Systems and Organizations
SA > SA-11 > SA-11(6)

SA-11(6) Developer Testing and Evaluation | Attack Surface Reviews
Family: System and Services Acquisition (SA) > SA-11 Developer Testing and Evaluation

Require the developer of the system, system component, or system service to perform attack surface reviews.
Security and Privacy Controls for Information Systems and Organizations
SA > SA-11 > SA-11(7) > Discussion

SA-11(7) Verify Scope of Testing and Evaluation - Discussion
Family: System and Services Acquisition (SA) > SA-11 Developer Testing and Evaluation

Verifying that testing and evaluation provides complete coverage of required controls can be accomplished by a variety of analytic techniques ranging from informal to formal. Each of these techniques provides an increasing level of assurance that corresponds to the degree of formality of the analysis. Rigorously demonstrating control coverage at the highest levels of assurance can be achieved using formal modeling and analysis techniques, including correlation between control implementation and corresponding test cases.
Security and Privacy Controls for Information Systems and Organizations
SA > SA-11 > SA-11(7)

SA-11(7) Developer Testing and Evaluation | Verify Scope of Testing and Evaluation
Family: System and Services Acquisition (SA) > SA-11 Developer Testing and Evaluation

Require the developer of the system, system component, or system service to verify that the scope of testing and evaluation provides complete coverage of the required controls at the following level of rigor: [Assignment: organization-defined organization-defined breadth and depth of testing and evaluation].
Security and Privacy Controls for Information Systems and Organizations
SA > SA-11 > SA-11(8) > Discussion

SA-11(8) Dynamic Code Analysis - Discussion
Family: System and Services Acquisition (SA) > SA-11 Developer Testing and Evaluation

Dynamic code analysis provides runtime verification of software programs using tools capable of monitoring programs for memory corruption, user privilege issues, and other potential security problems. Dynamic code analysis employs runtime tools to ensure that security functionality performs in the way it was designed. A type of dynamic analysis, known as fuzz testing, induces program failures by deliberately introducing malformed or random data into software programs. Fuzz testing strategies are derived from the intended use of applications and the functional and design specifications for the applications. To understand the scope of dynamic code analysis and the assurance provided, organizations may also consider conducting code coverage analysis (i.e., checking the degree to which the code has been tested using metrics such as percent of subroutines tested or percent of program statements called during execution of the test suite) and/or concordance analysis (i.e., checking for words that are out of place in software code, such as non-English language words or derogatory terms).
Security and Privacy Controls for Information Systems and Organizations
SA > SA-11 > SA-11(8)

SA-11(8) Developer Testing and Evaluation | Dynamic Code Analysis
Family: System and Services Acquisition (SA) > SA-11 Developer Testing and Evaluation

Require the developer of the system, system component, or system service to employ dynamic code analysis tools to identify common flaws and document the results of the analysis.
Security and Privacy Controls for Information Systems and Organizations
SA > SA-11 > SA-11(9) > Discussion

SA-11(9) Interactive Application Security Testing - Discussion
Family: System and Services Acquisition (SA) > SA-11 Developer Testing and Evaluation

Interactive (also known as instrumentation-based) application security testing is a method of detecting vulnerabilities by observing applications as they run during testing. The use of instrumentation relies on direct measurements of the actual running applications and uses access to the code, user interaction, libraries, frameworks, backend connections, and configurations to directly measure control effectiveness. When combined with analysis techniques, interactive application security testing can identify a broad range of potential vulnerabilities and confirm control effectiveness. Instrumentation-based testing works in real time and can be used continuously throughout the system development life cycle.
Security and Privacy Controls for Information Systems and Organizations
SA > SA-11 > SA-11(9)

SA-11(9) Developer Testing and Evaluation | Interactive Application Security Testing
Family: System and Services Acquisition (SA) > SA-11 Developer Testing and Evaluation

Require the developer of the system, system component, or system service to employ interactive application security testing tools to identify flaws and document the results.
Security and Privacy Controls for Information Systems and Organizations
SA > SA-15

SA-15 Development Process, Standards, and Tools
Family: System and Services Acquisition (SA)

a. Require the developer of the system, system component, or system service to follow a documented development process that:
1. Explicitly addresses security and privacy requirements;
2. Identifies the standards and tools used in the development process;
3. Documents the specific tool options and tool configurations used in the development process; and
4. Documents, manages, and ensures the integrity of changes to the process and/or tools used in development; and
b. Review the development process, standards, tools, tool options, and tool configurations [Assignment: organization-defined frequency] to determine if the process, standards, tools, tool options and tool configurations selected and employed can satisfy the following security and privacy requirements: [Assignment: organization-defined organization-defined security and privacy requirements].
Security and Privacy Controls for Information Systems and Organizations
SA > SA-15 > Discussion

SA-15 Development Process, Standards, and Tools - Discussion
Family: System and Services Acquisition (SA)

Development tools include programming languages and computer-aided design systems. Reviews of development processes include the use of maturity models to determine the potential effectiveness of such processes. Maintaining the integrity of changes to tools and processes facilitates effective supply chain risk assessment and mitigation. Such integrity requires configuration control throughout the system development life cycle to track authorized changes and prevent unauthorized changes.
Security and Privacy Controls for Information Systems and Organizations
SA > SA-15 > SA-15(1) > Discussion

SA-15(1) Quality Metrics - Discussion
Family: System and Services Acquisition (SA) > SA-15 Development Process, Standards, and Tools

Organizations use quality metrics to establish acceptable levels of system quality. Metrics can include quality gates, which are collections of completion criteria or sufficiency standards that represent the satisfactory execution of specific phases of the system development project. For example, a quality gate may require the elimination of all compiler warnings or a determination that such warnings have no impact on the effectiveness of required security or privacy capabilities. During the execution phases of development projects, quality gates provide clear, unambiguous indications of progress. Other metrics apply to the entire development project. Metrics can include defining the severity thresholds of vulnerabilities in accordance with organizational risk tolerance, such as requiring no known vulnerabilities in the delivered system with a Common Vulnerability Scoring System (CVSS) severity of medium or high.