mirror of
https://github.com/splunk/security_content
synced 2026-06-08 17:32:49 +00:00
Branch was auto-updated.
This commit is contained in:
+6
-1
@@ -340,7 +340,6 @@ def generate_doc_detections(REPO_PATH, OUTPUT_DIR, TEMPLATE_PATH, attack, messag
|
||||
for macro in detection_yaml['macros']:
|
||||
if 'lookups' in macro:
|
||||
for macro_lookup in macro['lookups']:
|
||||
print(macro_lookup)
|
||||
detection_lookups.append(macro_lookup)
|
||||
# now any other search lookups
|
||||
additional_detection_lookups = parse_and_add_lookups(detection_yaml['search'], lookups)
|
||||
@@ -350,6 +349,12 @@ def generate_doc_detections(REPO_PATH, OUTPUT_DIR, TEMPLATE_PATH, attack, messag
|
||||
detection_yaml['lookups'] = detection_lookups
|
||||
detection_yaml['lookups'] = detection_lookups
|
||||
|
||||
# sort macros and lookups
|
||||
sorted_macros = sorted(detection_yaml['macros'], key=lambda i: i['name'])
|
||||
detection_yaml['macros'] = sorted_macros
|
||||
sorted_lookups = sorted(detection_yaml['lookups'], key=lambda i: i['name'])
|
||||
detection_yaml['lookups'] = sorted_lookups
|
||||
|
||||
# grab the kind
|
||||
detection_yaml['kind'] = manifest_file.split('/')[-2]
|
||||
|
||||
|
||||
@@ -54,8 +54,8 @@ This search looks for the creation of WMI permanent event subscriptions.
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [wmi](https://github.com/splunk/security_content/blob/develop/macros/wmi.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [wmi](https://github.com/splunk/security_content/blob/develop/macros/wmi.yml)
|
||||
|
||||
Note that `wmi_permanent_event_subscription_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -53,8 +53,8 @@ This search looks for the creation of WMI temporary event subscriptions.
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [wmi](https://github.com/splunk/security_content/blob/develop/macros/wmi.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [wmi](https://github.com/splunk/security_content/blob/develop/macros/wmi.yml)
|
||||
|
||||
Note that `wmi_temporary_event_subscription_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -44,8 +44,8 @@ This search looks for suspicious Java classes that are often used to exploit rem
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [stream_http](https://github.com/splunk/security_content/blob/develop/macros/stream_http.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [stream_http](https://github.com/splunk/security_content/blob/develop/macros/stream_http.yml)
|
||||
|
||||
Note that `suspicious_java_classes_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -53,8 +53,8 @@ This search looks for reading lsass memory consistent with credential dumping.
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
|
||||
Note that `detect_credential_dumping_through_lsass_access_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -54,8 +54,8 @@ This search looks for reading loaded Images unique to credential dumping with Mi
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
|
||||
Note that `detect_mimikatz_using_loaded_images_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -53,8 +53,8 @@ Detect memory dumping of the LSASS process.
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
|
||||
Note that `access_lsass_memory_for_dump_creation_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -53,8 +53,8 @@ Detect remote thread creation into LSASS consistent with credential dumping.
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
|
||||
Note that `create_remote_thread_into_lsass_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -53,8 +53,8 @@ Detect the hands on keyboard behavior of Windows Task Manager creating a process
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
|
||||
Note that `creation_of_lsass_dump_with_taskmgr_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -51,8 +51,8 @@ This search provides information of unauthenticated requests via user agent, and
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [aws_cloudwatchlogs_eks](https://github.com/splunk/security_content/blob/develop/macros/aws_cloudwatchlogs_eks.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
|
||||
Note that `amazon_eks_kubernetes_cluster_scan_detection_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -51,8 +51,8 @@ This search provides detection information on unauthenticated requests against K
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [aws_cloudwatchlogs_eks](https://github.com/splunk/security_content/blob/develop/macros/aws_cloudwatchlogs_eks.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
|
||||
Note that `amazon_eks_kubernetes_pod_scan_detection_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -54,8 +54,8 @@ This search looks for child processes spawned by zoom.exe or zoom.us that has no
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [previously_seen_zoom_child_processes_window](https://github.com/splunk/security_content/blob/develop/macros/previously_seen_zoom_child_processes_window.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [security_content_summariesonly](https://github.com/splunk/security_content/blob/develop/macros/security_content_summariesonly.yml)
|
||||
|
||||
Note that `first_time_seen_child_process_of_zoom_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
@@ -53,8 +53,8 @@ The following analytic utilizes Windows Security Event ID 1102 or System log eve
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [wineventlog_system](https://github.com/splunk/security_content/blob/develop/macros/wineventlog_system.yml)
|
||||
* [wineventlog_security](https://github.com/splunk/security_content/blob/develop/macros/wineventlog_security.yml)
|
||||
* [wineventlog_system](https://github.com/splunk/security_content/blob/develop/macros/wineventlog_system.yml)
|
||||
|
||||
Note that `windows_event_log_cleared_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
+1
-1
@@ -62,8 +62,8 @@ This search detects Okta login failures due to bad credentials for multiple user
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [okta](https://github.com/splunk/security_content/blob/develop/macros/okta.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
|
||||
Note that `multiple_okta_users_with_invalid_credentials_from_the_same_ip_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -60,8 +60,8 @@ Detect failed Okta SSO events
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [okta](https://github.com/splunk/security_content/blob/develop/macros/okta.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
|
||||
Note that `okta_failed_sso_attempts_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -61,8 +61,8 @@ This search detects logins from the same user from different cities in a 24 hour
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [okta](https://github.com/splunk/security_content/blob/develop/macros/okta.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
|
||||
Note that `okta_user_logins_from_multiple_cities_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -57,9 +57,9 @@ This search looks for emails that have attachments with suspicious file extensio
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [suspicious_email_attachments](https://github.com/splunk/security_content/blob/develop/macros/suspicious_email_attachments.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [security_content_summariesonly](https://github.com/splunk/security_content/blob/develop/macros/security_content_summariesonly.yml)
|
||||
* [suspicious_email_attachments](https://github.com/splunk/security_content/blob/develop/macros/suspicious_email_attachments.yml)
|
||||
|
||||
Note that `suspicious_email_attachment_extensions_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
+1
-1
@@ -54,9 +54,9 @@ This search looks for fast execution of processes used for system network config
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [system_network_configuration_discovery_tools](https://github.com/splunk/security_content/blob/develop/macros/system_network_configuration_discovery_tools.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [security_content_summariesonly](https://github.com/splunk/security_content/blob/develop/macros/security_content_summariesonly.yml)
|
||||
* [system_network_configuration_discovery_tools](https://github.com/splunk/security_content/blob/develop/macros/system_network_configuration_discovery_tools.yml)
|
||||
|
||||
Note that `detect_processes_used_for_system_network_configuration_discovery_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -53,8 +53,8 @@ The malware sunburst will load the malicious dll by SolarWinds.BusinessLayerHost
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
|
||||
Note that `sunburst_correlation_dll_and_network_event_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -56,8 +56,8 @@ This search detects the assignment of rights to accesss content from another mai
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [o365_management_activity](https://github.com/splunk/security_content/blob/develop/macros/o365_management_activity.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
|
||||
Note that `o365_suspicious_rights_delegation_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -51,8 +51,8 @@ This search detects when multi factor authentication has been disabled, what ent
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [o365_management_activity](https://github.com/splunk/security_content/blob/develop/macros/o365_management_activity.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
|
||||
Note that `o365_disable_mfa_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -50,8 +50,8 @@ This search detects when an excessive number of authentication failures occur th
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [o365_management_activity](https://github.com/splunk/security_content/blob/develop/macros/o365_management_activity.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
|
||||
Note that `o365_excessive_authentication_failures_alert_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -49,8 +49,8 @@ This search detects when a user has performed an Ediscovery search or exported a
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [o365_management_activity](https://github.com/splunk/security_content/blob/develop/macros/o365_management_activity.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
|
||||
Note that `o365_pst_export_alert_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -57,8 +57,8 @@ This search detects when an admin configured a forwarding rule for multiple mail
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [o365_management_activity](https://github.com/splunk/security_content/blob/develop/macros/o365_management_activity.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
|
||||
Note that `o365_suspicious_admin_email_forwarding_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -57,8 +57,8 @@ This search detects when multiple user configured a forwarding rule to the same
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [o365_management_activity](https://github.com/splunk/security_content/blob/develop/macros/o365_management_activity.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
|
||||
Note that `o365_suspicious_user_email_forwarding_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -53,8 +53,8 @@ This search detects the creation of a new Federation setting by alerting about a
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [o365_management_activity](https://github.com/splunk/security_content/blob/develop/macros/o365_management_activity.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
|
||||
Note that `o365_add_app_role_assignment_grant_user_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -53,8 +53,8 @@ This search detects the creation of a new Federation setting by alerting about a
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [o365_management_activity](https://github.com/splunk/security_content/blob/develop/macros/o365_management_activity.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
|
||||
Note that `o365_added_service_principal_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -52,8 +52,8 @@ This search detects accounts with high number of Single Sign ON (SSO) logon erro
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [o365_management_activity](https://github.com/splunk/security_content/blob/develop/macros/o365_management_activity.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
|
||||
Note that `o365_excessive_sso_logon_errors_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -53,8 +53,8 @@ This search detects the addition of a new Federated domain.
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [o365_management_activity](https://github.com/splunk/security_content/blob/develop/macros/o365_management_activity.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
|
||||
Note that `o365_new_federated_domain_added_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -53,8 +53,8 @@ The following analytic identifies regasm.exe with a network connection to a publ
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
|
||||
Note that `detect_regasm_with_network_connection_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -53,8 +53,8 @@ The following analytic identifies Regsvcs.exe with a network connection to a pub
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
|
||||
Note that `detect_regsvcs_with_network_connection_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -51,8 +51,8 @@ Upon triage, review the process performing the named pipe. If it is explorer.exe
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
|
||||
Note that `cobalt_strike_named_pipes_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -51,8 +51,8 @@ The following analytics identifies a big number of instance of ransomware notes
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
|
||||
Note that `ransomware_notes_bulk_creation_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -50,8 +50,8 @@ This search looks for high frequency of file deletion relative to process name a
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
|
||||
Note that `high_file_deletion_frequency_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -51,8 +51,8 @@ This analytics are designed to indentify a high frequency of process termination
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
|
||||
Note that `high_process_termination_frequency_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -51,8 +51,8 @@ This detection is to identify a suspicious process that tries to delete the proc
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
|
||||
Note that `process_deleting_its_process_file_path_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -50,8 +50,8 @@ Certutil.exe may download a file from a remote destination using `-urlcache`. Th
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [process_certutil](https://github.com/splunk/security_content/blob/develop/macros/process_certutil.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [security_content_summariesonly](https://github.com/splunk/security_content/blob/develop/macros/security_content_summariesonly.yml)
|
||||
|
||||
Note that `certutil_download_with_urlcache_and_split_arguments_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
@@ -50,8 +50,8 @@ Certutil.exe may download a file from a remote destination using `-VerifyCtl`. T
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [process_certutil](https://github.com/splunk/security_content/blob/develop/macros/process_certutil.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [security_content_summariesonly](https://github.com/splunk/security_content/blob/develop/macros/security_content_summariesonly.yml)
|
||||
|
||||
Note that `certutil_download_with_verifyctl_and_split_arguments_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
@@ -50,8 +50,8 @@ CertUtil.exe may be used to `encode` and `decode` a file, including PE and scrip
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [process_certutil](https://github.com/splunk/security_content/blob/develop/macros/process_certutil.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [security_content_summariesonly](https://github.com/splunk/security_content/blob/develop/macros/security_content_summariesonly.yml)
|
||||
|
||||
Note that `certutil_with_decode_argument_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
@@ -53,8 +53,8 @@ this search detects a potential malicious office document that create schedule t
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
|
||||
Note that `office_document_creating_schedule_task_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -53,8 +53,8 @@ this detection was designed to identifies suspicious office documents that using
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
|
||||
Note that `office_document_executing_macro_code_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -50,8 +50,8 @@ this search is designed to detect suspicious powershell process that tries to in
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
|
||||
Note that `powershell_remote_thread_to_known_windows_process_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -53,8 +53,8 @@ this search is designed to detect suspicious wermgr.exe process that tries to co
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
|
||||
Note that `wermgr_process_connecting_to_ip_check_web_services_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -49,8 +49,8 @@ this search is designed to detect potential malicious wermgr.exe process that dr
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
|
||||
Note that `wermgr_process_create_executable_file_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -54,8 +54,8 @@ This search is to detect potential DNS exfiltration using nslookup application.
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
|
||||
Note that `excessive_usage_of_nslookup_app_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -56,8 +56,8 @@ This search is designed to detect high frequency of archive files data exfiltrat
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [stream_http](https://github.com/splunk/security_content/blob/develop/macros/stream_http.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [stream_http](https://github.com/splunk/security_content/blob/develop/macros/stream_http.yml)
|
||||
|
||||
Note that `multiple_archive_files_http_post_traffic_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -53,8 +53,8 @@ This search is to detect potential plain HTTP POST method data exfiltration. Thi
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [stream_http](https://github.com/splunk/security_content/blob/develop/macros/stream_http.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [stream_http](https://github.com/splunk/security_content/blob/develop/macros/stream_http.yml)
|
||||
|
||||
Note that `plain_http_post_exfiltrated_data_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -54,8 +54,8 @@ The following detection identifies the latest behavior utilized by different mal
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [process_bitsadmin](https://github.com/splunk/security_content/blob/develop/macros/process_bitsadmin.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [security_content_summariesonly](https://github.com/splunk/security_content/blob/develop/macros/security_content_summariesonly.yml)
|
||||
|
||||
Note that `office_product_spawning_bitsadmin_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
@@ -54,8 +54,8 @@ The following detection identifies the latest behavior utilized by different mal
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [process_certutil](https://github.com/splunk/security_content/blob/develop/macros/process_certutil.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [security_content_summariesonly](https://github.com/splunk/security_content/blob/develop/macros/security_content_summariesonly.yml)
|
||||
|
||||
Note that `office_product_spawning_certutil_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
@@ -50,8 +50,8 @@ this search is to detect potential trickbot infection through the create/connect
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
|
||||
Note that `trickbot_named_pipe_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -55,8 +55,8 @@ This analytic will detect suspicious driver loaded paths. This technique is comm
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
|
||||
Note that `suspicious_driver_loaded_path_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -55,8 +55,8 @@ This analytic identifies XMRIG coinminer driver installation on the system. The
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
|
||||
Note that `xmrig_driver_loaded_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -49,8 +49,8 @@ The following analytic will identify a suspicious download by the Telegram appli
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
|
||||
Note that `download_files_using_telegram_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -53,8 +53,8 @@ This analytic detects a potential process using COM Object like CMLUA or CMSTPLU
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
|
||||
Note that `cmlua_or_cmstplua_uac_bypass_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -49,8 +49,8 @@ This analytic identifies suspicious modification of registry to deface or change
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
|
||||
Note that `modification_of_wallpaper_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -53,8 +53,8 @@ this search is designed to detect potential malicious process loading COM object
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
|
||||
Note that `wbemprox_com_object_execution_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -59,8 +59,8 @@ Monitor for the creation of new WMI EventFilter, EventConsumer, and FilterToCons
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
|
||||
Note that `detect_wmi_event_subscription_persistence_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -58,8 +58,8 @@ This search is to detect a suspicious excessive usage of sc.exe in a host machin
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
|
||||
Note that `excessive_usage_of_sc_service_utility_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -57,8 +57,8 @@ This search is to detect suspicious loading of dll in specific path relative to
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
|
||||
Note that `spoolsv_suspicious_loaded_modules_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -50,8 +50,8 @@ This analytic identifies a suspicious behavior related to PrintNightmare, or CVE
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
|
||||
Note that `spoolsv_suspicious_process_access_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -56,8 +56,8 @@ The following analytic identifies a `.dll` being written by `spoolsv.exe`. This
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
|
||||
Note that `spoolsv_writing_a_dll_-_sysmon_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -55,8 +55,8 @@ This search is to detect a suspicious loaded unsigned dll by MMC.exe application
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
|
||||
Note that `uac_bypass_mmc_load_unsigned_dll_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -54,8 +54,8 @@ This search is to detect a suspicious mshta.exe process that spawn rundll32 or r
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [process_rundll32](https://github.com/splunk/security_content/blob/develop/macros/process_rundll32.yml)
|
||||
* [process_regsvr32](https://github.com/splunk/security_content/blob/develop/macros/process_regsvr32.yml)
|
||||
* [process_rundll32](https://github.com/splunk/security_content/blob/develop/macros/process_rundll32.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [security_content_summariesonly](https://github.com/splunk/security_content/blob/develop/macros/security_content_summariesonly.yml)
|
||||
|
||||
|
||||
@@ -58,8 +58,8 @@ This search detects newly added IP addresses/CIDR blocks to the list of MFA Trus
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [o365_management_activity](https://github.com/splunk/security_content/blob/develop/macros/o365_management_activity.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
|
||||
Note that `o365_bypass_mfa_via_trusted_ip_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -50,8 +50,8 @@ This analytic identifies the suspicious Remote Thread execution of rundll32.exe
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
|
||||
Note that `rundll32_createremotethread_in_browser_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -53,8 +53,8 @@ This search is to detect a suspicious rundll32.exe process having a http connect
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
|
||||
Note that `rundll32_dnsquery_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -53,8 +53,8 @@ This search is to detect a suspicious rundll32 process that drops executable (.e
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
|
||||
Note that `rundll32_process_creating_exe_dll_files_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -50,8 +50,8 @@ This analytic identifies the suspicious Remote Thread execution of rundll32.exe
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
|
||||
Note that `rundll32_create_remote_thread_to_a_process_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -53,8 +53,8 @@ This search is to detect dropping a suspicious file named as "license.dat
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
|
||||
Note that `drop_icedid_license_dat_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -53,8 +53,8 @@ This search is to detect a suspicious file creation namely passff.tar and cookie
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
|
||||
Note that `icedid_exfiltrated_archived_file_creation_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -49,8 +49,8 @@ This search is to detect a suspicious file creation of sqlite3.dll in %temp% fol
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
|
||||
Note that `sqlite_module_in_temp_folder_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -50,8 +50,8 @@ This search is to detect suspicious process injection in command shell. This tec
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
|
||||
Note that `create_remote_thread_in_shell_application_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -53,8 +53,8 @@ This search is to detect a possible uac bypass using the colorui.dll COM Object.
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
|
||||
Note that `uac_bypass_with_colorui_com_object_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -54,8 +54,8 @@ The following analytic identifies the process - `esentutl.exe` - being used to c
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [process_esentutl](https://github.com/splunk/security_content/blob/develop/macros/process_esentutl.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [security_content_summariesonly](https://github.com/splunk/security_content/blob/develop/macros/security_content_summariesonly.yml)
|
||||
|
||||
Note that `esentutl_sam_copy_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
@@ -57,8 +57,8 @@ This search looks for AWS CloudTrail events from AWS Elastic Container Service (
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [cloudtrail](https://github.com/splunk/security_content/blob/develop/macros/cloudtrail.yml)
|
||||
* [aws_ecr_users](https://github.com/splunk/security_content/blob/develop/macros/aws_ecr_users.yml)
|
||||
* [cloudtrail](https://github.com/splunk/security_content/blob/develop/macros/cloudtrail.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
|
||||
Note that `aws_ecr_container_upload_unknown_user_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
@@ -52,8 +52,8 @@ This search is to detect a pushed or commit to master or main branch. This is to
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [github](https://github.com/splunk/security_content/blob/develop/macros/github.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
|
||||
Note that `github_commit_changes_in_master_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -60,8 +60,8 @@ This search looks for disable security step in CircleCI pipeline.
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [circleci](https://github.com/splunk/security_content/blob/develop/macros/circleci.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
|
||||
Note that `circle_ci_disable_security_step_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -50,8 +50,8 @@ This search is to detect a pushed or commit to develop branch. This is to avoid
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [github](https://github.com/splunk/security_content/blob/develop/macros/github.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
|
||||
Note that `github_commit_in_develop_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -55,8 +55,8 @@ This search looks for Dependabot Alerts in Github logs.
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [github](https://github.com/splunk/security_content/blob/develop/macros/github.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
|
||||
Note that `github_dependabot_alert_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -56,9 +56,9 @@ This search looks for Pull Request from unknown user.
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [github_known_users](https://github.com/splunk/security_content/blob/develop/macros/github_known_users.yml)
|
||||
* [github](https://github.com/splunk/security_content/blob/develop/macros/github.yml)
|
||||
* [github_known_users](https://github.com/splunk/security_content/blob/develop/macros/github_known_users.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
|
||||
Note that `github_pull_request_from_unknown_user_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -56,8 +56,8 @@ This search looks for disable security job in CircleCI pipeline.
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [circleci](https://github.com/splunk/security_content/blob/develop/macros/circleci.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
|
||||
Note that `circle_ci_disable_security_job_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -53,8 +53,8 @@ This analytic is to detect an application try to connect and create ADSI Object
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
|
||||
Note that `schcache_change_by_app_connect_and_create_adsi_object_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -55,8 +55,8 @@ The following detection identifies the module load of mshtml.dll into an Office
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
|
||||
Note that `mshtml_module_load_in_office_product_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -53,8 +53,8 @@ This search is to detect a suspicious MS scripting process such as wscript.exe o
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
|
||||
Note that `ms_scripting_process_loading_ldap_module_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -53,8 +53,8 @@ This search is to detect a suspicious MS scripting process such as wscript.exe o
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
|
||||
Note that `ms_scripting_process_loading_wmi_module_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -54,8 +54,8 @@ Attempt To Add Certificate To Untrusted Store
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [process_certutil](https://github.com/splunk/security_content/blob/develop/macros/process_certutil.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [security_content_summariesonly](https://github.com/splunk/security_content/blob/develop/macros/security_content_summariesonly.yml)
|
||||
|
||||
Note that `attempt_to_add_certificate_to_untrusted_store_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
@@ -51,8 +51,8 @@ The following query identifies Microsoft Background Intelligent Transfer Service
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [process_bitsadmin](https://github.com/splunk/security_content/blob/develop/macros/process_bitsadmin.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [security_content_summariesonly](https://github.com/splunk/security_content/blob/develop/macros/security_content_summariesonly.yml)
|
||||
|
||||
Note that `bits_job_persistence_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
@@ -55,8 +55,8 @@ The following query identifies Microsoft Background Intelligent Transfer Service
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [process_bitsadmin](https://github.com/splunk/security_content/blob/develop/macros/process_bitsadmin.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [security_content_summariesonly](https://github.com/splunk/security_content/blob/develop/macros/security_content_summariesonly.yml)
|
||||
|
||||
Note that `bitsadmin_download_file_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
@@ -54,8 +54,8 @@ This search detects the use of wmic and Powershell to create a shadow copy.
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [process_wmic](https://github.com/splunk/security_content/blob/develop/macros/process_wmic.yml)
|
||||
* [process_powershell](https://github.com/splunk/security_content/blob/develop/macros/process_powershell.yml)
|
||||
* [process_wmic](https://github.com/splunk/security_content/blob/develop/macros/process_wmic.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [security_content_summariesonly](https://github.com/splunk/security_content/blob/develop/macros/security_content_summariesonly.yml)
|
||||
|
||||
|
||||
@@ -54,8 +54,8 @@ This search looks for events where `PsExec.exe` is run with the `accepteula` fla
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [process_psexec](https://github.com/splunk/security_content/blob/develop/macros/process_psexec.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [security_content_summariesonly](https://github.com/splunk/security_content/blob/develop/macros/security_content_summariesonly.yml)
|
||||
|
||||
Note that `detect_psexec_with_accepteula_flag_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
@@ -54,8 +54,8 @@ The following analytic identifies renamed instances of `PsExec.exe` being utiliz
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [process_psexec](https://github.com/splunk/security_content/blob/develop/macros/process_psexec.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [security_content_summariesonly](https://github.com/splunk/security_content/blob/develop/macros/security_content_summariesonly.yml)
|
||||
|
||||
Note that `detect_renamed_psexec_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
@@ -54,8 +54,8 @@ This analytic is to detect a possible abuse of verclsid to execute malicious fil
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [process_verclsid](https://github.com/splunk/security_content/blob/develop/macros/process_verclsid.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [security_content_summariesonly](https://github.com/splunk/security_content/blob/develop/macros/security_content_summariesonly.yml)
|
||||
|
||||
Note that `verclsid_clsid_execution_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
@@ -52,8 +52,8 @@ During triage, review parallel processes for further behavior. In addition, iden
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [process_curl](https://github.com/splunk/security_content/blob/develop/macros/process_curl.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [security_content_summariesonly](https://github.com/splunk/security_content/blob/develop/macros/security_content_summariesonly.yml)
|
||||
|
||||
Note that `windows_curl_download_to_suspicious_path_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
@@ -52,8 +52,8 @@ The following hunting analytic assists with identifying suspicious tasks that ha
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [wineventlog_task_scheduler](https://github.com/splunk/security_content/blob/develop/macros/wineventlog_task_scheduler.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [wineventlog_task_scheduler](https://github.com/splunk/security_content/blob/develop/macros/wineventlog_task_scheduler.yml)
|
||||
|
||||
Note that `winevent_windows_task_scheduler_event_action_started_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -54,8 +54,8 @@ Adversaries may use one of the three methods based on the remote destination and
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [process_curl](https://github.com/splunk/security_content/blob/develop/macros/process_curl.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [security_content_summariesonly](https://github.com/splunk/security_content/blob/develop/macros/security_content_summariesonly.yml)
|
||||
|
||||
Note that `windows_curl_upload_to_remote_destination_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
@@ -54,8 +54,8 @@ this analytic is to detect a suspicious compile before delivery approach of .net
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [process_csc](https://github.com/splunk/security_content/blob/develop/macros/process_csc.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [security_content_summariesonly](https://github.com/splunk/security_content/blob/develop/macros/security_content_summariesonly.yml)
|
||||
|
||||
Note that `csc_net_on_the_fly_compilation_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
@@ -56,8 +56,8 @@ This analytic look for a spawned runas.exe process with a administrator user opt
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [process_runas](https://github.com/splunk/security_content/blob/develop/macros/process_runas.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [security_content_summariesonly](https://github.com/splunk/security_content/blob/develop/macros/security_content_summariesonly.yml)
|
||||
|
||||
Note that `runas_execution_in_commandline_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
@@ -57,8 +57,8 @@ During triage review resulting network connections, file modifications, and para
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
|
||||
Note that `windows_installutil_credential_theft_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -55,8 +55,8 @@ DynamicWrapperX is an ActiveX component that can be used in a script to call Win
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [sysmon](https://github.com/splunk/security_content/blob/develop/macros/sysmon.yml)
|
||||
|
||||
Note that `loading_of_dynwrapx_module_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
|
||||
@@ -50,8 +50,8 @@ This analytic is to detect a suspicious dxdiag.exe process command-line executio
|
||||
|
||||
#### Macros
|
||||
The SPL above uses the following Macros:
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [process_dxdiag](https://github.com/splunk/security_content/blob/develop/macros/process_dxdiag.yml)
|
||||
* [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml)
|
||||
* [security_content_summariesonly](https://github.com/splunk/security_content/blob/develop/macros/security_content_summariesonly.yml)
|
||||
|
||||
Note that `system_info_gathering_using_dxdiag_application_filter` is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user