Linux auditd: Clear kernel ring buffer via syslog syscall (action 5/4/6)

Flags auditd syslog syscall actions that clear or suppress kernel ring buffer (dmesg) logs.

FreeReviewedSigma · Medium · v3
Product
linux
Service
auditd
Author
Milad Cheraghi (SigmaHQ), DRL 1.1
Published
2025-05-27
Updated
2026-07-31

ATT&CK techniques

  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

  14. Impact

What it detects

This rule flags Linux syslog syscall executions where the syscall action code clears kernel ring buffer content or disables console logging. Attackers can use these operations to reduce or remove evidence from dmesg logs after exploitation or privilege escalation. The detection relies on auditd records capturing the syslog syscall with argument values matching actions 4, 5, and 6 on 32-bit or 64-bit architectures.

Related detections9 linkedT1685.006 — drag to rearrange
Suspicious Deletion of System Logs Under var log on Linux Appliance
Suspicious Clearing of System Logs on Linux (via process_creation)
Malicious Sed Tampering of Juniper Syslog Configuration by UNC3886 (via process_creation)
Suspicious Clearing of Linux Authentication and History Logs
Suspicious Linux Log Sanitization via sed In-Place Edit
Suspicious utmpdump Usage for wtmp Log Manipulation
Linux Syslog Clearing or Removal Using System Utilities
macOS Host Indicator Removal via rm/unlink/shred of Local Log Paths
Linux process attempts to delete log files using rm, rmdir, shred, or unlink
Linux auditd: Clear kernel ring buffer via syslog syscall (action 5/4/6)
Pivot detection · T1685.006 · 9 related

Changelog

v3
  1. v3
    Candidate ingested via manual entry.2026-07-31
  2. v2
    Candidate ingested via manual entry.2026-07-31
  3. v1
    No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.