Data from Information Repositories: Code Repositories T1213.003

Tactic: Collection

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.

Authoring guide

Patterns shared across the 14 rules above: which fields they filter on, what specific values they look for, and what they exclude. The catalog normalizes field names across vendors so Sigma's Image, Elastic's process.name, and Splunk's process_name collapse into one row. Each rule contributes at most once per row.

Fields filtered most (19 distinct)

The fields most rules look at when detecting this technique. The How column shows the operators authors use (eq, wildcard, regex_match, match) and how often each appears. Sample values are concrete examples to start from, not an exhaustive list.

FieldRulesHowSample values
EventType4eq 2, in 1, wildcard 1git.clone, Process Create*, ProcessRollup2, exec, git.push
github.repository_public4eq 4false
EventID3eq 3git.clone, personal_access_token.access_granted, repo.download_zip
action3eq 3codespaces.destroy, environment.delete, org.remove_outside_collaborator, org.remove_self_hosted_runner, org.runner_group_created
data_stream.dataset3eq 3github.audit
event.category3eq 3configuration
auditType.action2eq 2Full data export triggered, Unauthorized full data export triggered
auditType.category2eq 2Data pipeline
event.dataset2eq 2github.audit
event.type2eq 2change, start
github.repo2is_not_null 2
Esql.event_count1ge 125
SubjectUserName1macro 1github_clone.principal.user.userid
extracted.fields["public_repo"]1eq 1false
extracted.fields["repository_public"]1eq 1false

Top indicator values (45 distinct)

Specific (field, operator, value) combinations the rules check for, ranked by how many rules under this technique use each one. The Corpus reach column counts how many rules across the entire catalog (any technique) check the same combination. High numbers point to widely-used indicators that are likely noisy on their own; combine them with another condition for useful signal. Blank means the combination is specific to rules under this technique. Click a value to expand the rules under this technique that use it.

FieldKindValueRules (here)Corpus reach
github.repository_publiceq
false
45
data_stream.dataseteq
github.audit
318
event.categoryeq
configuration
311
EventIDeq
git.clone
22
EventIDeq
personal_access_token.access_granted
1
EventIDeq
repo.download_zip
1
EventTypeeq
git.clone
22
auditType.categoryeq
Data pipeline
22
event.dataseteq
github.audit
214
Esql.event_countge
25
1
EventTypein
git.clone
1
EventTypein
git.push
1
EventTypewildcard
Process Create*
12
EventTypewildcard
ProcessRollup2
12
EventTypewildcard
exec
12
EventTypewildcard
exec_event
12
EventTypewildcard
executed
12
EventTypewildcard
process_started
12
EventTypewildcard
start
12
SubjectUserNamemacro
github_clone.principal.user.userid
1
actioneq
codespaces.destroy
1
actioneq
environment.delete
1
actioneq
org.remove_outside_collaborator
1
actioneq
org.remove_self_hosted_runner
1
actioneq
org.runner_group_created
1
actioneq
org.runner_group_removed
1
actioneq
org.runner_group_runner_removed
1
actioneq
org.runner_group_runners_added
1
actioneq
org.runner_group_runners_updated
1
actioneq
org.runner_group_updated
1

Rules under this technique

Every rule in the catalog tagged with this technique, grouped by vendor. Click a rule title for its full predicates, exclusions, and indicators.

Platform (all)
Domain (all)

Sigma 5 rules

Elastic 6 rules

YARA-L 3 rules