GitHub personal access token granted and used to clone large amount of repositories

Documentos > Datadog Security > OOTB Rules > GitHub personal access token granted and used to clone large amount of repositories

This rule is part of a beta feature. To learn more, contact Support.

Classification:

attack

Tactic:

TA0005-defense-evasion

Technique:

T1562-impair-defenses

This page is not yet available in Spanish. We are working on its translation.
If you have any questions or feedback about our current translation project, feel free to reach out to us!

Goal

Detect when a GitHub personal access token is used to clone repositories.

Strategy

This rule monitors GitHub audit logs for when a personal access token is used to clone a repository. If a user clones five repositories, a medium severity alert is generated. If the a user clones ten or more repositories, a high severity alert is generated.

Triage and response

Determine if the multiple repository clones by {{@github.actor}} are an expected action.
If the change was not authorized or was unexpected, begin your organization’s incident response process and investigate.