Restrict Incoming Communications Traffic
LOW MODERATE HIGHRequirements NIST SOURCE
Only allow incoming communications from [authorized sources] to be routed to [authorized destinations].
Discussion (NIST Supplemental Guidance)
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.
Implementation Guidance
Original engineering commentary written for this explorer — not NIST source text and not authoritative guidance.
No engineering interpretation has been authored for SC-7(11) 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
Assessment Objectives
- authorized sources of incoming communications to be routed are defined;
- authorized destinations to which incoming communications from authorized sources may be routed are defined;
- only incoming communications from <SC-07(11)_ODP[01] authorized sources> are allowed to be routed to <SC-07(11)_ODP[02] authorized destinations>.
Examine
[SELECT FROM: System and communications protection policy; procedures addressing boundary protection; system design documentation; system configuration settings and associated 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 with respect to source/destination address pairs].
Overlays
STIGs & CCIs
No STIG checks or CCI mappings are currently loaded for SC-7(11). 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
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
Testing
- Mechanisms implementing boundary protection capabilities with respect to source/destination address pairs
Other Records
- procedures addressing boundary protection
- system audit records
- other relevant documents or records