Linux UFW Disable Attempt via Process Execution

Flags Linux commands that stop/flush/unload or disable UFW, reducing firewall protection and exposure.

FreeReviewedSigma · Medium · v3
Product
linux
Category
process_creation
Author
Joseliyo Sanchez, @Joseliyo_Jstnk (SigmaHQ), DRL 1.1
Published
2023-01-18
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 identifies Linux process executions attempting to disable or stop the Uncomplicated Firewall (UFW). It matches command lines containing UFW disable actions (including the `ufw disable` form and the `systemctl disable ufw` form) and `ufw-init` stop/flush/force-stop sequences that unload or reset firewall state. Disabling UFW can reduce host network protection, and the detection relies on Linux process creation telemetry with command-line details.

Related detections9 linkedT1686 — drag to rearrange
Suspicious Disabling or Flushing of the Linux Host Firewall (via process_creation)
Malicious Firewall Deactivation - PowerShell (via powershell)
Malicious Firewall Deactivation - Firewall (via firewall-as)
Suspicious Outbound Firewall Block Rule Added via Netsh Advfirewall
Malicious Windows Firewall Disable via Netsh
OpenSSH Server Firewall Configuration on Windows - Firewall (via firewall-as)
Suspicious Firewall Rule Added Using PowerShell or CMD (via firewall-as)
Suspicious Firewall Rule Masquerading as CloudExperienceHost via netsh
Suspicious Firewall Rule Masquerading As Windows Update (via process_creation)
Linux UFW Disable Attempt via Process Execution
Pivot detection · T1686 · 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.