| ID | Technique | Tactic |
|---|
Detection: Attempt To Add Certificate To Untrusted Store
REMOVED DETECTION
This detection has been removed from the Splunk Threat Research content library and is no longer maintained or supported.
Reason: Detection is deprecated as the usage of certutil and addstore by itself is not malicious.
Removed in version: 6.1.0
If you have any questions or concerns, please reach out to us at research@splunk.com.
Description
The following analytic detects attempts to add a certificate to the untrusted
certificate store using the 'certutil -addstore' command.
It leverages process activity and command-line arguments from Endpoint Detection and Response (EDR) logs mapped to the Splunk Processes data model.
This activity is significant as it may indicate an attacker trying to disable security tools to gain unauthorized access.
If confirmed malicious, this could lead to the compromise of system security, allowing attackers
to bypass defenses and potentially escalate privileges or persist in the environment.
Search
1
2| tstats `security_content_summariesonly` count min(_time) as firstTime values(Processes.process) as process max(_time) as lastTime FROM datamodel=Endpoint.Processes
3 WHERE `process_certutil` (Processes.process=*-addstore*)
4 BY Processes.action Processes.dest Processes.original_file_name
5 Processes.parent_process Processes.parent_process_exec Processes.parent_process_guid
6 Processes.parent_process_id Processes.parent_process_name Processes.parent_process_path
7 Processes.process Processes.process_exec Processes.process_guid
8 Processes.process_hash Processes.process_id Processes.process_integrity_level
9 Processes.process_name Processes.process_path Processes.user
10 Processes.user_id Processes.vendor_product
11
12| `drop_dm_object_name("Processes")`
13
14| `security_content_ctime(firstTime)`
15
16| `security_content_ctime(lastTime)`
17
18| `attempt_to_add_certificate_to_untrusted_store_filter`
Data Source
| Name | Platform | Sourcetype | Source |
|---|---|---|---|
| Sysmon EventID 1 | 'XmlWinEventLog' |
'XmlWinEventLog:Microsoft-Windows-Sysmon/Operational' |
|
| Windows Event Log Security 4688 | 'XmlWinEventLog' |
'XmlWinEventLog:Security' |
|
| CrowdStrike ProcessRollup2 | Other | 'crowdstrike:events:sensor' |
'crowdstrike' |
Macros Used
| Name | Value |
|---|---|
| security_content_summariesonly | summariesonly=summariesonly_config allow_old_summaries=oldsummaries_config fillnull_value=fillnull_config`` |
| attempt_to_add_certificate_to_untrusted_store_filter | `` |
attempt_to_add_certificate_to_untrusted_store_filter is an empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
Annotations
Default Configuration
This detection is configured by default in Splunk Enterprise Security to run with the following settings:
| Setting | Value |
|---|---|
| Disabled | true |
| Cron Schedule | N/A |
| Earliest Time | N/A |
| Latest Time | N/A |
| Schedule Window | N/A |
| Creates Finding (Notable) | No |
| Creates Intermediate Finding (Risk Event) | No |
Implementation
The detection is based on data that originates from Endpoint Detection and Response (EDR) agents. These agents are designed to provide security-related telemetry from the endpoints where the agent is installed. To implement this search, you must ingest logs that contain the process GUID, process name, and parent process. Additionally, you must ingest complete command-line executions. These logs must be processed using the appropriate Splunk Technology Add-ons that are specific to the EDR product. The logs must also be mapped to the Processes node of the Endpoint data model. Use the Splunk Common Information Model (CIM) to normalize the field names and speed up the data modeling process.
Known False Positives
There may be legitimate reasons for administrators to add a certificate to the untrusted certificate store. In such cases, this will typically be done on a large number of systems.
Associated Analytic Story
No associated analytic story
References
Detection Testing
| Test Type | Status | Dataset | Source | Sourcetype |
|---|---|---|---|---|
| Validation | Not Applicable | N/A | N/A | N/A |
| Unit | Not Applicable | N/A | N/A |
N/A |
| Integration | Not Applicable | 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: 20