Files
splunk-security_content/detections/prohibited_apps_spawning_cmdprompt.json
2019-03-27 11:13:11 -04:00

87 lines
3.6 KiB
JSON

{
"asset_type": "Endpoint",
"channel": "ESCU",
"confidence": "medium",
"correlation_rule": {
"notable": {
"nes_fields": "dest, process, parent_process",
"rule_description": "A prohibited application from prohibited_apps_launching_cmd.csv was leveraged to launch cmd.exe",
"rule_title": "Prohibited application($parent_process$) used to launch cmd.exe on $dest$"
},
"risk": {
"risk_object": "dest",
"risk_object_type": [
"system"
],
"risk_score": 80
},
"suppress": {
"suppress_fields": "dest, parent_process",
"suppress_period": "86400s"
}
},
"creation_date": "2017-10-07",
"data_metadata": {
"data_models": [
"Endpoint"
],
"data_source": [
"Endpoint Intel"
],
"providing_technologies": [
"Carbon Black Response",
"CrowdStrike Falcon",
"Sysmon",
"Tanium",
"Ziften"
]
},
"eli5": "Obtaining access to the Command-Line Interface (CLI) is typically a primary attacker goal. Once an attacker has obtained the ability to execute code on a target system, they will often further manipulate the system via commands passed to the CLI. It is also unusual for many applications to spawn a command shell during normal operation, while it is often observed if an application has been compromised in some way. As such, it is often beneficial to look for cmd.exe being executed by processes that are often targeted for exploitation, or that would not spawn cmd.exe in any other circumstances. A lookup file is provided to easily modify the processes that are being watched for execution of cmd.exe.",
"how_to_implement": "You must be ingesting data that records process activity from your hosts and populates the Endpoint data model with the resultant dataset. This search includes a lookup file, <code>prohibited_apps_launching_cmd.csv</code>, that contains a list of processes that should not be spawning cmd.exe. You can modify this lookup to better suit your environment.",
"known_false_positives": "There are circumstances where an application may legitimately execute and interact with the Windows command-line interface. Investigate and modify the lookup file, as appropriate.",
"maintainers": [
{
"company": "Splunk",
"email": "bpatel@splunk.com",
"name": "Bhavin Patel"
}
],
"mappings": {
"cis20": [
"CIS 8"
],
"kill_chain_phases": [
"Exploitation"
],
"mitre_attack": [
"Execution",
"Command-Line Interface"
],
"nist": [
"PR.PT",
"DE.CM"
]
},
"modification_date": "2018-11-15",
"original_authors": [
{
"company": "Splunk",
"email": "bpatel@splunk.com",
"name": "Bhavin Patel"
}
],
"scheduling": {
"cron_schedule": "0 * * * *",
"earliest_time": "-70m@m",
"latest_time": "-10m@m"
},
"search": "| tstats `summariesonly` count values(Processes.user) as user values(Processes.process) as process min(_time) as firstTime max(_time) as lastTime from datamodel=Endpoint.Processes where Processes.process_name=cmd.exe by Processes.parent_process_name Processes.process_name Processes.dest | `drop_dm_object_name(Processes)` | `ctime(firstTime)`| `ctime(lastTime)` |search [`prohibited_apps_launching_cmd`]",
"search_description": "This search looks for executions of cmd.exe spawned by a process that is often abused by attackers and that does not typically launch cmd.exe.",
"search_id": "dcfd6b40-42f9-469d-a433-2e53f7486664",
"search_name": "Detect Prohibited Applications Spawning cmd.exe",
"search_type": "detection",
"security_domain": "endpoint",
"spec_version": 1,
"version": "2.0"
}