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.
github-telemetry

Classification:

attack

Tactic:

TA0005-defense-evasion

Technique:

T1562-impair-defenses

Cette page n'est pas encore disponible en français, sa traduction est en cours.
Si vous avez des questions ou des retours sur notre projet de traduction actuel, n'hésitez pas à nous contacter.

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

  1. Determine if the multiple repository clones by {{@github.actor}} are an expected action.
  2. If the change was not authorized or was unexpected, begin your organization’s incident response process and investigate.
PREVIEWING: alai97/reorganize-some-sections-in-dora-metrics