This search correlations detections by repository and risk_score
- Type: Correlation
Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
- Last Updated: 2021-09-06
- Author: Patrick Bareiss, Splunk
- ID: 8da9fdd9-6a1b-4ae0-8a34-8c25e6be9687
Kill Chain Phase
- Actions on Objectives
- CIS 13
1 2 3 4 5 6 `signals` | fillnull | stats sum(risk_score) as risk_score values(source) as signals values(user) as user by repository | sort - risk_score | where risk_score > 80 | `correlation_by_repository_and_risk_filter`
The SPL above uses the following Macros:
correlation_by_repository_and_risk_filter is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
List of fields required to use this analytic.
How To Implement
For Dev Sec Ops POC
Known False Positives
Associated Analytic Story
|70.0||70||100||Correlation triggered for user $user$|
The Risk Score is calculated by the following formula: Risk Score = (Impact * Confidence/100). Initial Confidence and Impact is set by the analytic author.
source | version: 1