Skip to main content

MON-16.3: Unauthorized Activities

MON 8 — High Detect

Mechanisms exist to monitor for unauthorized activities, accounts, connections, devices and software.

Control Question: Does the organization monitor for unauthorized activities, accounts, connections, devices and software?

General (10)
Framework Mapping Values
CIS CSC 8.1 2.3
CIS CSC 8.1 IG1 2.3
CIS CSC 8.1 IG2 2.3
CIS CSC 8.1 IG3 2.3
CSA CCM 4 LOG-11 LOG-13
NIST CSF 2.0 (source) DE.CM-03
SCF CORE Mergers, Acquisitions & Divestitures (MA&D) MON-16.3
SCF CORE ESP Level 1 Foundational MON-16.3
SCF CORE ESP Level 2 Critical Infrastructure MON-16.3
SCF CORE ESP Level 3 Advanced Threats MON-16.3
US (4)
Framework Mapping Values
US FFIEC D3.DC.Ev.B.3
US HIPAA HICP Large Practice 1.L.A 6.L.B 6.L.D 9.L.B
US NERC CIP 2024 (source) CIP-006-6 1.4
US SSA EIESR 8.0 5.6
EMEA (3)
Framework Mapping Values
EMEA Israel CDMO 1.0 21.10
EMEA Saudi Arabia OTCC-1 2022 2-3-1-11 2-3-1-12
EMEA UK DEFSTAN 05-138 4106

Capability Maturity Model

Level 0 — Not Performed

There is no evidence of a capability to monitor for unauthorized activities, accounts, connections, devices and software.

Level 1 — Performed Informally

Continuous Monitoring (MON) efforts are ad hoc and inconsistent. CMM Level 1 control maturity would reasonably expect all, or at least most, the following criteria to exist:

  • Generating event logs and the review of event logs is narrowly-focused to business-critical systems and/ or systems that store, processes and/ or transmit sensitive/regulated data.
  • Secure baseline configurations generate logs that contain sufficient information to establish necessary details of activity and allow for forensics analysis.
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.
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 monitor for unauthorized activities, accounts, connections, devices and software.

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 monitor for unauthorized activities, accounts, connections, devices and software.

Assessment Objectives

  1. MON-16.3_A01 unauthorized activities are defined.
  2. MON-16.3_A02 personnel or roles to be notified when unauthorized activities are detected is/are defined.
  3. MON-16.3_A03 methods to detect unauthorized activities are identified.
  4. MON-16.3_A04 monitoring mechanisms are configured to detect unauthorized activities.
  5. MON-16.3_A05 personnel or roles are notified when unauthorized activities are detected.

Evidence Requirements

E-IRO-02 Indicators of Compromise (IOC)

Documented evidence of defined Indicators of Compromise (IOC).

Incident Response
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

  • Indicators of Compromise (IoC)
  • Indicators of Exposure (IoE)
  • Managed Security Services Provider (MSSP)

Small

  • Indicators of Compromise (IoC)
  • Indicators of Exposure (IoE)
  • Security Incident Event Manager (SIEM)
  • Managed Security Services Provider (MSSP)

Medium

  • Indicators of Compromise (IoC)
  • Indicators of Exposure (IoE)
  • Security Incident Event Manager (SIEM)
  • Extended Detection and Response (XDR)
  • Managed Security Services Provider (MSSP)

Large

  • Indicators of Compromise (IoC)
  • Indicators of Exposure (IoE)
  • Security Incident Event Manager (SIEM)
  • Extended Detection and Response (XDR)
  • Managed Security Services Provider (MSSP)

Enterprise

  • Indicators of Compromise (IoC)
  • Indicators of Exposure (IoE)
  • Security Incident Event Manager (SIEM)
  • Extended Detection and Response (XDR)
  • Managed Security Services Provider (MSSP)

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.