Detection: Add Prohibited Processes to Enterprise Security

REMOVED DETECTION

This detection has been removed from the Splunk Threat Research content library and is no longer maintained or supported.

Reason: All detection(s) which leverage this baseline have been deprecated. As such, this baseline has been deprecated as well.

Removed in version: 5.2.0

If you have any questions or concerns, please reach out to us at research@splunk.com.

Updated Date: 2026-05-13 ID: 251930a5-1451-4428-bb13-eed5775be0ce Author: David Dorsey, Splunk Type: Baseline Product: Splunk Enterprise Security

Description

This search takes the existing interesting process table from ES, filters out any existing additions added by ESCU and then updates the table with processes identified by ESCU that should be prohibited on your endpoints.

Search

1
2| inputlookup prohibited_processes 
3| search note!=ESCU* 
4| inputlookup append=T prohibited_processes 
5| fillnull value=* dest dest_pci_domain 
6| fillnull value=false is_required is_secure 
7| fillnull value=true is_prohibited 
8| outputlookup prohibited_processes 
9| stats count

Data Source

No data sources specified for this detection.

Macros Used

Name	Value

Annotations

- MITRE ATT&CK

+ Kill Chain Phases

+ NIST

+ CIS

- Threat Actors

ID	Technique	Tactic

Default Configuration

This detection is configured by default in Splunk Enterprise Security to run with the following settings:

Setting	Value
Disabled	true
Cron Schedule	`N/A`
Earliest Time	`N/A`
Latest Time	`N/A`
Schedule Window	`N/A`
Creates Finding (Notable)	No
Creates Intermediate Finding (Risk Event)	No

Implementation

This search should be run on each new install of ESCU.

Known False Positives

none

Associated Analytic Story

Detection Testing

Test Type	Status	Dataset	Source	Sourcetype
Validation	Not Applicable	N/A	N/A	N/A
Unit	Not Applicable	N/A	`N/A`	`N/A`
Integration	Not Applicable	N/A	`N/A`	`N/A`

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

Source: GitHub |

Version: 1