Cross-source coverage

T1489 / ATT&CK

Service Stop

95 rules · 92 families across 9 sources.

1 deprecated hidden · include

From MITRE ATT&CK 19.2

Adversaries may stop or disable services on a system to render those services unavailable to legitimate users. Stopping critical services or processes can inhibit or stop response to an incident or aid in the adversary's overall objectives to cause damage to the environment.

Adversaries may accomplish this by disabling individual services of high importance to an organization, such as MSExchangeIS, which will make Exchange content inaccessible. In some cases, adversaries may stop or disable many or all services to render systems unusable. Services or processes may not allow for modification of their data stores while running. Adversaries may stop services or processes in order to conduct Data Destruction or Data Encrypted for Impact on the data stores of services like Exchange and SQL Server, or on virtual machines hosted on ESXi infrastructure.

Threat actors may also disable or stop service in cloud environments. For example, by leveraging the DisableAPIServiceAccess API in AWS, a threat actor may prevent the service from creating service-linked roles on new accounts in the AWS Organization.

Tactics
Impact
Platforms
ESXi · IaaS · Linux · macOS · Windows
Telemetry
WinEventLog:SysmonWinEventLog:SecurityWinEventLog:Systemauditd:SYSCALLlinux:syslogmacos:unifiedlogesxi:hostd

How MITRE says to detect it DET0021

Behavioral Detection for Service Stop across Platforms

Windows Analytic 0061

Adversary disables or stops critical services (e.g., Exchange, SQL, AV, endpoint monitoring) using native utilities or API calls, often preceding destructive actions (T1485, T1486). Behavioral chain: Elevated execution context + stop-service or sc.exe or ChangeServiceConfigW + terminated or disabled service + possible follow-up file manipulation.

  • WinEventLog:Sysmon EventCode=1
  • WinEventLog:Security EventCode=4672
  • WinEventLog:System EventCode=7036
  • WinEventLog:Sysmon EventCode=4

Linux Analytic 0062

Adversary executes systemctl or service stop targeting high-value services (e.g., mysql, sshd), possibly followed by rm or shred against data stores. Behavioral chain: sudo/su usage + stop command + /var/log/messages or syslog entries + file access/delete.

  • auditd:SYSCALL execve of systemctl or service stop
  • auditd:SYSCALL unlink/unlinkat on service binaries or data targets
  • linux:syslog service stopped messages

macOS Analytic 0063

Use of launchctl to stop services or kill critical background processes (e.g., securityd, com.apple.*), typically followed by command-line tools like rm or diskutil. Behavioral chain: Terminal or remote shell + launchctl bootout/disable + process termination + follow-on modification.

  • macos:unifiedlog launchctl disable or bootout calls
  • auditd:SYSCALL execve of launchctl or pkill

ESXi Analytic 0064

Attacker disables VM-related services or stops VMs forcibly to target vmdk or logs. Behavioral chain: esxcli or vim-cmd stop + audit log showing user privilege use + datastore file manipulation.

  • esxi:hostd Stop VM or disable service events via vim-cmd
  • esxi:hostd Log entries indicating VM powered off or forcibly terminated

Wazuh Core Ruleset

25 rules · 22 families
Detection Severity Format
MS-DHCP: A lease request could not be satisfied because the scope's address pool was exhausted. High Wazuh XML
MS-DHCP: Audit log paused. High Wazuh XML
MS-DHCP: The log was temporarily paused due to low disk space. High Wazuh XML
A critical error occurred in an MS DTC component, process terminating. Medium Wazuh XML
An IPsec negotiation with a remote computer failed because the IKE and AuthIP IPsec Keying Modules (IKEEXT) service is not started 2 variants Medium Wazuh XML
An IPsec negotiation with a remote computer failed because the IKE and AuthIP IPsec Keying Modules (IKEEXT) service is not started 2 variants Medium Wazuh XML
IPsec Services encountered a potentially serious failure Medium Wazuh XML
IPsec Services failed to initialize RPC server. IPsec Services could not be started 2 variants Medium Wazuh XML
IPsec Services failed to initialize RPC server. IPsec Services could not be started 2 variants Medium Wazuh XML
IPsec Services was disabled 2 variants Medium Wazuh XML

+ 15 more from Wazuh Core Ruleset → showing the 10 highest-severity

SigmaHQ/sigma

20 rules
Detection Severity Format
Delete All Scheduled Tasks High Sigma
Delete Important Scheduled Task High Sigma
Disable Important Scheduled Task High Sigma
Important Scheduled Task Deleted or Disabled High Sigma
Suspicious Windows Service Tampering High Sigma
Azure Application Deleted Medium Sigma
Azure Kubernetes Network Policy Change Medium Sigma
Azure Kubernetes RoleBinding/ClusterRoleBinding Modified and Deleted Medium Sigma
Azure Kubernetes Secret or Config Object Access Medium Sigma
Azure Kubernetes Sensitive Role Access Medium Sigma

+ 10 more from SigmaHQ/sigma → showing the 10 highest-severity

elastic/detection-rules

20 rules
Detection Severity Format
Azure Storage Account Deletions by User High Elastic TOML
Suspicious Termination of ESXI Process High Elastic TOML
Attempt to Disable Auditd Service Medium Elastic TOML
Attempt to Disable IPTables or Firewall Medium Elastic TOML
Attempt to Disable Syslog Service Medium Elastic TOML
Azure Kubernetes Services (AKS) Kubernetes Pods Deleted Medium Elastic TOML
Azure Resource Group Deleted Medium Elastic TOML
Azure Storage Account Deletion by Unusual User Medium Elastic TOML
Elastic Agent Service Terminated Medium Elastic TOML
High Number of Process and/or Service Terminations Medium Elastic TOML

+ 10 more from elastic/detection-rules → showing the 10 highest-severity

splunk/security_content

17 rules
Detection Severity Format
Excessive Attempt To Disable Services Undefined SPL
Linux Auditd Auditd Service Stop Undefined SPL
Linux Auditd Osquery Service Stop Undefined SPL
Linux Auditd Stop Services Undefined SPL
Linux Auditd Sysmon Service Stop Undefined SPL
Linux Disable Services Undefined SPL
Linux Magic SysRq Key Abuse Undefined SPL
Linux Stop Services Undefined SPL
Ollama Abnormal Service Crash Availability Attack Undefined SPL
Windows Excessive Service Stop Attempt Undefined SPL

+ 7 more from splunk/security_content → showing the 10 highest-severity

socfortress/Wazuh-Rules

6 rules
Detection Severity Format
Sysmon - Event 1: Process creation · Kill service process using taskkill (T1489) High Wazuh XML
Sysmon - Event 1: Process creation · Stop service using net.exe (T1489) High Wazuh XML
Sysmon - Event 1: Process creation · Stop service using sc.exe (T1489) High Wazuh XML
Potential service stop attempt using killall and signal (e.g., SIGTERM). Medium Wazuh XML
Potential service stop attempt using kill with pgrep/pidof substitution. Medium Wazuh XML
Potential service stop attempt using pkill with SIGTERM signal. Medium Wazuh XML

panther-labs/panther-analysis

3 rules
Detection Severity Format
Slack EKM Slackbot Unenrolled High Panther Python
Slack App Removed Medium Panther Python
Azure Virtual Machine Deleted Informational Panther Python

Bert-JanP/Hunting-Queries-Detection-Rules

2 rules
Detection Severity Format
MITRE ATT&CK Mapping Undefined KQL
Ransomware Behaviour Kill SQL Processes Undefined KQL

Azure/Azure-Sentinel

1 rule
Detection Severity Format
Workspace deletion activity from an infected device Medium KQL

chronicle/detection-rules

1 rule
Detection Severity Format
gcp_multiple_service_apis_disabled High YARA-L

Detection rules belong to the projects that publish them and remain under their own licenses. This site indexes and links to them; it claims no rights in them.