Restrict Threatening Outgoing Communications Traffic
LOW MODERATE HIGHRequirements NIST SOURCE
Requirement Context
This element is part of SC-7(9) — Restrict Threatening Outgoing Communications Traffic. See the Assessment section below for the related SP 800-53A examine/interview/test procedures. No engineering interpretation has been authored for this control yet.
Requirement Context
This element is part of SC-7(9) — Restrict Threatening Outgoing Communications Traffic. See the Assessment section below for the related SP 800-53A examine/interview/test procedures. No engineering interpretation has been authored for this control yet.
Discussion (NIST Supplemental Guidance)
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.
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(9) 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
- outgoing communications traffic posing a threat to external systems is detected;
- outgoing communications traffic posing a threat to external systems is denied;
- the identity of internal users associated with denied communications is audited.
Examine
[SELECT FROM: System and communications protection policy; procedures addressing boundary protection; system design documentation; system hardware and software; system architecture; 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; mechanisms implementing the detection and denial of threatening outgoing communications traffic; mechanisms implementing auditing of outgoing communications traffic].
Overlays
STIGs & CCIs
No STIG checks or CCI mappings are currently loaded for SC-7(9). 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 architecture
- system configuration settings and associated documentation
Testing
- Mechanisms implementing boundary protection capabilities
- mechanisms implementing the detection and denial of threatening outgoing communications traffic
- mechanisms implementing auditing of outgoing communications traffic
Other Records
- procedures addressing boundary protection
- system hardware and software
- system audit records
- other relevant documents or records