Try in Splunk Security Cloud


The search looks for a Windows Security Account Manager (SAM) was stopped via command-line. This is consistent with Ryuk infections across a fleet of endpoints.

  • Type: TTP
  • Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
  • Datamodel:
  • Last Updated: 2020-11-06
  • Author: Rod Soto, Jose Hernandez, Splunk
  • ID: 69c12d59-d951-431e-ab77-ec426b8d65e6


ID Technique Tactic
T1489 Service Stop Impact

| tstats `security_content_summariesonly` count min(_time) as firstTime max(_time) as lastTime FROM datamodel=Endpoint.Processes WHERE ("Processes.process_name"="net*.exe" "Processes.process"="*stop \"samss\"*") BY "Processes.dest", "Processes.user", "Processes.process" 
| `drop_dm_object_name(Processes)` 
| `security_content_ctime(lastTime)` 
| `security_content_ctime(firstTime)` 
| `windows_security_account_manager_stopped_filter`

Associated Analytic Story

How To Implement

You must be ingesting data that records the process-system activity from your hosts to populate the Endpoint Processes data-model object. If you are using Sysmon, you will need a Splunk Universal Forwarder on each endpoint from which you want to collect data.

Required field

  • _time
  • Processes.process_name
  • Processes.process
  • Processes.dest
  • Processes.user

Kill Chain Phase

  • Delivery

Known False Positives

SAM is a critical windows service, stopping it would cause major issues on an endpoint this makes false positive rare. AlthoughNo false positives have been identified.


Risk Score Impact Confidence Message
70.0 70 100 The Windows Security Account Manager (SAM) was stopped via cli by $user$ on $dest$ by this command: $processs$


Test Dataset

Replay any dataset to Splunk Enterprise by using our tool or the UI. Alternatively you can replay a dataset into a Splunk Attack Range

source | version: 1