Skip to main content

MON-08.3: Cryptographic Protection of Event Log Information

MON 5 — Medium Protect

Cryptographic mechanisms exist to protect the integrity of event logs and audit tools.

Control Question: Are cryptographic mechanisms utilized to protect the integrity of event logs and audit tools?

General (11)
Framework Mapping Values
CSA CCM 4 LOG-04 LOG-09
CSA IoT SCF 2 MON-05
GovRAMP High AU-09(03)
NIST 800-53 R4 AU-9(3)
NIST 800-53 R4 (high) AU-9(3)
NIST 800-53 R5 (source) AU-9(3)
NIST 800-53B R5 (high) (source) AU-9(3)
NIST 800-82 R3 HIGH OT Overlay AU-9(3)
NIST 800-171 R3 (source) 03.03.08.a
SCF CORE ESP Level 2 Critical Infrastructure MON-08.3
SCF CORE ESP Level 3 Advanced Threats MON-08.3
US (4)
Framework Mapping Values
US FedRAMP R4 AU-9(3)
US FedRAMP R4 (high) AU-9(3)
US FedRAMP R5 (source) AU-9(3)
US FedRAMP R5 (high) (source) AU-9(3)
Americas (1)
Framework Mapping Values
Americas Canada ITSP-10-171 03.03.08.A

Capability Maturity Model

Level 0 — Not Performed

There is no evidence of a capability to Cryptographic protect the integrity of event logs and audit tools.

Level 1 — Performed Informally

C|P-CMM1 is N/A, since a structured process is required to Cryptographic protect the integrity of event logs and audit tools.

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 Cryptographic protect the integrity of event logs and audit tools.

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 Cryptographic protect the integrity of event logs and audit tools.

Assessment Objectives

  1. MON-08.3_A01 cryptographic mechanisms to protect the integrity of audit information and audit tools are implemented.

Technology Recommendations

Micro/Small

  • Secure Baseline Configurations (SBC)

Small

  • Secure Baseline Configurations (SBC)

Medium

  • Secure Baseline Configurations (SBC)

Large

  • Secure Baseline Configurations (SBC)

Enterprise

  • Secure Baseline Configurations (SBC)

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.