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

SI-10(6) Injection Prevention - Discussion
Family: System and Information Integrity (SI) > SI-10 Information Input Validation

Untrusted data injections may be prevented using a parameterized interface or output escaping (output encoding). Parameterized interfaces separate data from code so that injections of malicious or unintended data cannot change the semantics of commands being sent. Output escaping uses specified characters to inform the interpreter's parser whether data is trusted. Prevention of untrusted data injections are with respect to the information inputs defined by the organization in the base control ( [SI-10](#si-10)).
Security and Privacy Controls for Information Systems and Organizations
SI > SI-10 > SI-10(6)

SI-10(6) Information Input Validation | Injection Prevention
Family: System and Information Integrity (SI) > SI-10 Information Input Validation

Prevent untrusted data injections.
Security and Privacy Controls for Information Systems and Organizations
SI > SI-11

SI-11 Error Handling
Family: System and Information Integrity (SI)

a. Generate error messages that provide information necessary for corrective actions without revealing information that could be exploited; and
b. Reveal error messages only to [Assignment: organization-defined personnel or roles].
Security and Privacy Controls for Information Systems and Organizations
SI > SI-11 > Discussion

SI-11 Error Handling - Discussion
Family: System and Information Integrity (SI)

Organizations consider the structure and content of error messages. The extent to which systems can handle error conditions is guided and informed by organizational policy and operational requirements. Exploitable information includes stack traces and implementation details; erroneous logon attempts with passwords mistakenly entered as the username; mission or business information that can be derived from, if not stated explicitly by, the information recorded; and personally identifiable information, such as account numbers, social security numbers, and credit card numbers. Error messages may also provide a covert channel for transmitting information.
Security and Privacy Controls for Information Systems and Organizations
SI > SI-12

SI-12 Information Management and Retention
Family: System and Information Integrity (SI)

Manage and retain information within the system and information output from the system in accordance with applicable laws, executive orders, directives, regulations, policies, standards, guidelines and operational requirements.
Security and Privacy Controls for Information Systems and Organizations
SI > SI-12 > Discussion

SI-12 Information Management and Retention - Discussion
Family: System and Information Integrity (SI)

Information management and retention requirements cover the full life cycle of information, in some cases extending beyond system disposal. Information to be retained may also include policies, procedures, plans, reports, data output from control implementation, and other types of administrative information. The National Archives and Records Administration (NARA) provides federal policy and guidance on records retention and schedules. If organizations have a records management office, consider coordinating with records management personnel. Records produced from the output of implemented controls that may require management and retention include, but are not limited to: All XX-1, [AC-6(9)](#ac-6.9), [AT-4](#at-4), [AU-12](#au-12), [CA-2](#ca-2), [CA-3](#ca-3), [CA-5](#ca-5), [CA-6](#ca-6), [CA-7](#ca-7), [CA-8](#ca-8), [CA-9](#ca-9), [CM-2](#cm-2), [CM-3](#cm-3), [CM-4](#cm-4), [CM-6](#cm-6), [CM-8](#cm-8), [CM-9](#cm-9), [CM-12](#cm-12), [CM-13](#cm-13), [CP-2](#cp-2), [IR-6](#ir-6), [IR-8](#ir-8), [MA-2](#ma-2), [MA-4](#ma-4), [PE-2](#pe-2), [PE-8](#pe-8), [PE-16](#pe-16), [PE-17](#pe-17), [PL-2](#pl-2), [PL-4](#pl-4), [PL-7](#pl-7), [PL-8](#pl-8), [PM-5](#pm-5), [PM-8](#pm-8), [PM-9](#pm-9), [PM-18](#pm-18), [PM-21](#pm-21), [PM-27](#pm-27), [PM-28](#pm-28), [PM-30](#pm-30), [PM-31](#pm-31), [PS-2](#ps-2), [PS-6](#ps-6), [PS-7](#ps-7), [PT-2](#pt-2), [PT-3](#pt-3), [PT-7](#pt-7), [RA-2](#ra-2), [RA-3](#ra-3), [RA-5](#ra-5), [RA-8](#ra-8), [SA-4](#sa-4), [SA-5](#sa-5), [SA-8](#sa-8), [SA-10](#sa-10), [SI-4](#si-4), [SR-2](#sr-2), [SR-4](#sr-4), [SR-8](#sr-8).
Security and Privacy Controls for Information Systems and Organizations
SI > SI-12 > SI-12(1) > Discussion

SI-12(1) Limit Personally Identifiable Information Elements - Discussion
Family: System and Information Integrity (SI) > SI-12 Information Management and Retention

Limiting the use of personally identifiable information throughout the information life cycle when the information is not needed for operational purposes helps to reduce the level of privacy risk created by a system. The information life cycle includes information creation, collection, use, processing, storage, maintenance, dissemination, disclosure, and disposition. Risk assessments as well as applicable laws, regulations, and policies can provide useful inputs to determining which elements of personally identifiable information may create risk.
Security and Privacy Controls for Information Systems and Organizations
SI > SI-12 > SI-12(1)

SI-12(1) Information Management and Retention | Limit Personally Identifiable Information Elements
Family: System and Information Integrity (SI) > SI-12 Information Management and Retention

Limit personally identifiable information being processed in the information life cycle to the following elements of personally identifiable information: [Assignment: organization-defined elements of personally identifiable information].
Security and Privacy Controls for Information Systems and Organizations
SI > SI-12 > SI-12(2) > Discussion

SI-12(2) Minimize Personally Identifiable Information in Testing, Training, and Research - Discussion
Family: System and Information Integrity (SI) > SI-12 Information Management and Retention

Organizations can minimize the risk to an individual's privacy by employing techniques such as de-identification or synthetic data. Limiting the use of personally identifiable information throughout the information life cycle when the information is not needed for research, testing, or training helps reduce the level of privacy risk created by a system. Risk assessments as well as applicable laws, regulations, and policies can provide useful inputs to determining the techniques to use and when to use them.
Security and Privacy Controls for Information Systems and Organizations
SI > SI-12 > SI-12(2)

SI-12(2) Information Management and Retention | Minimize Personally Identifiable Information in Testing, Training, and Research
Family: System and Information Integrity (SI) > SI-12 Information Management and Retention

Use the following techniques to minimize the use of personally identifiable information for research, testing, or training: [Assignment: organization-defined organization-defined techniques].
Security and Privacy Controls for Information Systems and Organizations
SI > SI-12 > SI-12(3) > Discussion

SI-12(3) Information Disposal - Discussion
Family: System and Information Integrity (SI) > SI-12 Information Management and Retention

Organizations can minimize both security and privacy risks by disposing of information when it is no longer needed. The disposal or destruction of information applies to originals as well as copies and archived records, including system logs that may contain personally identifiable information.
Security and Privacy Controls for Information Systems and Organizations
SI > SI-12 > SI-12(3)

SI-12(3) Information Management and Retention | Information Disposal
Family: System and Information Integrity (SI) > SI-12 Information Management and Retention

Use the following techniques to dispose of, destroy, or erase information following the retention period: [Assignment: organization-defined organization-defined techniques].
Security and Privacy Controls for Information Systems and Organizations
SI > SI-13

SI-13 Predictable Failure Prevention
Family: System and Information Integrity (SI)

a. Determine mean time to failure (MTTF) for the following system components in specific environments of operation: [Assignment: organization-defined system components] ; and
b. Provide substitute system components and a means to exchange active and standby components in accordance with the following criteria: [Assignment: organization-defined mean time to failure (MTTF) substitution criteria].
Security and Privacy Controls for Information Systems and Organizations
SI > SI-13 > Discussion

SI-13 Predictable Failure Prevention - Discussion
Family: System and Information Integrity (SI)

While MTTF is primarily a reliability issue, predictable failure prevention is intended to address potential failures of system components that provide security capabilities. Failure rates reflect installation-specific consideration rather than the industry-average. Organizations define the criteria for the substitution of system components based on the MTTF value with consideration for the potential harm from component failures. The transfer of responsibilities between active and standby components does not compromise safety, operational readiness, or security capabilities. The preservation of system state variables is also critical to help ensure a successful transfer process. Standby components remain available at all times except for maintenance issues or recovery failures in progress.
Security and Privacy Controls for Information Systems and Organizations
SI > SI-13 > SI-13(1) > Discussion

SI-13(1) Transferring Component Responsibilities - Discussion
Family: System and Information Integrity (SI) > SI-13 Predictable Failure Prevention

Transferring primary system component responsibilities to other substitute components prior to primary component failure is important to reduce the risk of degraded or debilitated mission or business functions. Making such transfers based on a percentage of mean time to failure allows organizations to be proactive based on their risk tolerance. However, the premature replacement of system components can result in the increased cost of system operations.
Security and Privacy Controls for Information Systems and Organizations
SI > SI-13 > SI-13(1)

SI-13(1) Predictable Failure Prevention | Transferring Component Responsibilities
Family: System and Information Integrity (SI) > SI-13 Predictable Failure Prevention

Take system components out of service by transferring component responsibilities to substitute components no later than [Assignment: organization-defined fraction or percentage] of mean time to failure.
Security and Privacy Controls for Information Systems and Organizations
SI > SI-13 > SI-13(3) > Discussion

SI-13(3) Manual Transfer Between Components - Discussion
Family: System and Information Integrity (SI) > SI-13 Predictable Failure Prevention

For example, if the MTTF for a system component is 100 days and the MTTF percentage defined by the organization is 90 percent, the manual transfer would occur after 90 days.
Security and Privacy Controls for Information Systems and Organizations
SI > SI-13 > SI-13(3)

SI-13(3) Predictable Failure Prevention | Manual Transfer Between Components
Family: System and Information Integrity (SI) > SI-13 Predictable Failure Prevention

Manually initiate transfers between active and standby system components when the use of the active component reaches [Assignment: organization-defined percentage] of the mean time to failure.
Security and Privacy Controls for Information Systems and Organizations
SI > SI-13 > SI-13(4) > Discussion

SI-13(4) Standby Component Installation and Notification - Discussion
Family: System and Information Integrity (SI) > SI-13 Predictable Failure Prevention

Automatic or manual transfer of components from standby to active mode can occur upon the detection of component failures.
Security and Privacy Controls for Information Systems and Organizations
SI > SI-13 > SI-13(4)

SI-13(4) Predictable Failure Prevention | Standby Component Installation and Notification
Family: System and Information Integrity (SI) > SI-13 Predictable Failure Prevention

If system component failures are detected:
(a) Ensure that the standby components are successfully and transparently installed within [Assignment: organization-defined time period] ; and
(b) [Selection; one or more: activate [Assignment: organization-defined alarm] ; automatically shut down the system; [Assignment: organization-defined action] ].
Security and Privacy Controls for Information Systems and Organizations
SI > SI-13 > SI-13(5) > Discussion

SI-13(5) Failover Capability - Discussion
Family: System and Information Integrity (SI) > SI-13 Predictable Failure Prevention

Failover refers to the automatic switchover to an alternate system upon the failure of the primary system. Failover capability includes incorporating mirrored system operations at alternate processing sites or periodic data mirroring at regular intervals defined by the recovery time periods of organizations.
Security and Privacy Controls for Information Systems and Organizations
SI > SI-13 > SI-13(5)

SI-13(5) Predictable Failure Prevention | Failover Capability
Family: System and Information Integrity (SI) > SI-13 Predictable Failure Prevention

Provide [Selection: real-time; near real-time] [Assignment: organization-defined failover capability] for the system.
Security and Privacy Controls for Information Systems and Organizations
SI > SI-14

SI-14 Non-persistence
Family: System and Information Integrity (SI)

Implement non-persistent [Assignment: organization-defined system components and services] that are initiated in a known state and terminated [Selection; one or more: upon end of session of use; [Assignment: organization-defined frequency] ].
Security and Privacy Controls for Information Systems and Organizations
SI > SI-14 > Discussion

SI-14 Non-persistence - Discussion
Family: System and Information Integrity (SI)

Implementation of non-persistent components and services mitigates risk from advanced persistent threats (APTs) by reducing the targeting capability of adversaries (i.e., window of opportunity and available attack surface) to initiate and complete attacks. By implementing the concept of non-persistence for selected system components, organizations can provide a trusted, known state computing resource for a specific time period that does not give adversaries sufficient time to exploit vulnerabilities in organizational systems or operating environments. Since the APT is a high-end, sophisticated threat with regard to capability, intent, and targeting, organizations assume that over an extended period, a percentage of attacks will be successful. Non-persistent system components and services are activated as required using protected information and terminated periodically or at the end of sessions. Non-persistence increases the work factor of adversaries attempting to compromise or breach organizational systems.

Non-persistence can be achieved by refreshing system components, periodically reimaging components, or using a variety of common virtualization techniques. Non-persistent services can be implemented by using virtualization techniques as part of virtual machines or as new instances of processes on physical machines (either persistent or non-persistent). The benefit of periodic refreshes of system components and services is that it does not require organizations to first determine whether compromises of components or services have occurred (something that may often be difficult to determine). The refresh of selected system components and services occurs with sufficient frequency to prevent the spread or intended impact of attacks, but not with such frequency that it makes the system unstable. Refreshes of critical components and services may be done periodically to hinder the ability of adversaries to exploit optimum windows of vulnerabilities.
Security and Privacy Controls for Information Systems and Organizations
SI > SI-14 > SI-14(1) > Discussion

SI-14(1) Refresh from Trusted Sources - Discussion
Family: System and Information Integrity (SI) > SI-14 Non-persistence

Trusted sources include software and data from write-once, read-only media or from selected offline secure storage facilities.
Security and Privacy Controls for Information Systems and Organizations
SI > SI-14 > SI-14(1)

SI-14(1) Non-persistence | Refresh from Trusted Sources
Family: System and Information Integrity (SI) > SI-14 Non-persistence

Obtain software and data employed during system component and service refreshes from the following trusted sources: [Assignment: organization-defined trusted sources].
Security and Privacy Controls for Information Systems and Organizations
SI > SI-14 > SI-14(2) > Discussion

SI-14(2) Non-persistent Information - Discussion
Family: System and Information Integrity (SI) > SI-14 Non-persistence

Retaining information longer than is needed makes the information a potential target for advanced adversaries searching for high value assets to compromise through unauthorized disclosure, unauthorized modification, or exfiltration. For system-related information, unnecessary retention provides advanced adversaries information that can assist in their reconnaissance and lateral movement through the system.
Security and Privacy Controls for Information Systems and Organizations
SI > SI-14 > SI-14(2)

SI-14(2) Non-persistence | Non-persistent Information
Family: System and Information Integrity (SI) > SI-14 Non-persistence

(a) [Selection: refresh [Assignment: organization-defined information] [Assignment: organization-defined frequency] ; generate [Assignment: organization-defined information] on demand] ; and
(b) Delete information when no longer needed.
Security and Privacy Controls for Information Systems and Organizations
SI > SI-14 > SI-14(3) > Discussion

SI-14(3) Non-persistent Connectivity - Discussion
Family: System and Information Integrity (SI) > SI-14 Non-persistence

Persistent connections to systems can provide advanced adversaries with paths to move laterally through systems and potentially position themselves closer to high value assets. Limiting the availability of such connections impedes the adversary's ability to move freely through organizational systems.
Security and Privacy Controls for Information Systems and Organizations
SI > SI-14 > SI-14(3)

SI-14(3) Non-persistence | Non-persistent Connectivity
Family: System and Information Integrity (SI) > SI-14 Non-persistence

Establish connections to the system on demand and terminate connections after [Selection: completion of a request; a period of non-use].
Security and Privacy Controls for Information Systems and Organizations
SI > SI-15

SI-15 Information Output Filtering
Family: System and Information Integrity (SI)

Validate information output from the following software programs and/or applications to ensure that the information is consistent with the expected content: [Assignment: organization-defined software programs and/or applications].
Security and Privacy Controls for Information Systems and Organizations
SI > SI-15 > Discussion

SI-15 Information Output Filtering - Discussion
Family: System and Information Integrity (SI)

Certain types of attacks, including SQL injections, produce output results that are unexpected or inconsistent with the output results that would be expected from software programs or applications. Information output filtering focuses on detecting extraneous content, preventing such extraneous content from being displayed, and then alerting monitoring tools that anomalous behavior has been discovered.
Security and Privacy Controls for Information Systems and Organizations
SI > SI-16

SI-16 Memory Protection
Family: System and Information Integrity (SI)

Implement the following controls to protect the system memory from unauthorized code execution: [Assignment: organization-defined controls].
Security and Privacy Controls for Information Systems and Organizations
SI > SI-16 > Discussion

SI-16 Memory Protection - Discussion
Family: System and Information Integrity (SI)

Some adversaries launch attacks with the intent of executing code in non-executable regions of memory or in memory locations that are prohibited. Controls employed to protect memory include data execution prevention and address space layout randomization. Data execution prevention controls can either be hardware-enforced or software-enforced with hardware enforcement providing the greater strength of mechanism.
Security and Privacy Controls for Information Systems and Organizations
SI > SI-17

SI-17 Fail-safe Procedures
Family: System and Information Integrity (SI)

Implement the indicated fail-safe procedures when the indicated failures occur: [Assignment: organization-defined organization-defined list of failure conditions and associated fail-safe procedures].
Security and Privacy Controls for Information Systems and Organizations
SI > SI-17 > Discussion

SI-17 Fail-safe Procedures - Discussion
Family: System and Information Integrity (SI)

Failure conditions include the loss of communications among critical system components or between system components and operational facilities. Fail-safe procedures include alerting operator personnel and providing specific instructions on subsequent steps to take. Subsequent steps may include doing nothing, reestablishing system settings, shutting down processes, restarting the system, or contacting designated organizational personnel.
Security and Privacy Controls for Information Systems and Organizations
SI > SI-18

SI-18 Personally Identifiable Information Quality Operations
Family: System and Information Integrity (SI)

a. Check the accuracy, relevance, timeliness, and completeness of personally identifiable information across the information life cycle [Assignment: organization-defined organization-defined frequency] ; and
b. Correct or delete inaccurate or outdated personally identifiable information.
Security and Privacy Controls for Information Systems and Organizations
SI > SI-18 > Discussion

SI-18 Personally Identifiable Information Quality Operations - Discussion
Family: System and Information Integrity (SI)

Personally identifiable information quality operations include the steps that organizations take to confirm the accuracy and relevance of personally identifiable information throughout the information life cycle. The information life cycle includes the creation, collection, use, processing, storage, maintenance, dissemination, disclosure, and disposal of personally identifiable information. Personally identifiable information quality operations include editing and validating addresses as they are collected or entered into systems using automated address verification look-up application programming interfaces. Checking personally identifiable information quality includes the tracking of updates or changes to data over time, which enables organizations to know how and what personally identifiable information was changed should erroneous information be identified. The measures taken to protect personally identifiable information quality are based on the nature and context of the personally identifiable information, how it is to be used, how it was obtained, and the potential de-identification methods employed. The measures taken to validate the accuracy of personally identifiable information used to make determinations about the rights, benefits, or privileges of individuals covered under federal programs may be more comprehensive than the measures used to validate personally identifiable information used for less sensitive purposes.