Machine Learning Detected a DNS Request Predicted to be a DGA Domain

 1[metadata]
 2creation_date = "2023/09/14"
 3integration = ["dga", "endpoint", "network_traffic"]
 4maturity = "production"
 5updated_date = "2024/05/21"
 6
 7[rule]
 8author = ["Elastic"]
 9description = """
10A supervised machine learning model has identified a DNS question name that is predicted to be the result of a Domain
11Generation Algorithm (DGA), which could indicate command and control network activity.
12"""
13from = "now-10m"
14index = ["logs-endpoint.events.*", "logs-network_traffic.*"]
15language = "kuery"
16license = "Elastic License v2"
17name = "Machine Learning Detected a DNS Request Predicted to be a DGA Domain"
18references = [
19    "https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html",
20    "https://docs.elastic.co/en/integrations/dga",
21    "https://www.elastic.co/security-labs/detect-domain-generation-algorithm-activity-with-new-kibana-integration",
22]
23risk_score = 21
24rule_id = "f3403393-1fd9-4686-8f6e-596c58bc00b4"
25setup = """## Setup
26
27The rule requires the Domain Generation Algorithm (DGA) Detection integration assets to be installed, as well as DNS events collected by integrations such as Elastic Defend, Network Packet Capture, or Packetbeat.  
28
29### DGA Detection Setup
30The DGA Detection integration consists of an ML-based framework to detect DGA activity in DNS events.
31
32#### Prerequisite Requirements:
33- Fleet is required for DGA Detection.
34- To configure Fleet Server refer to the [documentation](https://www.elastic.co/guide/en/fleet/current/fleet-server.html).
35- DNS events collected by the [Elastic Defend](https://docs.elastic.co/en/integrations/endpoint), [Network Packet Capture](https://docs.elastic.co/integrations/network_traffic) integration, or [Packetbeat](https://www.elastic.co/guide/en/beats/packetbeat/current/packetbeat-overview.html).
36- To install Elastic Defend, refer to the [documentation](https://www.elastic.co/guide/en/security/current/install-endpoint.html).
37- To add the Network Packet Capture integration to an Elastic Agent policy, refer to [this](https://www.elastic.co/guide/en/fleet/current/add-integration-to-policy.html) guide.
38- To set up and run Packetbeat, follow [this](https://www.elastic.co/guide/en/beats/packetbeat/current/setting-up-and-running.html) guide.
39
40#### The following steps should be executed to install assets associated with the DGA Detection integration:
41- Go to the Kibana homepage. Under Management, click Integrations.
42- In the query bar, search for Domain Generation Algorithm Detection and select the integration to see more details about it.
43- Follow the instructions under the **Installation** section.
44- For this rule to work, complete the instructions through **Configure the ingest pipeline**.
45"""
46severity = "low"
47tags = [
48    "Domain: Network",
49    "Domain: Endpoint",
50    "Data Source: Elastic Defend",
51    "Use Case: Domain Generation Algorithm Detection",
52    "Rule Type: ML",
53    "Rule Type: Machine Learning",
54    "Tactic: Command and Control",
55]
56timestamp_override = "event.ingested"
57type = "query"
58
59query = '''
60ml_is_dga.malicious_prediction:1 and not dns.question.registered_domain:avsvmcloud.com
61'''
62
63
64[[rule.threat]]
65framework = "MITRE ATT&CK"
66[[rule.threat.technique]]
67id = "T1568"
68name = "Dynamic Resolution"
69reference = "https://attack.mitre.org/techniques/T1568/"
70[[rule.threat.technique.subtechnique]]
71id = "T1568.002"
72name = "Domain Generation Algorithms"
73reference = "https://attack.mitre.org/techniques/T1568/002/"
74
75
76
77[rule.threat.tactic]
78id = "TA0011"
79name = "Command and Control"
80reference = "https://attack.mitre.org/tactics/TA0011/"