Boundary Protection

✓ LOW ✓ MODERATE ✓ HIGH
26 Enhancements 1 Overlay 25 Related Controls
Graph
Export ▾

Requirements NIST SOURCE

Discussion (NIST Supplemental Guidance)

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 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).

Enhancements NIST SOURCE

SC-7(1) Physically Separated Subnetworks WITHDRAWN

Withdrawn. Incorporated into SC-7.

SC-7(2) Public Access WITHDRAWN

Withdrawn. Incorporated into SC-7.

SC-7(3) Access Points LOW ✓ MODERATE ✓ HIGH

Limit the number of external network connections to the system.

Discussion

Limiting the number of external network connections facilitates monitoring of inbound and outbound communications traffic. The Trusted Internet Connection DHS TIC 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.

Open full page for SC-7(3) →
SC-7(4) External Telecommunications Services LOW ✓ MODERATE ✓ HIGH
  1. (a) Implement a managed interface for each external telecommunication service;
  2. (b) Establish a traffic flow policy for each managed interface;
  3. (c) Protect the confidentiality and integrity of the information being transmitted across each interface;
  4. (d) Document each exception to the traffic flow policy with a supporting mission or business need and duration of that need;
  5. (e) Review exceptions to the traffic flow policy [frequency] and remove exceptions that are no longer supported by an explicit mission or business need;
  6. (f) Prevent unauthorized exchange of control plane traffic with external networks;
  7. (g) Publish information to enable remote networks to detect unauthorized control plane traffic from internal networks; and
  8. (h) Filter unauthorized control plane traffic from external networks.
Discussion

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 for additional information on the use of the resource public key infrastructure (RPKI) to protect BGP routes and detect unauthorized BGP announcements.

Open full page for SC-7(4) →
SC-7(5) Deny by Default — Allow by Exception LOW ✓ MODERATE ✓ HIGH

Deny network communications traffic by default and allow network communications traffic by exception [one of: at managed interfaces; for].

Discussion

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.

Open full page for SC-7(5) →
SC-7(6) Response to Recognized Failures WITHDRAWN

Withdrawn. Incorporated into SC-7(18).

SC-7(7) Split Tunneling for Remote Devices LOW ✓ MODERATE ✓ HIGH

Prevent split tunneling for remote devices connecting to organizational systems unless the split tunnel is securely provisioned using [safeguards].

Discussion

Split tunneling is the process of allowing a remote user or device to establish a non-remote connection with a system and simultaneously communicate via some other connection to a resource in an external network. This method of network access enables a user to access remote devices and simultaneously, access uncontrolled networks. Split tunneling might be desirable by remote users to communicate with local system resources, such as printers or file servers. However, split tunneling can facilitate unauthorized external connections, making the system vulnerable to attack and to exfiltration of organizational information. Split tunneling can be prevented by disabling configuration settings that allow such capability in remote devices and by preventing those configuration settings from being configurable by users. Prevention can also be achieved by the detection of split tunneling (or of configuration settings that allow split tunneling) in the remote device, and by prohibiting the connection if the remote device is using split tunneling. A virtual private network (VPN) can be used to securely provision a split tunnel. A securely provisioned VPN includes locking connectivity to exclusive, managed, and named environments, or to a specific set of pre-approved addresses, without user control.

Open full page for SC-7(7) →
SC-7(8) Route Traffic to Authenticated Proxy Servers LOW ✓ MODERATE ✓ HIGH

Route [internal communications traffic] to [external networks] through authenticated proxy servers at managed interfaces.

Discussion

External networks are networks outside of organizational control. A proxy server is a server (i.e., system or application) that acts as an intermediary for clients requesting system resources from non-organizational or other organizational servers. System resources that may be requested include files, connections, web pages, or services. Client requests established through a connection to a proxy server are assessed to manage complexity and provide additional protection by limiting direct connectivity. Web content filtering devices are one of the most common proxy servers that provide access to the Internet. Proxy servers can support the logging of Transmission Control Protocol sessions and the blocking of specific Uniform Resource Locators, Internet Protocol addresses, and domain names. Web proxies can be configured with organization-defined lists of authorized and unauthorized websites. Note that proxy servers may inhibit the use of virtual private networks (VPNs) and create the potential for "man-in-the-middle" attacks (depending on the implementation).

Open full page for SC-7(8) →
SC-7(9) Restrict Threatening Outgoing Communications Traffic LOW MODERATE HIGH
  1. (a) Detect and deny outgoing communications traffic posing a threat to external systems; and
  2. (b) Audit the identity of internal users associated with denied communications.
Discussion

Detecting outgoing communications traffic from internal actions that may pose threats to external systems is known as extrusion detection. Extrusion detection is carried out within the system at managed interfaces. Extrusion detection includes the analysis of incoming and outgoing communications traffic while searching for indications of internal threats to the security of external systems. Internal threats to external systems include traffic indicative of denial-of-service attacks, traffic with spoofed source addresses, and traffic that contains malicious code. Organizations have criteria to determine, update, and manage identified threats related to extrusion detection.

Open full page for SC-7(9) →
SC-7(10) Prevent Exfiltration LOW MODERATE HIGH
  1. (a) Prevent the exfiltration of information; and
  2. (b) Conduct exfiltration tests [frequency].
Discussion

Prevention of exfiltration applies to both the intentional and unintentional exfiltration of information. Techniques used to prevent the exfiltration of information from systems may be implemented at internal endpoints, external boundaries, and across managed interfaces and include adherence to protocol formats, monitoring for beaconing activity from systems, disconnecting external network interfaces except when explicitly needed, employing traffic profile analysis to detect deviations from the volume and types of traffic expected, call backs to command and control centers, conducting penetration testing, monitoring for steganography, disassembling and reassembling packet headers, and using data loss and data leakage prevention tools. Devices that enforce strict adherence to protocol formats include deep packet inspection firewalls and Extensible Markup Language (XML) gateways. The devices verify adherence to protocol formats and specifications at the application layer and identify vulnerabilities that cannot be detected by devices that operate at the network or transport layers. The prevention of exfiltration is similar to data loss prevention or data leakage prevention and is closely associated with cross-domain solutions and system guards that enforce information flow requirements.

Open full page for SC-7(10) →
SC-7(11) Restrict Incoming Communications Traffic LOW MODERATE HIGH

Only allow incoming communications from [authorized sources] to be routed to [authorized destinations].

Discussion

General source address validation techniques are applied to restrict the use of illegal and unallocated source addresses as well as source addresses that should only be used within the system. The restriction of incoming communications traffic provides determinations that source and destination address pairs represent authorized or allowed communications. Determinations can be based on several factors, including the presence of such address pairs in the lists of authorized or allowed communications, the absence of such address pairs in lists of unauthorized or disallowed pairs, or meeting more general rules for authorized or allowed source and destination pairs. Strong authentication of network addresses is not possible without the use of explicit security protocols, and thus, addresses can often be spoofed. Further, identity-based incoming traffic restriction methods can be employed, including router access control lists and firewall rules.

Open full page for SC-7(11) →
SC-7(12) Host-based Protection LOW MODERATE HIGH

Implement [host-based boundary protection mechanisms] at [system components].

Discussion

Host-based boundary protection mechanisms include host-based firewalls. System components that employ host-based boundary protection mechanisms include servers, workstations, notebook computers, and mobile devices.

Open full page for SC-7(12) →
SC-7(13) Isolation of Security Tools, Mechanisms, and Support Components LOW MODERATE HIGH

Isolate [information security tools, mechanisms, and support components] from other internal system components by implementing physically separate subnetworks with managed interfaces to other components of the system.

Discussion

Physically separate subnetworks with managed interfaces are useful in isolating computer network defenses from critical operational processing networks to prevent adversaries from discovering the analysis and forensics techniques employed by organizations.

Open full page for SC-7(13) →
SC-7(14) Protect Against Unauthorized Physical Connections LOW MODERATE HIGH

Protect against unauthorized physical connections at [managed interfaces].

Discussion

Systems that operate at different security categories or classification levels may share common physical and environmental controls, since the systems may share space within the same facilities. In practice, it is possible that these separate systems may share common equipment rooms, wiring closets, and cable distribution paths. Protection against unauthorized physical connections can be achieved by using clearly identified and physically separated cable trays, connection frames, and patch panels for each side of managed interfaces with physical access controls that enforce limited authorized access to these items.

Open full page for SC-7(14) →
SC-7(15) Networked Privileged Accesses LOW MODERATE HIGH

Route networked, privileged accesses through a dedicated, managed interface for purposes of access control and auditing.

Discussion

Privileged access provides greater accessibility to system functions, including security functions. Adversaries attempt to gain privileged access to systems through remote access to cause adverse mission or business impacts, such as by exfiltrating information or bringing down a critical system capability. Routing networked, privileged access requests through a dedicated, managed interface further restricts privileged access for increased access control and auditing.

Open full page for SC-7(15) →
SC-7(16) Prevent Discovery of System Components LOW MODERATE HIGH

Prevent the discovery of specific system components that represent a managed interface.

Discussion

Preventing the discovery of system components representing a managed interface helps protect network addresses of those components from discovery through common tools and techniques used to identify devices on networks. Network addresses are not available for discovery and require prior knowledge for access. Preventing the discovery of components and devices can be accomplished by not publishing network addresses, using network address translation, or not entering the addresses in domain name systems. Another prevention technique is to periodically change network addresses.

Open full page for SC-7(16) →
SC-7(17) Automated Enforcement of Protocol Formats LOW MODERATE HIGH

Enforce adherence to protocol formats.

Discussion

System components that enforce protocol formats include deep packet inspection firewalls and XML gateways. The components verify adherence to protocol formats and specifications at the application layer and identify vulnerabilities that cannot be detected by devices operating at the network or transport layers.

Open full page for SC-7(17) →
SC-7(18) Fail Secure LOW MODERATE ✓ HIGH

Prevent systems from entering unsecure states in the event of an operational failure of a boundary protection device.

Discussion

Fail secure is a condition achieved by employing mechanisms to ensure that in the event of operational failures of boundary protection devices at managed interfaces, systems do not enter into unsecure states where intended security properties no longer hold. Managed interfaces include routers, firewalls, and application gateways that reside on protected subnetworks (commonly referred to as demilitarized zones). Failures of boundary protection devices cannot lead to or cause information external to the devices to enter the devices nor can failures permit unauthorized information releases.

Open full page for SC-7(18) →
SC-7(19) Block Communication from Non-organizationally Configured Hosts LOW MODERATE HIGH

Block inbound and outbound communications traffic between [communication clients] that are independently configured by end users and external service providers.

Discussion

Communication clients independently configured by end users and external service providers include instant messaging clients and video conferencing software and applications. Traffic blocking does not apply to communication clients that are configured by organizations to perform authorized functions.

Open full page for SC-7(19) →
SC-7(20) Dynamic Isolation and Segregation LOW MODERATE HIGH

Provide the capability to dynamically isolate [system components] from other system components.

Discussion

The capability to dynamically isolate certain internal system components is useful when it is necessary to partition or separate system components of questionable origin from components that possess greater trustworthiness. Component isolation reduces the attack surface of organizational systems. Isolating selected system components can also limit the damage from successful attacks when such attacks occur.

Open full page for SC-7(20) →
SC-7(21) Isolation of System Components LOW MODERATE ✓ HIGH

Employ boundary protection mechanisms to isolate [system components] supporting [missions and/or business functions].

Discussion

Organizations can isolate system components that perform different mission or business functions. Such isolation limits unauthorized information flows among system components and provides the opportunity to deploy greater levels of protection for selected system components. Isolating system components with boundary protection mechanisms provides the capability for increased protection of individual system components and to more effectively control information flows between those components. Isolating system components provides enhanced protection that limits the potential harm from hostile cyber-attacks and errors. The degree of isolation varies depending upon the mechanisms chosen. Boundary protection mechanisms include routers, gateways, and firewalls that separate system components into physically separate networks or subnetworks; cross-domain devices that separate subnetworks; virtualization techniques; and the encryption of information flows among system components using distinct encryption keys.

Open full page for SC-7(21) →
SC-7(22) Separate Subnets for Connecting to Different Security Domains LOW MODERATE HIGH

Implement separate network addresses to connect to systems in different security domains.

Discussion

The decomposition of systems into subnetworks (i.e., subnets) helps to provide the appropriate level of protection for network connections to different security domains that contain information with different security categories or classification levels.

Open full page for SC-7(22) →
SC-7(23) Disable Sender Feedback on Protocol Validation Failure LOW MODERATE HIGH

Disable feedback to senders on protocol format validation failure.

Discussion

Disabling feedback to senders when there is a failure in protocol validation format prevents adversaries from obtaining information that would otherwise be unavailable.

Open full page for SC-7(23) →
SC-7(24) Personally Identifiable Information LOW MODERATE HIGH

For systems that process personally identifiable information:

  1. (a) Apply the following processing rules to data elements of personally identifiable information: [processing rules];
  2. (b) Monitor for permitted processing at the external interfaces to the system and at key internal boundaries within the system;
  3. (c) Document each processing exception; and
  4. (d) Review and remove exceptions that are no longer supported.
Discussion

Managing the processing of personally identifiable information is an important aspect of protecting an individual’s privacy. Applying, monitoring for, and documenting exceptions to processing rules ensure that personally identifiable information is processed only in accordance with established privacy requirements.

Open full page for SC-7(24) →
SC-7(25) Unclassified National Security System Connections LOW MODERATE HIGH

Prohibit the direct connection of [unclassified national security system] to an external network without the use of [boundary protection device].

Discussion

A direct connection is a dedicated physical or virtual connection between two or more systems. Organizations typically do not have complete control over external networks, including the Internet. Boundary protection devices (e.g., firewalls, gateways, and routers) mediate communications and information flows between unclassified national security systems and external networks.

Open full page for SC-7(25) →
SC-7(26) Classified National Security System Connections LOW MODERATE HIGH

Prohibit the direct connection of a classified national security system to an external network without the use of [boundary protection device].

Discussion

A direct connection is a dedicated physical or virtual connection between two or more systems. Organizations typically do not have complete control over external networks, including the Internet. Boundary protection devices (e.g., firewalls, gateways, and routers) mediate communications and information flows between classified national security systems and external networks. In addition, approved boundary protection devices (typically managed interface or cross-domain systems) provide information flow enforcement from systems to external networks.

Open full page for SC-7(26) →
SC-7(27) Unclassified Non-national Security System Connections LOW MODERATE HIGH

Prohibit the direct connection of [unclassified, non-national security system] to an external network without the use of [boundary protection device].

Discussion

A direct connection is a dedicated physical or virtual connection between two or more systems. Organizations typically do not have complete control over external networks, including the Internet. Boundary protection devices (e.g., firewalls, gateways, and routers) mediate communications and information flows between unclassified non-national security systems and external networks.

Open full page for SC-7(27) →
SC-7(28) Connections to Public Networks LOW MODERATE HIGH

Prohibit the direct connection of [system] to a public network.

Discussion

A direct connection is a dedicated physical or virtual connection between two or more systems. A public network is a network accessible to the public, including the Internet and organizational extranets with public access.

Open full page for SC-7(28) →
SC-7(29) Separate Subnets to Isolate Functions LOW MODERATE HIGH

Implement [one of: physically; logically] separate subnetworks to isolate the following critical system components and functions: [critical system components and functions].

Discussion

Separating critical system components and functions from other noncritical system components and functions through separate subnetworks may be necessary to reduce susceptibility to a catastrophic or debilitating breach or compromise that results in system failure. For example, physically separating the command and control function from the in-flight entertainment function through separate subnetworks in a commercial aircraft provides an increased level of assurance in the trustworthiness of critical system functions.

Open full page for SC-7(29) →

Implementation Guidance

Engineering Interpretation

Original engineering commentary written for this explorer — not NIST source text and not authoritative guidance.

No engineering interpretation has been authored for SC-7 yet. This section is architected to receive it — see the Requirements and Assessment sections above for the authoritative NIST source content in the meantime.

Assessment

NIST SP 800-53A REV 5.2.0

Assessment Objectives

  1. one of the following PARAMETER VALUES is selected: {physically; logically};
  2. communications at external managed interfaces to the system are monitored;
  3. communications at external managed interfaces to the system are controlled;
  4. communications at key internal managed interfaces within the system are monitored;
  5. communications at key internal managed interfaces within the system are controlled;
  6. subnetworks for publicly accessible system components are <SC-07_ODP SELECTED PARAMETER VALUE> separated from internal organizational networks;
  7. external networks or systems are only connected to through managed interfaces consisting of boundary protection devices arranged in accordance with an organizational security and privacy architecture.

Examine

[SELECT FROM: System and communications protection policy; procedures addressing boundary protection; list of key internal boundaries of the system; system design documentation; boundary protection hardware and software; system configuration settings and associated documentation; enterprise security architecture documentation; system audit records; system security plan; other relevant documents or records].

Interview

[SELECT FROM: System/network administrators; organizational personnel with information security responsibilities; system developer; organizational personnel with boundary protection responsibilities].

Test

[SELECT FROM: Mechanisms implementing boundary protection capabilities].

Overlays

OT/ICS Overlay SP 800-82r3

NIST SP 800-82r3 Appendix F, Table 22. Blank baseline means the control/control enhancement is not selected in that initial OT baseline.

LOW

  • Base control: Included (matches standard baseline)
  • Added: (28) (29)

MODERATE

  • Base control: Included (matches standard baseline)
  • Included: (3) (4) (5) (7) (8)
  • Added: (18) (28) (29)

HIGH

  • Base control: Included (matches standard baseline)
  • Included: (3) (4) (5) (7) (8) (18) (21)
  • Added: (28) (29)

STIGs & CCIs

No STIG checks or CCI mappings are currently loaded for SC-7. This section is architected to display, per product: STIG ID, Finding ID, Severity, Title, Description, Check, Fix, CCI, and NIST control mapping — but nothing is populated here until a real DISA STIG/CCI dataset is ingested.

Learn more about STIG/CCI integration →

Evidence

Potential Evidence — Derived

Categorized from the SP 800-53A "Examine"/"Test" artifact list above by keyword — not an authoritative NIST evidence list.

Policy

  • System and communications protection policy
  • system security plan

Configuration

  • system design documentation
  • system configuration settings and associated documentation
  • enterprise security architecture documentation

Testing

  • Mechanisms implementing boundary protection capabilities

Other Records

  • procedures addressing boundary protection
  • list of key internal boundaries of the system
  • boundary protection hardware and software
  • system audit records
  • other relevant documents or records