Github Commit In Develop

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:
ATT&CK: T1199
Last Updated: 2021-09-01
Author: Teoderick Contreras, Splunk

ATT&CK

ID	Technique	Tactic
T1199	Trusted Relationship	Initial Access

Search

`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

DevSecOps

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

https://www.redhat.com/en/topics/devops/what-is-devsecops

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

https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1199/github_push_master/github_push_develop.json

version: 1

#############
# Automatically generated by doc_gen.py in https://github.com/splunk/security_content''
# On Date: 2021-09-17 11:18:22.076192 UTC''
# Author: Splunk Security Research''
# Contact: research@splunk.com''
#############

3.0 KiB Raw Blame History