Linux syslog: Detect suspicious BIND/named error messages

Alerts on Linux syslog messages with BIND named fatal or denied DNS error strings.

FreeReviewedSigma · High · v3
Product
linux
Service
syslog
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2018-02-20
Updated
2026-07-31

ATT&CK techniques

Initial Access
  1. Recon

  2. Resource Dev

  3. Execution

  4. Persistence

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule matches specific error strings in Linux syslog associated with BIND/named, including fatal-exit indications and denied or dropped packet conditions. Such messages can reflect probing or exploitation attempts that trigger unexpected server behavior or access denials (for example, attempting restricted DNS operations). It relies on syslog text containing the configured keyword phrases from the named service.

Related detections9 linkedT1190 — drag to rearrange
Malicious SharePoint ToolShell Exploitation via ToolPane Endpoint
Malicious Exchange Mailbox Export to ASPX via New-MailboxExportRequest
Suspicious Shell Spawned by ActiveMQ Java Process
Cleo Autorun Exploitation via Healthcheck File Drop
Suspicious SharePoint Worker Process Spawning Command Interpreter via ToolShell
Malicious IIS Worker Process Spawning Command Shell Reconnaissance
Potential StyleSmuggler (CVE-2026-75650) Exploitation Attempt - Magento GraphQL Styles Parameter (via webserver)
Cisco IOS XE Configuration Change by Web UI WSMA User
Possible React2Shell CVE-2025-55182 Prototype Pollution Exploitation
Linux syslog: Detect suspicious BIND/named error messages
Pivot detection · T1190 · 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.