mirror of
https://github.com/splunk/security_content
synced 2026-06-08 17:32:49 +00:00
divious1
77 lines
3.2 KiB
JSON
77 lines
3.2 KiB
JSON
{
|
|
"asset_type": "Endpoint",
|
|
"confidence": "medium",
|
|
"creation_date": "2019-02-14",
|
|
"data_metadata": {
|
|
"data_models": [
|
|
"Network_Resolution"
|
|
],
|
|
"data_source": [
|
|
"DNS"
|
|
],
|
|
"providing_technologies": [
|
|
"Splunk Stream",
|
|
"Bro"
|
|
]
|
|
},
|
|
"description": "The search takes the DNS records and their answers results of the discovered_dns_records lookup and finds if any records have changed by searching DNS response from the Network_Resolution datamodel across the last day.",
|
|
"detect": {
|
|
"phantom": {
|
|
"phantom_server": "automation (hostname)",
|
|
"playbook_display_name": "Excessive Account Lockouts Enrichment And Response",
|
|
"playbook_name": "community/excessive_account_lockouts_enrichment_and_response",
|
|
"playbook_url": "https://my.phantom.us/4.1/playbook/excessive-account-lockouts-enrichment-and-response/",
|
|
"sensitivity": "green",
|
|
"severity": "medium"
|
|
}
|
|
},
|
|
"eli5": "Using a lookup `discover_dns_records` generated by support search \"Discover DNS records\" we check previous network traffic and make sure the responses have not changed.",
|
|
"how_to_implement": "To successfully implement this search you will need to ensure that DNS data is populating the `Network_Resolution` data model. It also requires that the `discover_dns_record` lookup table be populated by the included support search \"Discover DNS record\". <br></br> <b>Splunk>Phantom Playbook Integration</b><br></br>If Splunk>Phantom is also configured in your environment, a Playbook called \"DNS Hijack Investigation\" can be configured to run when any results are found by this detection search. The playbook takes in the DNS record changed and uses Geoip, whois, Censys and PassiveTotal to detect if DNS issuers changed. To use this integration, install the Phantom App for Splunk <code>https://splunkbase.splunk.com/app/3411/</code>, add the correct hostname to the \"Phantom Instance\" field in the Adaptive Response Actions when configuring this detection search, and set the corresponding Playbook to active. <br/>(Playbook Link:<code>https://my.phantom.us/4.1/playbook/dns-hijack-investigation/</code>).<br></br>",
|
|
"id": "44d3a43e-dcd5-49f7-8356-5209bb369065",
|
|
"known_false_positives": "Legitimate DNS changes can be detected in this search. Investigate, verify and update the list of provided current answers for the domains in question as appropriate.",
|
|
"maintainers": [
|
|
{
|
|
"company": "Splunk",
|
|
"email": "jhernandez@splunk.com",
|
|
"name": "Jose Hernandez"
|
|
}
|
|
],
|
|
"mappings": {
|
|
"cis20": [
|
|
"CIS 1",
|
|
"CIS 3",
|
|
"CIS 8",
|
|
"CIS 12"
|
|
],
|
|
"kill_chain_phases": [
|
|
"Command and Control"
|
|
],
|
|
"mitre_attack": [
|
|
"Exfiltration",
|
|
"Command and Control",
|
|
"Defense Evasion",
|
|
"Commonly Used Port"
|
|
],
|
|
"nist": [
|
|
"ID.AM",
|
|
"PR.DS",
|
|
"PR.IP",
|
|
"DE.AE",
|
|
"DE.CM"
|
|
]
|
|
},
|
|
"modification_date": "2019-02-14",
|
|
"name": "DNS record changed",
|
|
"original_authors": [
|
|
{
|
|
"company": "Splunk",
|
|
"email": "jhernandez@splunk.com",
|
|
"name": "Jose Hernandez"
|
|
}
|
|
],
|
|
"security_domain": "network",
|
|
"spec_version": 1,
|
|
"type": "splunk",
|
|
"version": "1.0"
|
|
}
|