Detection: Monitor DNS For Brand Abuse

DEPRECATED DETECTION

This detection has been marked as deprecated by the Splunk Threat Research team. This means that it will no longer be maintained or supported. If you have any questions or concerns, please reach out to us at research@splunk.com.

Updated Date: 2024-10-17 ID: 24dd17b1-e2fb-4c31-878c-d4f746595bfa Author: David Dorsey, Splunk Type: TTP Product: Splunk Enterprise Security

Description

This search looks for DNS requests for faux domains similar to the domains that you want to have monitored for abuse.

Search

1
2| tstats `security_content_summariesonly` values(DNS.answer) as IPs min(_time) as firstTime from datamodel=Network_Resolution by DNS.src, DNS.query 
3| `drop_dm_object_name("DNS")` 
4| `security_content_ctime(firstTime)`
5| `brand_abuse_dns` 
6| `monitor_dns_for_brand_abuse_filter`

Data Source

No data sources specified for this detection.

Macros Used

Name	Value
brand_abuse_dns	`lookup update=true brandMonitoring_lookup domain as query OUTPUT domain_abuse
monitor_dns_for_brand_abuse_filter	`search *`

monitor_dns_for_brand_abuse_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

NistCategory.DE_CM

Cis18Value.CIS_13

Default Configuration

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

Setting	Value
Disabled	true
Cron Schedule	`0 * * * *`
Earliest Time	`-70m@m`
Latest Time	`-10m@m`
Schedule Window	`auto`
Creates Notable	Yes
Rule Title	`%name%`
Rule Description	`%description%`
Notable Event Fields	user, dest
Creates Risk Event	True

This configuration file applies to all detections of type TTP. These detections will use Risk Based Alerting and generate Notable Events.

Implementation

You need to ingest data from your DNS logs. Specifically you must ingest the domain that is being queried and the IP of the host originating the request. Ideally, you should also be ingesting the answer to the query and the query type. This approach allows you to also create your own localized passive DNS capability which can aid you in future investigations. You also need to have run the search "ESCU - DNSTwist Domain Names", which creates the permutations of the domain that will be checked for. You also need the dnstwist custom command.

Known False Positives

None at this time

Associated Analytic Story

Brand Monitoring

Risk Based Analytics (RBA)

Risk Message	Risk Score	Impact	Confidence
tbd	25	50	50

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

Detection Testing

Test Type	Status	Dataset	Source	Sourcetype
Validation	Not Applicable	N/A	N/A	N/A
Unit	❌ Failing	N/A	`N/A`	`N/A`
Integration	❌ Failing	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: 3