| ID | Technique | Tactic |
|---|---|---|
| T1071.001 | Web Protocols | Command and Control |
Detection: Detect web traffic to dynamic domain providers
REMOVED DETECTION
This detection has been removed from the Splunk Threat Research content library and is no longer maintained or supported.
Reason: Updated to use a different log source
Removed in version: 5.2.0
Replacement: Detect hosts connecting to dynamic domain providers
If you have any questions or concerns, please reach out to us at research@splunk.com.
Description
This search looks for web connections to dynamic DNS providers.
Search
1
2| tstats `security_content_summariesonly` count values(Web.url) as url min(_time) as firstTime from datamodel=Web where Web.status=200 by Web.src Web.dest Web.status
3| `drop_dm_object_name(Web)`
4| `security_content_ctime(firstTime)`
5| `dynamic_dns_web_traffic`
6| `detect_web_traffic_to_dynamic_domain_providers_filter`
Data Source
No data sources specified for this detection.
Macros Used
| Name | Value |
|---|---|
| security_content_summariesonly | summariesonly=summariesonly_config allow_old_summaries=oldsummaries_config fillnull_value=fillnull_config`` |
| detect_web_traffic_to_dynamic_domain_providers_filter | `` |
detect_web_traffic_to_dynamic_domain_providers_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
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 |
TTP detections generate a Finding (Notable) and may generate Intermediate Findings (Risk Events) for associated entities.
Implementation
This search requires you to be ingesting web-traffic logs. You can obtain these logs from indexing data from a web proxy or by using a network-traffic-analysis tool, such as Bro or Splunk Stream. The web data model must contain the URL being requested, the IP address of the host initiating the request, and the destination IP. This search also leverages a lookup file, dynamic_dns_providers_default.csv, which contains a non-exhaustive list of dynamic DNS providers. Consider periodically updating this local lookup file with new domains.
This search produces fields (isDynDNS) that are not yet supported by ES Incident Review and therefore cannot be viewed when a finding event is raised. These fields contribute additional context to the finding. To see the additional metadata, add the following fields, if not already present, to Incident Review - Event Attributes (Configure > Incident Management > Incident Review Settings > Add New Entry):
- Label: IsDynamicDNS, Field: isDynDNS Deprecated because duplicate.
Known False Positives
It is possible that list of dynamic DNS providers is outdated and/or that the URL being requested is legitimate.
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: 6