Detection: Correlation by Repository and Risk

DEPRECATED DETECTION

This detection has been marked as deprecated by the Splunk Threat Research team. This means that it will no longer be maintained or supported. If you have any questions or concerns, please reach out to us at research@splunk.com.

Updated Date: 2024-10-17 ID: 8da9fdd9-6a1b-4ae0-8a34-8c25e6be9687 Author: Patrick Bareiss, Splunk Type: Correlation Product: Splunk Enterprise Security

Description

This search has been deprecated and updated with Risk Rule for Dev Sec Ops by Repository detection. The following analytic detects by correlating repository and risk score to identify patterns and trends in the data based on the level of risk associated. The analytic adds any null values and calculates the sum of the risk scores for each detection. Then, the analytic captures the source and user information for each detection and sorts the results in ascending order based on the risk score. Finally, the analytic filters the detections with a risk score below 80 and focuses only on high-risk detections.This detection is important because it provides valuable insights into the distribution of high-risk activities across different repositories. It also identifies the most vulnerable repositories that are frequently targeted by potential threats. Additionally, it proactively detects and responds to potential threats, thereby minimizing the impact of attacks and safeguarding critical assets. Finally, it provides a comprehensive view of the risk landscape and helps to make informed decisions to protect the organization's data and infrastructure. False positives might occur so it is important to identify the impact of the attack and prioritize response and mitigation efforts.

Search

1`risk_index` 
2| fillnull 
3| stats sum(risk_score) as risk_score values(source) as signals values(user) as user by repository 
4| sort - risk_score 
5| where risk_score > 80 
6| `correlation_by_repository_and_risk_filter`

Data Source

No data sources specified for this detection.

Macros Used

Name	Value
risk_index	`index=risk`
correlation_by_repository_and_risk_filter	`search *`

correlation_by_repository_and_risk_filter is an empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.

Annotations

- MITRE ATT&CK

+ Kill Chain Phases

+ NIST

+ CIS

- Threat Actors

ID	Technique	Tactic
T1204.003	Malicious Image	Execution
T1204	User Execution	Execution

KillChainPhase.INSTALLATION

NistCategory.DE_AE

Cis18Value.CIS_13

TeamTNT

LAPSUS$

Scattered Spider

Default Configuration

This detection is configured by default in Splunk Enterprise Security to run with the following settings:

Setting	Value
Disabled	true
Cron Schedule	`0 * * * *`
Earliest Time	`-70m@m`
Latest Time	`-10m@m`
Schedule Window	`auto`
Creates Notable	Yes
Rule Title	`%name%`
Rule Description	`%description%`
Notable Event Fields	user, dest
Creates Risk Event	False

This configuration file applies to all detections of type Correlation. These correlations will generate Notable Events.

Implementation

For Dev Sec Ops POC

Known False Positives

unknown

Associated Analytic Story

Dev Sec Ops

Risk Based Analytics (RBA)

Risk Message	Risk Score	Impact	Confidence
Correlation triggered for user $user$	70	70	100

The Risk Score is calculated by the following formula: Risk Score = (Impact * Confidence/100). Initial Confidence and Impact is set by the analytic author.

Detection Testing

Test Type	Status	Dataset	Source	Sourcetype
Validation	Not Applicable	N/A	N/A	N/A
Unit	❌ Failing	N/A	`N/A`	`N/A`
Integration	❌ Failing	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: 2