Files
splunk-security_content/docs/_posts/2021-09-01-github_commit_in_develop.md
T
2021-09-17 12:50:23 -04:00

2.7 KiB

title, excerpt, categories, last_modified_at, toc, tags
title excerpt categories last_modified_at toc tags
Github Commit In Develop Trusted Relationship
Cloud
2021-09-01 true
Anomaly
T1199
Trusted Relationship
Initial Access
Splunk Enterprise
Splunk Enterprise Security
Splunk Cloud
Exploitation

Description

This search is to detect a pushed or commit to develop branch. This is to avoid unwanted modification to develop without a review to the changes. Ideally in terms of devsecops the changes made in a branch and do a PR for review. of course in some cases admin of the project may did a changes directly to master branch

  • Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
  • Datamodel:
  • Last Updated: 2021-09-01
  • Author: Teoderick Contreras, Splunk

ATT&CK

| ID | Technique | Tactic | | ----------- | ----------- |--------------|| T1199 | Trusted Relationship | Initial Access |

`github` branches{}.name = main OR branches{}.name = develop 
|  stats count min(_time) as firstTime max(_time) as lastTime  by commit.author.html_url commit.commit.author.email commit.author.login commit.commit.message repository.pushed_at commit.commit.committer.date 
| `security_content_ctime(firstTime)` 
| `security_content_ctime(lastTime)` 
| `github_commit_in_develop_filter`

Associated Analytic Story

How To Implement

To successfully implement this search, you need to be ingesting logs related to github logs having the fork, commit, push metadata that can be use to monitor the changes in a github project.

Required field

  • _time

Kill Chain Phase

  • Exploitation

Known False Positives

admin can do changes directly to develop branch

RBA

Risk Score Impact Confidence
9.0 30 30

Reference

Test Dataset

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

version: 1