GitLab brute force attack

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

Set up the gitlab integration.

Esta página aún no está disponible en español. Estamos trabajando en su traducción.
Si tienes alguna pregunta o comentario sobre nuestro actual proyecto de traducción, no dudes en ponerte en contacto con nosotros.

Goal

Detects GitLab brute force attacks where multiple failed login attempts are followed by successful actions.

Strategy

This rule monitors GitLab audit events for patterns indicating brute force attacks. It tracks failed login attempts, then correlates these with any subsequent successful events from the same user account. The detection triggers when more than 5 failed login attempts are followed by at least one successful event within the evaluation window.

Triage & Response

  • Examine the failed login attempts for {{@usr.name}} to determine the source IP addresses and timing patterns of the attack.
  • Verify if the successful authentication following the failed attempts represents legitimate user activity or account compromise.
  • Review the user account’s recent activity to identify any suspicious actions performed after the successful login.