admin/splunk-security_content
1
0
Fork 0
mirror of https://github.com/splunk/security_content synced 2026-06-08 17:32:49 +00:00
Code Issues Packages Projects Releases Wiki Activity

Revert "Update windows_event_log_cleared.yml"

Browse Source 
This reverts commit 8761bf0f85.
This commit is contained in:
mhaag-spl
2021-09-21 09:15:56 -06:00
parent c9b15f05c8
commit 71a9bed8f4
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
detections/endpoint/windows_event_log_cleared.yml
+2 -2
View File
@@ -11,9 +11,9 @@ description: The following analytic utilizes Windows Security Event ID 1102 or S
triage, based on time of day and user, determine if this was planned. If not planned,
follow through with reviewing parallel alerts and other data sources to determine
what else may have occurred.
search: '(`wineventlog_security` EventCode=1102) OR (`wineventlog_system` EventCode=104)
search: (`wineventlog_security` EventCode=1102) OR (`wineventlog_system` EventCode=104)
| stats count min(_time) as firstTime max(_time) as lastTime by dest Message EventCode
| `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)` | `windows_event_log_cleared_filter`'
| `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)` | `windows_event_log_cleared_filter`
how_to_implement: To successfully implement this search, you need to be ingesting
Windows event logs from your hosts. In addition, the Splunk Windows TA is needed.
known_false_positives: It is possible that these logs may be legitimately cleared