ID | Technique | Tactic |
---|---|---|
T1485 | Data Destruction | Impact |
T1195 | Supply Chain Compromise | Initial Access |
Detection: GitHub Organizations Repository Archived
Description
The following analytic detects when a repository is archived in GitHub Organizations. The detection monitors GitHub Organizations audit logs for repository archival events by tracking actor details, repository information, and associated metadata. For a SOC, identifying repository archival is important as it could indicate attempts to make critical code inaccessible or preparation for repository deletion. While archiving is a legitimate feature, unauthorized archival of active repositories could signal account compromise, insider threats, or attempts to disrupt development operations. The impact of unauthorized repository archival includes loss of active development access, disruption to workflows and CI/CD pipelines, and potential business delays if critical repositories are affected. Additionally, archived repositories may be targeted for subsequent deletion, potentially resulting in permanent loss of intellectual property if proper backups are not maintained.
Search
1`github_organizations` vendor_action=repo.archived
2| fillnull
3| stats count min(_time) as firstTime max(_time) as lastTime by actor, actor_id, actor_is_bot, actor_location.country_code, business, business_id, org, org_id, repo, repo_id, user_agent, visibility, vendor_action
4| eval user=actor
5| `security_content_ctime(firstTime)`
6| `security_content_ctime(lastTime)`
7| `github_organizations_repository_archived_filter`
Data Source
Name | Platform | Sourcetype | Source |
---|---|---|---|
GitHub Organizations Audit Logs | N/A | 'github:cloud:audit' |
'github' |
Macros Used
Name | Value |
---|---|
github_organizations | sourcetype=github:cloud:audit |
github_organizations_repository_archived_filter | search * |
github_organizations_repository_archived_filter
is an empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
Annotations
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 Risk Event | True |
Implementation
You must ingest GitHub Organizations logs using Splunk Add-on for Github using a Personal Access Token https://docs.splunk.com/Documentation/AddOns/released/GitHub/Configureinputs .
Known False Positives
unknown
Associated Analytic Story
Risk Based Analytics (RBA)
Risk Message:
$user$ archived a repository in GitHub Organizations
Risk Object | Risk Object Type | Risk Score | Threat Objects |
---|---|---|---|
user | user | 25 | user_agent |
References
Detection Testing
Test Type | Status | Dataset | Source | Sourcetype |
---|---|---|---|---|
Validation | ✅ Passing | N/A | N/A | N/A |
Unit | ✅ Passing | Dataset | github |
github:cloud:audit |
Integration | ✅ Passing | Dataset | github |
github:cloud:audit |
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: 1