How Smart Filtering Can Reduce SIEM Log Noise

· Original article ↗

Summary

The article explains how filtering low-security-value logs before SIEM storage can reduce noise and cost. Huntress says its early-adopter Managed SIEM filtered more than 20 Windows event types, including Event ID 4627.

Key points

  • The article argues that collecting every available log can increase SIEM noise and costs; it recommends prioritizing logs with security value.
  • It identifies VPN password-authentication and MFA events as security-relevant, while noting that other VPN debug data may be more useful to networking teams.
  • Disk-space and service-status logs are presented as primarily IT operations data that may be low priority for a security-focused SIEM.
  • Huntress says its early-adopter Managed SIEM filtered more than 20 Windows event types, including Event ID 4627, which reports group membership information.
  • Huntress describes filtering both near the data source and again before storage, while promoting its Managed SIEM product.

Article Details

Defense Focus
Reduce SIEM noise and ingestion costs by filtering low-security-value log data before collection while retaining events useful for threat detection and investigation.
Detection Methods
  • Review event types for noise and security value, then filter low-value events before they reach storage.
  • Apply a second filtering pass with rulesets before storage to remove non-security events missed by the initial filtering stage.
  • Retain security-relevant authentication and MFA events, and use endpoint detection and response telemetry to track privilege escalations.
Data Sources
  • Windows event logs, including Windows Event ID 4627 (Group Membership Information)
  • VPN security password-authentication and MFA events
  • Endpoint detection and response telemetry for privilege escalations
Rule Types
  • SIEM Smart Filtering rulesets for pre-collection and pre-storage event filtering
Platforms
  • Huntress Managed SIEM
Defensive Actions
  • Define which events constitute security events for the organization and its compliance requirements rather than collecting every available log.
  • Filter noisy, low-security-value events such as Windows Event ID 4627 before SIEM storage.
  • Tune log collection as close to the data source as possible to limit excess ingestion and false positives.
  • Keep security-relevant authentication and MFA events; use dedicated service-availability monitoring for operational events that do not support security detection.

Vendors

Products

Related Articles