splunk-security_content/docs/_posts/2019-04-01-web_servers_executing_suspicious_processes.md

title, excerpt, categories, last_modified_at, toc, toc_label, tags

title	excerpt	categories	last_modified_at	toc	toc_label	tags
Web Servers Executing Suspicious Processes	System Information Discovery	Application	2019-04-01	true		System Information Discovery Discovery Splunk Enterprise Splunk Enterprise Security Splunk Cloud Endpoint

⚠️ WARNING THIS IS A EXPERIMENTAL analytic

We have not been able to test, simulate, or build datasets for this object. Use at your own risk. This analytic is NOT supported.

Try in Splunk Security Cloud{: .btn .btn--success}

Description

This search looks for suspicious processes on all systems labeled as web servers.

• Type: TTP
• Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
• Datamodel: Endpoint
• Last Updated: 2019-04-01
• Author: David Dorsey, Splunk
• ID: ec3b7601-689a-4463-94e0-c9f45638efb9

Annotations

ATT&CK

ID	Technique	Tactic
T1082	System Information Discovery	Discovery

Kill Chain Phase

• Actions on Objectives

NIST

• PR.IP

CIS20

• CIS 3

CVE

Search

| tstats `security_content_summariesonly` count min(_time) as firstTime max(_time) as lastTime from datamodel=Endpoint.Processes where Processes.dest_category="web_server" AND (Processes.process="*whoami*" OR Processes.process="*ping*" OR Processes.process="*iptables*" OR Processes.process="*wget*" OR Processes.process="*service*" OR Processes.process="*curl*") by Processes.process Processes.process_name, Processes.dest Processes.user
| `drop_dm_object_name(Processes)` 
| `security_content_ctime(firstTime)` 
| `security_content_ctime(lastTime)` 
| `web_servers_executing_suspicious_processes_filter`

Macros

The SPL above uses the following Macros:

• security_content_ctime
• security_content_summariesonly

ℹ️ web_servers_executing_suspicious_processes_filter is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.

Required field

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

How To Implement

You must be ingesting data that records process activity from your hosts to populate the Endpoint data model in the Processes node. You must also be ingesting logs with both the process name and command line from your endpoints. The command-line arguments are mapped to the "process" field in the Endpoint data model. In addition, web servers will need to be identified in the Assets and Identity Framework of Enterprise Security.

Known False Positives

Some of these processes may be used legitimately on web servers during maintenance or other administrative tasks.

Associated Analytic story

• Apache Struts Vulnerability

RBA

Risk Score	Impact	Confidence	Message
25.0	50	50	tbd

ℹ️ The Risk Score is calculated by the following formula: Risk Score = (Impact * Confidence/100). Initial Confidence and Impact is set by the analytic author.

Reference

Test Dataset

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 | version: 1