Skip to main content

MON-01.3: Inbound & Outbound Communications Traffic

MON 9 — Critical Detect

Mechanisms exist to continuously monitor inbound and outbound communications traffic for unusual or unauthorized activities or conditions.

Control Question: Does the organization continuously monitor inbound and outbound communications traffic for unusual or unauthorized activities or conditions?

General (25)
Framework Mapping Values
AICPA TSC 2017:2022 (used for SOC 2) (source) CC7.2
CSA IoT SCF 2 OPA-04
GovRAMP Core SI-04(04)
GovRAMP Moderate SI-04(04)
GovRAMP High SI-04(04)
ISO 27002 2022 8.16
NIST 800-53 R4 SI-4(4)
NIST 800-53 R4 (moderate) SI-4(4)
NIST 800-53 R4 (high) SI-4(4)
NIST 800-53 R5 (source) SI-4(4)
NIST 800-53B R5 (moderate) (source) SI-4(4)
NIST 800-53B R5 (high) (source) SI-4(4)
NIST 800-82 R3 MODERATE OT Overlay SI-4(4)
NIST 800-82 R3 HIGH OT Overlay SI-4(4)
NIST 800-171 R2 (source) 3.14.6
NIST 800-171A (source) 3.14.6[a] 3.14.6[b] 3.14.6[c]
NIST 800-171 R3 (source) 03.13.01.a 03.14.06.c
NIST 800-171A R3 (source) A.03.13.01.a[01] A.03.13.01.a[03] A.03.14.06.c[01] A.03.14.06.c[02]
NIST CSF 2.0 (source) DE.CM-01
OWASP Top 10 2021 A01:2021 A07:2021 A09:2021
SPARTA CM0073
SCF CORE Mergers, Acquisitions & Divestitures (MA&D) MON-01.3
SCF CORE ESP Level 1 Foundational MON-01.3
SCF CORE ESP Level 2 Critical Infrastructure MON-01.3
SCF CORE ESP Level 3 Advanced Threats MON-01.3
US (18)
EMEA (3)
Framework Mapping Values
EMEA EU NIS2 Annex 3.2.3(a)
EMEA Israel CDMO 1.0 9.9 9.10 10.9
EMEA Saudi Arabia SACS-002 TPC-40
APAC (1)
Framework Mapping Values
APAC New Zealand NZISM 3.6 16.6.10.C.01 16.6.10.C.02 18.4.8.C.01 18.4.8.C.02 18.4.8.C.03
Americas (1)
Framework Mapping Values
Americas Canada ITSP-10-171 03.13.01.A 03.14.06.C

Capability Maturity Model

Level 0 — Not Performed

There is no evidence of a capability to continuously monitor inbound and outbound communications traffic for unusual or unauthorized activities or conditions.

Level 1 — Performed Informally

C|P-CMM1 is N/A, since a structured process is required to continuously monitor inbound and outbound communications traffic for unusual or unauthorized activities or conditions.

Level 2 — Planned & Tracked

Continuous Monitoring (MON) efforts are requirements-driven and governed at a local/regional level, but are not consistent across the organization. CMM Level 2 control maturity would reasonably expect all, or at least most, the following criteria to exist: o Identify cybersecurity and data protection controls that are appropriate to address applicable statutory, regulatory and contractual requirements for situational awareness management. o Configure alerts for critical or sensitive data that is stored, transmitted and processed on assets. o Use a structured process to review and analyze logs.

  • Situational awareness management is decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices.
  • Secure baseline configurations generate logs that contain sufficient information to establish necessary details of activity and allow for forensics analysis.
  • IT/cybersecurity personnel:
  • A log aggregator, or similar automated tool, provides an event log report generation capability to aid in detecting and assessing anomalous activities on business-critical systems.
Level 3 — Well Defined

Continuous Monitoring (MON) efforts are standardized across the organization and centrally managed, where technically feasible, to ensure consistency. CMM Level 3 control maturity would reasonably expect all, or at least most, the following criteria to exist: o Governs asset management that ensures compliance with requirements for asset management. o Leverages a Configuration Management Database (CMDB), or similar tool, as the authoritative source of IT assets. o Centrally collects logs and is protected according to the manufacturer’s security guidelines to protect the integrity of the event logs with cryptographic mechanisms. o Monitors the organization for Indicators of Compromise (IoC) and provides 24x7x365 near real-time alerting capability. o Is configured to alert incident response personnel of detected suspicious events such that incident responders can look to terminate suspicious events.

  • An IT Asset Management (ITAM) function, or similar function:
  • A Security Incident Event Manager (SIEM), or similar automated tool:
  • Both inbound and outbound network traffic is monitored for unauthorized activities to identify prohibited activities and assist incident handlers with identifying potentially compromised systems.
  • A Security Operations Center (SOC), or similar function, enables cybersecurity operations covering preparation, detection and analysis, containment, eradication and recovery.
Level 4 — Quantitatively Controlled

See C|P-CMM3. There are no defined C|P-CMM4 criteria, since it is reasonable to assume a quantitatively-controlled process is not necessary to continuously monitor inbound and outbound communications traffic for unusual or unauthorized activities or conditions.

Level 5 — Continuously Improving

See C|P-CMM4. There are no defined C|P-CMM5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to continuously monitor inbound and outbound communications traffic for unusual or unauthorized activities or conditions.

Assessment Objectives

  1. MON-01.3_A01 criteria for unusual or unauthorized activities or conditions for inbound communications traffic are defined.
  2. MON-01.3_A02 criteria for unusual or unauthorized activities or conditions for outbound communications traffic are defined.
  3. MON-01.3_A03 unusual or unauthorized activities or conditions that are to be monitored in outbound communications traffic are defined.
  4. MON-01.3_A04 inbound communications traffic is monitored to detect unusual or unauthorized activities or conditions.
  5. MON-01.3_A05 outbound communications traffic is monitored to detect unusual or unauthorized activities or conditions.
  6. MON-01.3_A06 anomalous or suspicious behavior is defined.
  7. MON-01.3_A07 systems, applications and services are monitored to detect attacks and indicators of potential attacks.
  8. MON-01.3_A08 communications at external managed interfaces to the system are monitored.
  9. MON-01.3_A09 communications at key internal managed interfaces within the system are monitored.
  10. MON-01.3_A10 the frequency at which to monitor inbound communications traffic for unusual or unauthorized activities or conditions is defined.

Evidence Requirements

E-MON-01 Event Log Review & Analysis

Documented evidence of security event log review and analysis (e.g., system monitoring records).

Event Log Monitoring
E-MON-06 Automated Event Escalation & Reporting

Documented evidence of a capability for selected events to alert applicable personnel, or roles, based on the type of event. This can be demonstrated by the configuration of a Security Incident Event Manager (SIEM), or similar technology, that helps automate event log analysis and reporting.

Event Log Monitoring
E-MON-07 Situational Awareness

Documented evidence of the organization leveraging knowledge of event log generation to gain situational awareness of cross-domain activities (e.g., technology issues, security events, policy violations, service provider activities, remote workforce activities, physical security events, etc.).

Event Log Monitoring

Technology Recommendations

Micro/Small

  • Intrusion Detection / Prevention Systems (IDS / IPS)

Small

  • Intrusion Detection / Prevention Systems (IDS / IPS)

Medium

  • Intrusion Detection / Prevention Systems (IDS / IPS)
  • Extended Detection and Response (XDR)

Large

  • Intrusion Detection / Prevention Systems (IDS / IPS)
  • Extended Detection and Response (XDR)

Enterprise

  • Intrusion Detection / Prevention Systems (IDS / IPS)
  • Extended Detection and Response (XDR)

The Secure Controls Framework (SCF) is maintained by SCF Council. Use of SCF content is subject to the SCF Terms & Conditions.

Manage this control in SCF Connect

Track implementation status, collect evidence, and map controls to your compliance frameworks automatically.