Files
splunk-security_content/detections/shim_database_installation.yml
2019-12-11 15:14:49 -05:00

108 lines
3.7 KiB
YAML

asset_type: Endpoint
confidence: medium
creation_date: '2017-10-03'
data_metadata:
data_models:
- Endpoint
data_source:
- Endpoint Intel
providing_technologies:
- Carbon Black Response
- CrowdStrike Falcon
- Sysmon
- Tanium
- Ziften
description: This search detects the process execution and arguments required to silently
create a shim database. The sdbinst.exe application is used to install shim database
files (.sdb). A shim is a small library which transparently intercepts an API, changes
the parameters passed, handles the operation itself, or redirects the operation
elsewhere.
detect:
splunk:
correlation_rule:
notable:
nes_fields: dest, user, process
rule_description: The system $dest$ had a shim database installed.
rule_title: Shim Database Installation on $dest$
risk:
risk_object: dest
risk_object_type:
- system
risk_score: 20
schedule:
cron_schedule: 0 * * * *
earliest_time: -70m@m
latest_time: -10m@m
search: '| tstats `security_content_summariesonly` values(Processes.process) as process min(_time)
as firstTime max(_time) as lastTime from datamodel=Endpoint.Processes where
Processes.process_name = sdbinst.exe Processes.process="*-p*" Processes.process="*-q*"
by Processes.process_name Processes.parent_process_name Processes.dest Processes.user
| `drop_dm_object_name(Processes)` | `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)`'
suppress:
suppress_fields: dest,user
suppress_period: 14400s
eli5: This search looks for the execution of sdbinst.exe with command-line arguments
of -q and -p. The -q option performs a silent installation with no visible window,
status, or warning information. The -p option allows the shim database to contain
patches. It will return the count, the first time, and the last time these command-line
arguments were seen on each endpoint and by each user.
entities:
- dest
how_to_implement: You must be ingesting data that records process activity from your
hosts to populate the Endpoint data model in the Processes node. You must also be
ingesting logs with both the process name and command line from your endpoints.
The command-line arguments are mapped to the "process" field in the Endpoint data
model.
id: 404620de-46d8-48b6-90cc-8a8d7b0876a3
investigations:
- id: bc91a8cf-35e7-4bb2-8140-e756cc06fd76
name: Get Authentication Logs For Endpoint
type: splunk
- id: fecf2918-670d-4f1c-872b-3d7317a41bf9
name: Get Parent Process Info
type: splunk
- id: fdcfb369-1725-4c24-824a-22972d7f0d55
name: Get Risk Modifiers For User
type: splunk
- id: bc91a8cf-35e7-4bb2-8140-e756cc06fd71
name: Get Process Info
type: splunk
- id: 3d6c3213-5fff-4a1e-b57d-b24c262171e7
name: Get Notable History
type: splunk
- id: f3fb4d1b-5f33-4b01-b541-c7af9534c242
name: Get Notable Info
type: splunk
- id: fdcfb369-1725-4c24-824a-22972d7f0d65
name: Get Risk Modifiers For Endpoint
type: splunk
- id: bc91a8cf-35e7-4bb2-8140-e756cc06fd74
name: Get User Information from Identity Table
type: splunk
known_false_positives: None identified
maintainers:
- company: Splunk
email: davidd@splunk.com
name: David Dorsey
mappings:
cis20:
- CIS 8
kill_chain_phases:
- Actions on Objectives
mitre_attack:
- Persistence
- Application Shimming
nist:
- DE.CM
modification_date: '2019-03-01'
name: Shim Database Installation With Suspicious Parameters
original_authors:
- company: Splunk
email: davidd@splunk.com
name: David Dorsey
references: []
security_domain: endpoint
spec_version: 2
type: splunk
version: '2.0'