GitHub secret scanning disabled or bypassed

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 secret scanning setting has been disabled.

Strategy

This rule monitors GitHub audit logs for when a secret scanning setting has been disabled. GitHub scans repositories for known types of secrets to prevent fraudulent use of secrets that were committed accidentally. Disabling these settings could lead to a degradation in the organization’s security posture.

Triage and response

  1. Determine if the change taken by {{@github.actor}} is authorized.
  2. If the change was not authorized or was unexpected, begin your organization’s incident response process and investigate.

Changelog

  • 21 February 2024 - Updated detection rule name.
  • 4 September 2024 - Updated detection rule name.