Linux process commands stopping firewall and security services

Flags Linux commands that stop/disable firewall/security services or set SELinux enforcement to 0.

FreeReviewedSigma · Medium · v2
Product
linux
Category
process_creation
Author
Ömer Günal, Alejandro Ortuno, oscd.community (SigmaHQ), DRL 1.1
Published
2020-06-17
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 activity where commands attempt to stop or disable common security controls, including iptables/ip6tables, firewalld, and endpoint protection services (e.g., cbdaemon and falcon-sensor). Such actions can impair host defenses and are consistent with attacker attempts to evade detection or maintain persistence. It relies on process creation telemetry, matching image paths and command-line arguments like stop/disable/off and service identifiers.

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 process commands stopping firewall and security services
Pivot detection · T1686 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. 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.