ezesecops/rmf-ato-core huggingface dataset:
Security and Privacy Controls for Information Systems and Organizations
SC > SC-2 > SC-2(1) > Discussion

SC-2(1) Interfaces for Non-privileged Users - Discussion
Family: System and Communications Protection (SC) > SC-2 Separation of System and User Functionality

Preventing the presentation of system management functionality at interfaces to non-privileged users ensures that system administration options, including administrator privileges, are not available to the general user population. Restricting user access also prohibits the use of the grey-out option commonly used to eliminate accessibility to such information. One potential solution is to withhold system administration options until users establish sessions with administrator privileges.
Security and Privacy Controls for Information Systems and Organizations
SC > SC-2 > SC-2(1)

SC-2(1) Separation of System and User Functionality | Interfaces for Non-privileged Users
Family: System and Communications Protection (SC) > SC-2 Separation of System and User Functionality

Prevent the presentation of system management functionality at interfaces to non-privileged users.
Security and Privacy Controls for Information Systems and Organizations
SC > SC-2 > SC-2(2) > Discussion

SC-2(2) Disassociability - Discussion
Family: System and Communications Protection (SC) > SC-2 Separation of System and User Functionality

If a system is compromised, storing applications and software separately from state information about users' interactions with an application may better protect individuals' privacy.
Security and Privacy Controls for Information Systems and Organizations
SC > SC-2 > SC-2(2)

SC-2(2) Separation of System and User Functionality | Disassociability
Family: System and Communications Protection (SC) > SC-2 Separation of System and User Functionality

Store state information from applications and software separately.
Security and Privacy Controls for Information Systems and Organizations
SC > SC-3

SC-3 Security Function Isolation
Family: System and Communications Protection (SC)

Isolate security functions from nonsecurity functions.
Security and Privacy Controls for Information Systems and Organizations
SC > SC-3 > Discussion

SC-3 Security Function Isolation - Discussion
Family: System and Communications Protection (SC)

Security functions are isolated from nonsecurity functions by means of an isolation boundary implemented within a system via partitions and domains. The isolation boundary controls access to and protects the integrity of the hardware, software, and firmware that perform system security functions. Systems implement code separation in many ways, such as through the provision of security kernels via processor rings or processor modes. For non-kernel code, security function isolation is often achieved through file system protections that protect the code on disk and address space protections that protect executing code. Systems can restrict access to security functions using access control mechanisms and by implementing least privilege capabilities. While the ideal is for all code within the defined security function isolation boundary to only contain security-relevant code, it is sometimes necessary to include nonsecurity functions as an exception. The isolation of security functions from nonsecurity functions can be achieved by applying the systems security engineering design principles in [SA-8](#sa-8) , including [SA-8(1)](#sa-8.1), [SA-8(3)](#sa-8.3), [SA-8(4)](#sa-8.4), [SA-8(10)](#sa-8.10), [SA-8(12)](#sa-8.12), [SA-8(13)](#sa-8.13), [SA-8(14)](#sa-8.14) , and [SA-8(18)](#sa-8.18).
Security and Privacy Controls for Information Systems and Organizations
SC > SC-3 > SC-3(1) > Discussion

SC-3(1) Hardware Separation - Discussion
Family: System and Communications Protection (SC) > SC-3 Security Function Isolation

Hardware separation mechanisms include hardware ring architectures that are implemented within microprocessors and hardware-enforced address segmentation used to support logically distinct storage objects with separate attributes (i.e., readable, writeable).
Security and Privacy Controls for Information Systems and Organizations
SC > SC-3 > SC-3(1)

SC-3(1) Security Function Isolation | Hardware Separation
Family: System and Communications Protection (SC) > SC-3 Security Function Isolation

Employ hardware separation mechanisms to implement security function isolation.
Security and Privacy Controls for Information Systems and Organizations
SC > SC-3 > SC-3(2) > Discussion

SC-3(2) Access and Flow Control Functions - Discussion
Family: System and Communications Protection (SC) > SC-3 Security Function Isolation

Security function isolation occurs because of implementation. The functions can still be scanned and monitored. Security functions that are potentially isolated from access and flow control enforcement functions include auditing, intrusion detection, and malicious code protection functions.
Security and Privacy Controls for Information Systems and Organizations
SC > SC-3 > SC-3(2)

SC-3(2) Security Function Isolation | Access and Flow Control Functions
Family: System and Communications Protection (SC) > SC-3 Security Function Isolation

Isolate security functions enforcing access and information flow control from nonsecurity functions and from other security functions.
Security and Privacy Controls for Information Systems and Organizations
SC > SC-3 > SC-3(3) > Discussion

SC-3(3) Minimize Nonsecurity Functionality - Discussion
Family: System and Communications Protection (SC) > SC-3 Security Function Isolation

Where it is not feasible to achieve strict isolation of nonsecurity functions from security functions, it is necessary to take actions to minimize nonsecurity-relevant functions within the security function boundary. Nonsecurity functions contained within the isolation boundary are considered security-relevant because errors or malicious code in the software can directly impact the security functions of systems. The fundamental design objective is that the specific portions of systems that provide information security are of minimal size and complexity. Minimizing the number of nonsecurity functions in the security-relevant system components allows designers and implementers to focus only on those functions which are necessary to provide the desired security capability (typically access enforcement). By minimizing the nonsecurity functions within the isolation boundaries, the amount of code that is trusted to enforce security policies is significantly reduced, thus contributing to understandability.
Security and Privacy Controls for Information Systems and Organizations
SC > SC-3 > SC-3(3)

SC-3(3) Security Function Isolation | Minimize Nonsecurity Functionality
Family: System and Communications Protection (SC) > SC-3 Security Function Isolation

Minimize the number of nonsecurity functions included within the isolation boundary containing security functions.
Security and Privacy Controls for Information Systems and Organizations
SC > SC-3 > SC-3(4) > Discussion

SC-3(4) Module Coupling and Cohesiveness - Discussion
Family: System and Communications Protection (SC) > SC-3 Security Function Isolation

The reduction of inter-module interactions helps to constrain security functions and manage complexity. The concepts of coupling and cohesion are important with respect to modularity in software design. Coupling refers to the dependencies that one module has on other modules. Cohesion refers to the relationship between functions within a module. Best practices in software engineering and systems security engineering rely on layering, minimization, and modular decomposition to reduce and manage complexity. This produces software modules that are highly cohesive and loosely coupled.
Security and Privacy Controls for Information Systems and Organizations
SC > SC-3 > SC-3(4)

SC-3(4) Security Function Isolation | Module Coupling and Cohesiveness
Family: System and Communications Protection (SC) > SC-3 Security Function Isolation

Implement security functions as largely independent modules that maximize internal cohesiveness within modules and minimize coupling between modules.
Security and Privacy Controls for Information Systems and Organizations
SC > SC-3 > SC-3(5) > Discussion

SC-3(5) Layered Structures - Discussion
Family: System and Communications Protection (SC) > SC-3 Security Function Isolation

The implementation of layered structures with minimized interactions among security functions and non-looping layers (i.e., lower-layer functions do not depend on higher-layer functions) enables the isolation of security functions and the management of complexity.
Security and Privacy Controls for Information Systems and Organizations
SC > SC-3 > SC-3(5)

SC-3(5) Security Function Isolation | Layered Structures
Family: System and Communications Protection (SC) > SC-3 Security Function Isolation

Implement security functions as a layered structure minimizing interactions between layers of the design and avoiding any dependence by lower layers on the functionality or correctness of higher layers.
Security and Privacy Controls for Information Systems and Organizations
SC > SC-4

SC-4 Information in Shared System Resources
Family: System and Communications Protection (SC)

Prevent unauthorized and unintended information transfer via shared system resources.
Security and Privacy Controls for Information Systems and Organizations
SC > SC-4 > Discussion

SC-4 Information in Shared System Resources - Discussion
Family: System and Communications Protection (SC)

Preventing unauthorized and unintended information transfer via shared system resources stops information produced by the actions of prior users or roles (or the actions of processes acting on behalf of prior users or roles) from being available to current users or roles (or current processes acting on behalf of current users or roles) that obtain access to shared system resources after those resources have been released back to the system. Information in shared system resources also applies to encrypted representations of information. In other contexts, control of information in shared system resources is referred to as object reuse and residual information protection. Information in shared system resources does not address information remanence, which refers to the residual representation of data that has been nominally deleted; covert channels (including storage and timing channels), where shared system resources are manipulated to violate information flow restrictions; or components within systems for which there are only single users or roles.
Security and Privacy Controls for Information Systems and Organizations
SC > SC-4 > SC-4(2) > Discussion

SC-4(2) Multilevel or Periods Processing - Discussion
Family: System and Communications Protection (SC) > SC-4 Information in Shared System Resources

Changes in processing levels can occur during multilevel or periods processing with information at different classification levels or security categories. It can also occur during serial reuse of hardware components at different classification levels. Organization-defined procedures can include approved sanitization processes for electronically stored information.
Security and Privacy Controls for Information Systems and Organizations
SC > SC-4 > SC-4(2)

SC-4(2) Information in Shared System Resources | Multilevel or Periods Processing
Family: System and Communications Protection (SC) > SC-4 Information in Shared System Resources

Prevent unauthorized information transfer via shared resources in accordance with [Assignment: organization-defined procedures] when system processing explicitly switches between different information classification levels or security categories.
Security and Privacy Controls for Information Systems and Organizations
SC > SC-5

SC-5 Denial-of-service Protection
Family: System and Communications Protection (SC)

a. [Selection: protect against; limit] the effects of the following types of denial-of-service events: [Assignment: organization-defined types of denial-of-service events] ; and
b. Employ the following controls to achieve the denial-of-service objective: [Assignment: organization-defined controls by type of denial-of-service event].
Security and Privacy Controls for Information Systems and Organizations
SC > SC-5 > Discussion

SC-5 Denial-of-service Protection - Discussion
Family: System and Communications Protection (SC)

Denial-of-service events may occur due to a variety of internal and external causes, such as an attack by an adversary or a lack of planning to support organizational needs with respect to capacity and bandwidth. Such attacks can occur across a wide range of network protocols (e.g., IPv4, IPv6). A variety of technologies are available to limit or eliminate the origination and effects of denial-of-service events. For example, boundary protection devices can filter certain types of packets to protect system components on internal networks from being directly affected by or the source of denial-of-service attacks. Employing increased network capacity and bandwidth combined with service redundancy also reduces the susceptibility to denial-of-service events.
Security and Privacy Controls for Information Systems and Organizations
SC > SC-5 > SC-5(1) > Discussion

SC-5(1) Restrict Ability to Attack Other Systems - Discussion
Family: System and Communications Protection (SC) > SC-5 Denial-of-service Protection

Restricting the ability of individuals to launch denial-of-service attacks requires the mechanisms commonly used for such attacks to be unavailable. Individuals of concern include hostile insiders or external adversaries who have breached or compromised the system and are using it to launch a denial-of-service attack. Organizations can restrict the ability of individuals to connect and transmit arbitrary information on the transport medium (i.e., wired networks, wireless networks, spoofed Internet protocol packets). Organizations can also limit the ability of individuals to use excessive system resources. Protection against individuals having the ability to launch denial-of-service attacks may be implemented on specific systems or boundary devices that prohibit egress to potential target systems.
Security and Privacy Controls for Information Systems and Organizations
SC > SC-5 > SC-5(1)

SC-5(1) Denial-of-service Protection | Restrict Ability to Attack Other Systems
Family: System and Communications Protection (SC) > SC-5 Denial-of-service Protection

Restrict the ability of individuals to launch the following denial-of-service attacks against other systems: [Assignment: organization-defined denial-of-service attacks].
Security and Privacy Controls for Information Systems and Organizations
SC > SC-5 > SC-5(2) > Discussion

SC-5(2) Capacity, Bandwidth, and Redundancy - Discussion
Family: System and Communications Protection (SC) > SC-5 Denial-of-service Protection

Managing capacity ensures that sufficient capacity is available to counter flooding attacks. Managing capacity includes establishing selected usage priorities, quotas, partitioning, or load balancing.
Security and Privacy Controls for Information Systems and Organizations
SC > SC-5 > SC-5(2)

SC-5(2) Denial-of-service Protection | Capacity, Bandwidth, and Redundancy
Family: System and Communications Protection (SC) > SC-5 Denial-of-service Protection

Manage capacity, bandwidth, or other redundancy to limit the effects of information flooding denial-of-service attacks.
Security and Privacy Controls for Information Systems and Organizations
SC > SC-5 > SC-5(3) > Discussion

SC-5(3) Detection and Monitoring - Discussion
Family: System and Communications Protection (SC) > SC-5 Denial-of-service Protection

Organizations consider the utilization and capacity of system resources when managing risk associated with a denial of service due to malicious attacks. Denial-of-service attacks can originate from external or internal sources. System resources that are sensitive to denial of service include physical disk storage, memory, and CPU cycles. Techniques used to prevent denial-of-service attacks related to storage utilization and capacity include instituting disk quotas, configuring systems to automatically alert administrators when specific storage capacity thresholds are reached, using file compression technologies to maximize available storage space, and imposing separate partitions for system and user data.
Security and Privacy Controls for Information Systems and Organizations
SC > SC-5 > SC-5(3)

SC-5(3) Denial-of-service Protection | Detection and Monitoring
Family: System and Communications Protection (SC) > SC-5 Denial-of-service Protection

(a) Employ the following monitoring tools to detect indicators of denial-of-service attacks against, or launched from, the system: [Assignment: organization-defined monitoring tools] ; and
(b) Monitor the following system resources to determine if sufficient resources exist to prevent effective denial-of-service attacks: [Assignment: organization-defined system resources].
Security and Privacy Controls for Information Systems and Organizations
SC > SC-6

SC-6 Resource Availability
Family: System and Communications Protection (SC)

Protect the availability of resources by allocating [Assignment: organization-defined resources] by [Selection; one or more: priority; quota; [Assignment: organization-defined controls] ].
Security and Privacy Controls for Information Systems and Organizations
SC > SC-6 > Discussion

SC-6 Resource Availability - Discussion
Family: System and Communications Protection (SC)

Priority protection prevents lower-priority processes from delaying or interfering with the system that services higher-priority processes. Quotas prevent users or processes from obtaining more than predetermined amounts of resources.
Security and Privacy Controls for Information Systems and Organizations
SC > SC-7

SC-7 Boundary Protection
Family: System and Communications Protection (SC)

a. Monitor and control communications at the external managed interfaces to the system and at key internal managed interfaces within the system;
b. Implement subnetworks for publicly accessible system components that are [Selection: physically; logically] separated from internal organizational networks; and
c. Connect to external networks or systems only through managed interfaces consisting of boundary protection devices arranged in accordance with an organizational security and privacy architecture.
Security and Privacy Controls for Information Systems and Organizations
SC > SC-7 > Discussion

SC-7 Boundary Protection - Discussion
Family: System and Communications Protection (SC)

Managed interfaces include gateways, routers, firewalls, guards, network-based malicious code analysis, virtualization systems, or encrypted tunnels implemented within a security architecture. Subnetworks that are physically or logically separated from internal networks are referred to as demilitarized zones or DMZs. Restricting or prohibiting interfaces within organizational systems includes restricting external web traffic to designated web servers within managed interfaces, prohibiting external traffic that appears to be spoofing internal addresses, and prohibiting internal traffic that appears to be spoofing external addresses. [SP 800-189](#f5edfe51-d1f2-422e-9b27-5d0e90b49c72) provides additional information on source address validation techniques to prevent ingress and egress of traffic with spoofed addresses. Commercial telecommunications services are provided by network components and consolidated management systems shared by customers. These services may also include third party-provided access lines and other service elements. Such services may represent sources of increased risk despite contract security provisions. Boundary protection may be implemented as a common control for all or part of an organizational network such that the boundary to be protected is greater than a system-specific boundary (i.e., an authorization boundary).
Security and Privacy Controls for Information Systems and Organizations
SC > SC-7 > SC-7(3) > Discussion

SC-7(3) Access Points - Discussion
Family: System and Communications Protection (SC) > SC-7 Boundary Protection

Limiting the number of external network connections facilitates monitoring of inbound and outbound communications traffic. The Trusted Internet Connection [DHS TIC](#4f42ee6e-86cc-403b-a51f-76c2b4f81b54) initiative is an example of a federal guideline that requires limits on the number of external network connections. Limiting the number of external network connections to the system is important during transition periods from older to newer technologies (e.g., transitioning from IPv4 to IPv6 network protocols). Such transitions may require implementing the older and newer technologies simultaneously during the transition period and thus increase the number of access points to the system.
Security and Privacy Controls for Information Systems and Organizations
SC > SC-7 > SC-7(3)

SC-7(3) Boundary Protection | Access Points
Family: System and Communications Protection (SC) > SC-7 Boundary Protection

Limit the number of external network connections to the system.
Security and Privacy Controls for Information Systems and Organizations
SC > SC-7 > SC-7(4) > Discussion

SC-7(4) External Telecommunications Services - Discussion
Family: System and Communications Protection (SC) > SC-7 Boundary Protection

External telecommunications services can provide data and/or voice communications services. Examples of control plane traffic include Border Gateway Protocol (BGP) routing, Domain Name System (DNS), and management protocols. See [SP 800-189](#f5edfe51-d1f2-422e-9b27-5d0e90b49c72) for additional information on the use of the resource public key infrastructure (RPKI) to protect BGP routes and detect unauthorized BGP announcements.
Security and Privacy Controls for Information Systems and Organizations
SC > SC-7 > SC-7(4)

SC-7(4) Boundary Protection | External Telecommunications Services
Family: System and Communications Protection (SC) > SC-7 Boundary Protection

(a) Implement a managed interface for each external telecommunication service;
(b) Establish a traffic flow policy for each managed interface;
(c) Protect the confidentiality and integrity of the information being transmitted across each interface;
(d) Document each exception to the traffic flow policy with a supporting mission or business need and duration of that need;
(e) Review exceptions to the traffic flow policy [Assignment: organization-defined frequency] and remove exceptions that are no longer supported by an explicit mission or business need;
(f) Prevent unauthorized exchange of control plane traffic with external networks;
(g) Publish information to enable remote networks to detect unauthorized control plane traffic from internal networks; and
(h) Filter unauthorized control plane traffic from external networks.
Security and Privacy Controls for Information Systems and Organizations
SC > SC-7 > SC-7(5) > Discussion

SC-7(5) Deny by Default - Allow by Exception - Discussion
Family: System and Communications Protection (SC) > SC-7 Boundary Protection

Denying by default and allowing by exception applies to inbound and outbound network communications traffic. A deny-all, permit-by-exception network communications traffic policy ensures that only those system connections that are essential and approved are allowed. Deny by default, allow by exception also applies to a system that is connected to an external system.
Security and Privacy Controls for Information Systems and Organizations
SC > SC-7 > SC-7(5)

SC-7(5) Boundary Protection | Deny by Default - Allow by Exception
Family: System and Communications Protection (SC) > SC-7 Boundary Protection

Deny network communications traffic by default and allow network communications traffic by exception [Selection; one or more: at managed interfaces; for [Assignment: organization-defined systems] ].