Detection: HTTP Suspicious Tool User Agent

REMOVED DETECTION

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

Reason: Detection has been renamed for clarity

Removed in version: 5.22.0

Replacement: HTTP Scripting Tool User Agent

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

Description

This Splunk query analyzes web access logs to identify and categorize non-browser user agents, detecting various types of security tools, scripting languages, automation frameworks, and suspicious patterns. This activity can signify malicious actors attempting to interact with web endpoints in non-standard ways.

 1`nginx_access_logs` 
 2| eval http_user_agent = lower(http_user_agent) 
 3| `security_content_ctime(firstTime)` 
 4| `security_content_ctime(lastTime)` 
 5| `drop_dm_object_name(Web)` 
 6| lookup scripting_tools_user_agents tool_user_agent AS http_user_agent OUTPUT tool 
 7| where isnotnull(tool) 
 8| rename dest_ip as dest 
 9| stats count min(firstTime) as first_seen max(lastTime) as last_seen values(tool) as tool by http_user_agent dest src_ip status 
10| `http_suspicious_tool_user_agent_filter`

Data Source

Name Platform Sourcetype Source
Nginx Access Other 'nginx:plus:kv' '/var/log/nginx/access.log'

Macros Used

Name Value
nginx_access_logs (sourcetype="nginx:plus:kv" OR sourcetype="nginx:plus:access")
http_suspicious_tool_user_agent_filter ``
http_suspicious_tool_user_agent_filter is an empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.

Annotations

- MITRE ATT&CK
+ Kill Chain Phases
+ NIST
+ CIS
- Threat Actors
ID Technique Tactic
T1071.001 Web Protocols Command and Control

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
Anomaly detections generate Intermediate Findings (Risk Events). They do not generate a Finding (Notable) directly.

Implementation

This analytic necessitates the collection of web data, which can be achieved through Splunk Stream or by utilizing the Splunk Add-on for Apache Web Server. No additional configuration is required for this analytic.

Known False Positives

False positives may be present if the activity is part of diagnostics or testing. Filter as needed.

Associated Analytic Story

References

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: 2