Cross-source coverage

T1213.003 / ATT&CK

Data from Information Repositories: Code Repositories

12 rules across 3 sources.

From MITRE ATT&CK 19.2

Adversaries may leverage code repositories to collect valuable information. Code repositories are tools/services that store source code and automate software builds. They may be hosted internally or privately on third party sites such as Github, GitLab, SourceForge, and BitBucket. Users typically interact with code repositories through a web application or command-line utilities such as git.

Once adversaries gain access to a victim network or a private code repository, they may collect sensitive information such as proprietary source code or Unsecured Credentials contained within software's source code. Having access to software's source code may allow adversaries to develop Exploits, while credentials may provide access to additional resources using Valid Accounts.

Note: This is distinct from Code Repositories, which focuses on conducting Reconnaissance via public code repositories.

Tactics
Collection
Platforms
SaaS
Telemetry
saas:github

How MITRE says to detect it DET0263

Detecting Bulk or Anomalous Access to Private Code Repositories via SaaS Platforms

SaaS Analytic 0732

Anomalous or bulk download activity from private or restricted repositories by non-developer or privileged accounts, often preceded by unusual login behavior (e.g., unfamiliar geo, OAuth token use, elevated API rate).

  • saas:github repo.download, repo.clone, oauth.authorize, repo.getContent
  • saas:github Login from unusual IP, device fingerprint, or location; access token creation from new client
  • saas:github Bulk access to multiple files or large volume of repo requests within short time window

SigmaHQ/sigma

5 rules
Detection Severity Format
Bitbucket Unauthorized Full Data Export Triggered Critical Sigma
Bitbucket Full Data Export Triggered High Sigma
Github Delete Action Invoked Medium Sigma
Github Outside Collaborator Detected Medium Sigma
Github Self Hosted Runner Changes Detected Low Sigma

elastic/detection-rules

4 rules
Detection Severity Format
GitHub Exfiltration via High Number of Repository Clones by User Medium Elastic TOML
Potential Secret Scanning via Gitleaks Medium Elastic TOML
Github Activity on a Private Repository from an Unusual IP Low Elastic TOML
High Number of Cloned GitHub Repos From PAT Low Elastic TOML

chronicle/detection-rules

3 rules
Detection Severity Format
github_access_granted_to_personal_access_token_followed_by_high_number_of_cloned_non_public_repositories High YARA-L
github_high_number_of_non_public_github_repositories_cloned High YARA-L
github_high_number_of_non_public_github_repositories_downloaded High YARA-L

Detection rules belong to the projects that publish them and remain under their own licenses. This site indexes and links to them; it claims no rights in them.