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

AC-4(21) Physical or Logical Separation of Information Flows - Discussion
Family: Access Control (AC) > AC-4 Information Flow Enforcement

Enforcing the separation of information flows associated with defined types of data can enhance protection by ensuring that information is not commingled while in transit and by enabling flow control by transmission paths that are not otherwise achievable. Types of separable information include inbound and outbound communications traffic, service requests and responses, and information of differing security impact or classification levels.
Security and Privacy Controls for Information Systems and Organizations
AC > AC-4 > AC-4(21)

AC-4(21) Information Flow Enforcement | Physical or Logical Separation of Information Flows
Family: Access Control (AC) > AC-4 Information Flow Enforcement

Separate information flows logically or physically using [Assignment: organization-defined organization-defined mechanisms and/or techniques] to accomplish [Assignment: organization-defined required separations].
Security and Privacy Controls for Information Systems and Organizations
AC > AC-4 > AC-4(22) > Discussion

AC-4(22) Access Only - Discussion
Family: Access Control (AC) > AC-4 Information Flow Enforcement

The system provides a capability for users to access each connected security domain without providing any mechanisms to allow users to transfer data or information between the different security domains. An example of an access-only solution is a terminal that provides a user access to information with different security classifications while assuredly keeping the information separate.
Security and Privacy Controls for Information Systems and Organizations
AC > AC-4 > AC-4(22)

AC-4(22) Information Flow Enforcement | Access Only
Family: Access Control (AC) > AC-4 Information Flow Enforcement

Provide access from a single device to computing platforms, applications, or data residing in multiple different security domains, while preventing information flow between the different security domains.
Security and Privacy Controls for Information Systems and Organizations
AC > AC-4 > AC-4(23) > Discussion

AC-4(23) Modify Non-releasable Information - Discussion
Family: Access Control (AC) > AC-4 Information Flow Enforcement

Modifying non-releasable information can help prevent a data spill or attack when information is transferred across security domains. Modification actions include masking, permutation, alteration, removal, or redaction.
Security and Privacy Controls for Information Systems and Organizations
AC > AC-4 > AC-4(23)

AC-4(23) Information Flow Enforcement | Modify Non-releasable Information
Family: Access Control (AC) > AC-4 Information Flow Enforcement

When transferring information between different security domains, modify non-releasable information by implementing [Assignment: organization-defined modification action].
Security and Privacy Controls for Information Systems and Organizations
AC > AC-4 > AC-4(24) > Discussion

AC-4(24) Internal Normalized Format - Discussion
Family: Access Control (AC) > AC-4 Information Flow Enforcement

Converting data into normalized forms is one of most of effective mechanisms to stop malicious attacks and large classes of data exfiltration.
Security and Privacy Controls for Information Systems and Organizations
AC > AC-4 > AC-4(24)

AC-4(24) Information Flow Enforcement | Internal Normalized Format
Family: Access Control (AC) > AC-4 Information Flow Enforcement

When transferring information between different security domains, parse incoming data into an internal normalized format and regenerate the data to be consistent with its intended specification.
Security and Privacy Controls for Information Systems and Organizations
AC > AC-4 > AC-4(25) > Discussion

AC-4(25) Data Sanitization - Discussion
Family: Access Control (AC) > AC-4 Information Flow Enforcement

Data sanitization is the process of irreversibly removing or destroying data stored on a memory device (e.g., hard drives, flash memory/solid state drives, mobile devices, CDs, and DVDs) or in hard copy form.
Security and Privacy Controls for Information Systems and Organizations
AC > AC-4 > AC-4(25)

AC-4(25) Information Flow Enforcement | Data Sanitization
Family: Access Control (AC) > AC-4 Information Flow Enforcement

When transferring information between different security domains, sanitize data to minimize [Selection; one or more: delivery of malicious content, command and control of malicious code, malicious code augmentation, and steganography-encoded data; spillage of sensitive information] in accordance with [Assignment: organization-defined policy].
Security and Privacy Controls for Information Systems and Organizations
AC > AC-4 > AC-4(26) > Discussion

AC-4(26) Audit Filtering Actions - Discussion
Family: Access Control (AC) > AC-4 Information Flow Enforcement

Content filtering is the process of inspecting information as it traverses a cross-domain solution and determines if the information meets a predefined policy. Content filtering actions and the results of filtering actions are recorded for individual messages to ensure that the correct filter actions were applied. Content filter reports are used to assist in troubleshooting actions by, for example, determining why message content was modified and/or why it failed the filtering process. Audit events are defined in [AU-2](#au-2) . Audit records are generated in [AU-12](#au-12).
Security and Privacy Controls for Information Systems and Organizations
AC > AC-4 > AC-4(26)

AC-4(26) Information Flow Enforcement | Audit Filtering Actions
Family: Access Control (AC) > AC-4 Information Flow Enforcement

When transferring information between different security domains, record and audit content filtering actions and results for the information being filtered.
Security and Privacy Controls for Information Systems and Organizations
AC > AC-4 > AC-4(27) > Discussion

AC-4(27) Redundant/Independent Filtering Mechanisms - Discussion
Family: Access Control (AC) > AC-4 Information Flow Enforcement

Content filtering is the process of inspecting information as it traverses a cross-domain solution and determines if the information meets a predefined policy. Redundant and independent content filtering eliminates a single point of failure filtering system. Independence is defined as the implementation of a content filter that uses a different code base and supporting libraries (e.g., two JPEG filters using different vendors' JPEG libraries) and multiple, independent system processes.
Security and Privacy Controls for Information Systems and Organizations
AC > AC-4 > AC-4(27)

AC-4(27) Information Flow Enforcement | Redundant/Independent Filtering Mechanisms
Family: Access Control (AC) > AC-4 Information Flow Enforcement

When transferring information between different security domains, implement content filtering solutions that provide redundant and independent filtering mechanisms for each data type.
Security and Privacy Controls for Information Systems and Organizations
AC > AC-4 > AC-4(28) > Discussion

AC-4(28) Linear Filter Pipelines - Discussion
Family: Access Control (AC) > AC-4 Information Flow Enforcement

Content filtering is the process of inspecting information as it traverses a cross-domain solution and determines if the information meets a predefined policy. The use of linear content filter pipelines ensures that filter processes are non-bypassable and always invoked. In general, the use of parallel filtering architectures for content filtering of a single data type introduces bypass and non-invocation issues.
Security and Privacy Controls for Information Systems and Organizations
AC > AC-4 > AC-4(28)

AC-4(28) Information Flow Enforcement | Linear Filter Pipelines
Family: Access Control (AC) > AC-4 Information Flow Enforcement

When transferring information between different security domains, implement a linear content filter pipeline that is enforced with discretionary and mandatory access controls.
Security and Privacy Controls for Information Systems and Organizations
AC > AC-4 > AC-4(29) > Discussion

AC-4(29) Filter Orchestration Engines - Discussion
Family: Access Control (AC) > AC-4 Information Flow Enforcement

Content filtering is the process of inspecting information as it traverses a cross-domain solution and determines if the information meets a predefined security policy. An orchestration engine coordinates the sequencing of activities (manual and automated) in a content filtering process. Errors are defined as either anomalous actions or unexpected termination of the content filter process. This is not the same as a filter failing content due to non-compliance with policy. Content filter reports are a commonly used mechanism to ensure that expected filtering actions are completed successfully.
Security and Privacy Controls for Information Systems and Organizations
AC > AC-4 > AC-4(29)

AC-4(29) Information Flow Enforcement | Filter Orchestration Engines
Family: Access Control (AC) > AC-4 Information Flow Enforcement

When transferring information between different security domains, employ content filter orchestration engines to ensure that:
(a) Content filtering mechanisms successfully complete execution without errors; and
(b) Content filtering actions occur in the correct order and comply with [Assignment: organization-defined policy].
Security and Privacy Controls for Information Systems and Organizations
AC > AC-4 > AC-4(30) > Discussion

AC-4(30) Filter Mechanisms Using Multiple Processes - Discussion
Family: Access Control (AC) > AC-4 Information Flow Enforcement

The use of multiple processes to implement content filtering mechanisms reduces the likelihood of a single point of failure.
Security and Privacy Controls for Information Systems and Organizations
AC > AC-4 > AC-4(30)

AC-4(30) Information Flow Enforcement | Filter Mechanisms Using Multiple Processes
Family: Access Control (AC) > AC-4 Information Flow Enforcement

When transferring information between different security domains, implement content filtering mechanisms using multiple processes.
Security and Privacy Controls for Information Systems and Organizations
AC > AC-4 > AC-4(31) > Discussion

AC-4(31) Failed Content Transfer Prevention - Discussion
Family: Access Control (AC) > AC-4 Information Flow Enforcement

Content that failed filtering checks can corrupt the system if transferred to the receiving domain.
Security and Privacy Controls for Information Systems and Organizations
AC > AC-4 > AC-4(31)

AC-4(31) Information Flow Enforcement | Failed Content Transfer Prevention
Family: Access Control (AC) > AC-4 Information Flow Enforcement

When transferring information between different security domains, prevent the transfer of failed content to the receiving domain.
Security and Privacy Controls for Information Systems and Organizations
AC > AC-4 > AC-4(32) > Discussion

AC-4(32) Process Requirements for Information Transfer - Discussion
Family: Access Control (AC) > AC-4 Information Flow Enforcement

The processes transferring information between filter pipelines have minimum complexity and functionality to provide assurance that the processes operate correctly.
Security and Privacy Controls for Information Systems and Organizations
AC > AC-4 > AC-4(32)

AC-4(32) Information Flow Enforcement | Process Requirements for Information Transfer
Family: Access Control (AC) > AC-4 Information Flow Enforcement

When transferring information between different security domains, the process that transfers information between filter pipelines:
(a) Does not filter message content;
(b) Validates filtering metadata;
(c) Ensures the content associated with the filtering metadata has successfully completed filtering; and
(d) Transfers the content to the destination filter pipeline.
Security and Privacy Controls for Information Systems and Organizations
AC > AC-5

AC-5 Separation of Duties
Family: Access Control (AC)

a. Identify and document [Assignment: organization-defined duties of individuals] ; and
b. Define system access authorizations to support separation of duties.
Security and Privacy Controls for Information Systems and Organizations
AC > AC-5 > Discussion

AC-5 Separation of Duties - Discussion
Family: Access Control (AC)

Separation of duties addresses the potential for abuse of authorized privileges and helps to reduce the risk of malevolent activity without collusion. Separation of duties includes dividing mission or business functions and support functions among different individuals or roles, conducting system support functions with different individuals, and ensuring that security personnel who administer access control functions do not also administer audit functions. Because separation of duty violations can span systems and application domains, organizations consider the entirety of systems and system components when developing policy on separation of duties. Separation of duties is enforced through the account management activities in [AC-2](#ac-2) , access control mechanisms in [AC-3](#ac-3) , and identity management activities in [IA-2](#ia-2), [IA-4](#ia-4) , and [IA-12](#ia-12).
Security and Privacy Controls for Information Systems and Organizations
AC > AC-6

AC-6 Least Privilege
Family: Access Control (AC)

Employ the principle of least privilege, allowing only authorized accesses for users (or processes acting on behalf of users) that are necessary to accomplish assigned organizational tasks.
Security and Privacy Controls for Information Systems and Organizations
AC > AC-6 > Discussion

AC-6 Least Privilege - Discussion
Family: Access Control (AC)

Organizations employ least privilege for specific duties and systems. The principle of least privilege is also applied to system processes, ensuring that the processes have access to systems and operate at privilege levels no higher than necessary to accomplish organizational missions or business functions. Organizations consider the creation of additional processes, roles, and accounts as necessary to achieve least privilege. Organizations apply least privilege to the development, implementation, and operation of organizational systems.
Security and Privacy Controls for Information Systems and Organizations
AC > AC-6 > AC-6(1) > Discussion

AC-6(1) Authorize Access to Security Functions - Discussion
Family: Access Control (AC) > AC-6 Least Privilege

Security functions include establishing system accounts, configuring access authorizations (i.e., permissions, privileges), configuring settings for events to be audited, and establishing intrusion detection parameters. Security-relevant information includes filtering rules for routers or firewalls, configuration parameters for security services, cryptographic key management information, and access control lists. Authorized personnel include security administrators, system administrators, system security officers, system programmers, and other privileged users.
Security and Privacy Controls for Information Systems and Organizations
AC > AC-6 > AC-6(1)

AC-6(1) Least Privilege | Authorize Access to Security Functions
Family: Access Control (AC) > AC-6 Least Privilege

Authorize access for [Assignment: organization-defined individuals and roles] to:
(a) [Assignment: organization-defined organization-defined security functions (deployed in hardware, software, and firmware)] ; and
(b) [Assignment: organization-defined security-relevant information].
Security and Privacy Controls for Information Systems and Organizations
AC > AC-6 > AC-6(2) > Discussion

AC-6(2) Non-privileged Access for Nonsecurity Functions - Discussion
Family: Access Control (AC) > AC-6 Least Privilege

Requiring the use of non-privileged accounts when accessing nonsecurity functions limits exposure when operating from within privileged accounts or roles. The inclusion of roles addresses situations where organizations implement access control policies, such as role-based access control, and where a change of role provides the same degree of assurance in the change of access authorizations for the user and the processes acting on behalf of the user as would be provided by a change between a privileged and non-privileged account.
Security and Privacy Controls for Information Systems and Organizations
AC > AC-6 > AC-6(2)

AC-6(2) Least Privilege | Non-privileged Access for Nonsecurity Functions
Family: Access Control (AC) > AC-6 Least Privilege

Require that users of system accounts (or roles) with access to [Assignment: organization-defined security functions or security-relevant information] use non-privileged accounts or roles, when accessing nonsecurity functions.
Security and Privacy Controls for Information Systems and Organizations
AC > AC-6 > AC-6(3) > Discussion

AC-6(3) Network Access to Privileged Commands - Discussion
Family: Access Control (AC) > AC-6 Least Privilege

Network access is any access across a network connection in lieu of local access (i.e., user being physically present at the device).
Security and Privacy Controls for Information Systems and Organizations
AC > AC-6 > AC-6(3)

AC-6(3) Least Privilege | Network Access to Privileged Commands
Family: Access Control (AC) > AC-6 Least Privilege

Authorize network access to [Assignment: organization-defined privileged commands] only for [Assignment: organization-defined compelling operational needs] and document the rationale for such access in the security plan for the system.
Security and Privacy Controls for Information Systems and Organizations
AC > AC-6 > AC-6(4) > Discussion

AC-6(4) Separate Processing Domains - Discussion
Family: Access Control (AC) > AC-6 Least Privilege

Providing separate processing domains for finer-grained allocation of user privileges includes using virtualization techniques to permit additional user privileges within a virtual machine while restricting privileges to other virtual machines or to the underlying physical machine, implementing separate physical domains, and employing hardware or software domain separation mechanisms.
Security and Privacy Controls for Information Systems and Organizations
AC > AC-6 > AC-6(4)

AC-6(4) Least Privilege | Separate Processing Domains
Family: Access Control (AC) > AC-6 Least Privilege

Provide separate processing domains to enable finer-grained allocation of user privileges.
Security and Privacy Controls for Information Systems and Organizations
AC > AC-6 > AC-6(5) > Discussion

AC-6(5) Privileged Accounts - Discussion
Family: Access Control (AC) > AC-6 Least Privilege

Privileged accounts, including super user accounts, are typically described as system administrator for various types of commercial off-the-shelf operating systems. Restricting privileged accounts to specific personnel or roles prevents day-to-day users from accessing privileged information or privileged functions. Organizations may differentiate in the application of restricting privileged accounts between allowed privileges for local accounts and for domain accounts provided that they retain the ability to control system configurations for key parameters and as otherwise necessary to sufficiently mitigate risk.
Security and Privacy Controls for Information Systems and Organizations
AC > AC-6 > AC-6(5)

AC-6(5) Least Privilege | Privileged Accounts
Family: Access Control (AC) > AC-6 Least Privilege

Restrict privileged accounts on the system to [Assignment: organization-defined personnel or roles].
Security and Privacy Controls for Information Systems and Organizations
AC > AC-6 > AC-6(6) > Discussion

AC-6(6) Privileged Access by Non-organizational Users - Discussion
Family: Access Control (AC) > AC-6 Least Privilege

An organizational user is an employee or an individual considered by the organization to have the equivalent status of an employee. Organizational users include contractors, guest researchers, or individuals detailed from other organizations. A non-organizational user is a user who is not an organizational user. Policies and procedures for granting equivalent status of employees to individuals include a need-to-know, citizenship, and the relationship to the organization.
Security and Privacy Controls for Information Systems and Organizations
AC > AC-6 > AC-6(6)

AC-6(6) Least Privilege | Privileged Access by Non-organizational Users
Family: Access Control (AC) > AC-6 Least Privilege

Prohibit privileged access to the system by non-organizational users.
Security and Privacy Controls for Information Systems and Organizations
AC > AC-6 > AC-6(7) > Discussion

AC-6(7) Review of User Privileges - Discussion
Family: Access Control (AC) > AC-6 Least Privilege

The need for certain assigned user privileges may change over time to reflect changes in organizational mission and business functions, environments of operation, technologies, or threats. A periodic review of assigned user privileges is necessary to determine if the rationale for assigning such privileges remains valid. If the need cannot be revalidated, organizations take appropriate corrective actions.
Security and Privacy Controls for Information Systems and Organizations
AC > AC-6 > AC-6(7)

AC-6(7) Least Privilege | Review of User Privileges
Family: Access Control (AC) > AC-6 Least Privilege

(a) Review [Assignment: organization-defined frequency] the privileges assigned to [Assignment: organization-defined roles and classes] to validate the need for such privileges; and
(b) Reassign or remove privileges, if necessary, to correctly reflect organizational mission and business needs.
Security and Privacy Controls for Information Systems and Organizations
AC > AC-6 > AC-6(8) > Discussion

AC-6(8) Privilege Levels for Code Execution - Discussion
Family: Access Control (AC) > AC-6 Least Privilege

In certain situations, software applications or programs need to execute with elevated privileges to perform required functions. However, depending on the software functionality and configuration, if the privileges required for execution are at a higher level than the privileges assigned to organizational users invoking such applications or programs, those users may indirectly be provided with greater privileges than assigned.
Security and Privacy Controls for Information Systems and Organizations
AC > AC-6 > AC-6(8)

AC-6(8) Least Privilege | Privilege Levels for Code Execution
Family: Access Control (AC) > AC-6 Least Privilege

Prevent the following software from executing at higher privilege levels than users executing the software: [Assignment: organization-defined software].
Security and Privacy Controls for Information Systems and Organizations
AC > AC-6 > AC-6(9) > Discussion

AC-6(9) Log Use of Privileged Functions - Discussion
Family: Access Control (AC) > AC-6 Least Privilege

The misuse of privileged functions, either intentionally or unintentionally by authorized users or by unauthorized external entities that have compromised system accounts, is a serious and ongoing concern and can have significant adverse impacts on organizations. Logging and analyzing the use of privileged functions is one way to detect such misuse and, in doing so, help mitigate the risk from insider threats and the advanced persistent threat.
Security and Privacy Controls for Information Systems and Organizations
AC > AC-6 > AC-6(9)

AC-6(9) Least Privilege | Log Use of Privileged Functions
Family: Access Control (AC) > AC-6 Least Privilege

Log the execution of privileged functions.
Security and Privacy Controls for Information Systems and Organizations
AC > AC-6 > AC-6(10) > Discussion

AC-6(10) Prohibit Non-privileged Users from Executing Privileged Functions - Discussion
Family: Access Control (AC) > AC-6 Least Privilege

Privileged functions include disabling, circumventing, or altering implemented security or privacy controls, establishing system accounts, performing system integrity checks, and administering cryptographic key management activities. Non-privileged users are individuals who do not possess appropriate authorizations. Privileged functions that require protection from non-privileged users include circumventing intrusion detection and prevention mechanisms or malicious code protection mechanisms. Preventing non-privileged users from executing privileged functions is enforced by [AC-3](#ac-3).