Domain 7Security OperationsCORE

Log Management, SIEM & Telemetry Analysis

Centralized logging architectures, SIEM correlation, SOAR automated playbooks, NTP clock synchronization for evidentiary integrity, and user behavioral analytics.

Domain: Domain 7: Security Operations•Updated: 2026-08-26
#Log Management#SIEM#SOAR#Telemetry#NTP#Continuous Monitoring#Egress Filtering

CISSP Domain 7: Log Management, SIEM & Telemetry Analysis — Mindmap Review Study Guide

═══════════════════════════════════

PART 1: MERMAID MINDMAP

═══════════════════════════════════

mindmap
  root((Logging and Monitoring))
    Log Event Sources
      Network Devices
      IDS and IPS
      Servers and Endpoints
      Operating Systems
      Applications
      Anti-malware
    Log Review and Analysis
      Selectivity and Relevance
      Real-time Review
      Errors
      Unauthorized Modifications
      Breaches
    SIEM System
      Generation
      Limiting Log File Size
        Circular Overwrite
        Clipping Levels
      Time Stamps
        Consistent Format
        Network Time Protocol
      Transmission
      Collection and Aggregation
      Normalization
      Analysis
      Retention
      Disposal
    Continuous Monitoring
      Identify Systems
      Identify Risks
      Apply Controls
      Monitor Effectiveness

═══════════════════════════════════

PART 2: TECHNICAL DEFINITIONS & CONCEPTS

═══════════════════════════════════

Log Event Sources

Log Event Data Sources — Almost every system across an organization can generate log event data. Sources include network devices (firewalls, routers, switches), Intrusion Detection and Prevention Systems (IDS & IPS), servers, desktops, laptops, operating systems, applications, and anti-malware systems.

Log Review and Analysis

Selectivity — The practice of configuring systems to only log what is relevant. This is necessary because many systems can generate an avalanche of event data, making it critical to filter out noise.

Real-time Review — The capability to review logging event data as close to real-time as possible, preventing scenarios where a significant breach is only discovered months after it occurred.

Errors — Anomalies indicating that something is broken and needs to be fixed. For example, a webserver generating many Error 404 (file not found) messages is a clear indication of an error.

Unauthorized Modifications — Changes made to a system without authorization. Attackers often exploit a vulnerability, break in, install a backdoor, and then patch the vulnerability behind themselves. Looking for unauthorized patching is a key indicator of a breach.

Breaches — Incidents where systems are compromised. From a security perspective, monitoring for breaches includes looking for systems being used for crypto currency mining, data exfiltration occurring, or impending ransomware attacks.

SIEM System

Security Information and Event Management (SIEM) — Also referred to as SIMs. These systems automate the tasks and analysis required for logging and monitoring to solve the challenge of finding a “needle in a haystack” across a plethora of devices generating massive volumes of event data.

Generation — The first step before feeding data into a SIEM, which involves enabling logging on devices across the environment so that they are actively generating log data.

Limiting Log File Size — A necessary configuration for endpoint devices (like firewalls, routers, and switches) because they generate massive amounts of data but have very limited onboard storage.

Method Mechanism Transcript Example
Circular Overwrite Sets a maximum log file size. When reached, the system circles back to the top of the file and overwrites data until the max size is reached again, repeating continuously. Setting a max size of 10MB or 10,000 lines.
Clipping Levels Sets an event threshold. Below the threshold, nothing is logged; at or above the threshold, logging begins. Used to ignore normal noise and capture actual attacks. Setting a threshold of 3 failed logins. 1-2 are ignored (mistyped password), but 3 or more are logged (brute force attempt).

Time Stamps — Critical metadata for each log event that must be managed carefully to ensure events can be accurately tracked and correlated.

Consistent Format — The requirement that all timestamps use the exact same format (e.g., year, month, day, and 24-hour clock) so that events from different systems can be easily correlated.

Network Time Protocol (NTP) — The protocol used to synchronize the clocks of all systems across the environment. It is very difficult to trace how an attacker traversed a network if clocks are out of sync (e.g., one system is 3 seconds slower, another is 5 seconds fast, or another’s date is set to 1979).

Transmission — The process of sending generated log event data from any device in the environment to the SIEM system in real-time.

Collection and Aggregation — The SIEM function that collects and aggregates all event data from across the environment into one central system.

Normalization — The process where the SIEM cleans up event data from disparate devices so that all the variables are comparable.

Analysis — The process where the SIEM applies various techniques (such as event correlation, statistical models, and rules) to the normalized data to look for errors and anomalies.

Retention — The practice of retaining log event data for long-term storage. This enables longitudinal analysis and tracking, and ensures the organization meets contractual or regulatory requirements for log retention.

Disposal — The process of securely and defensibly destroying event data when it no longer needs to be retained.

Continuous Monitoring

Continuous Monitoring (CSM) — Also referred to as Continuous Security Monitoring. It is a specific organizational process to manage security posture against an ever-changing threat landscape.

⚠️ EXAM TIP: Memorize the exact 4-step order for Continuous Monitoring as explicitly outlined in the transcript:

  1. Identifies all their systems.
  2. Identifies the risks associated with each system.
  3. Applies the appropriate controls to mitigate the risks.
  4. Continuously monitors the controls to assess their effectiveness against the ever-changing threat landscape.