Elastic Security Detection Rules

GitHub Secret Scanning Disabled

Last updated a month ago on 2025-12-16
Created 2 years ago on 2023-12-16

About

Detects when GitHub Secret Scanning is disabled for a repository. Adversaries may disable secret scanning to evade detection of hardcoded secrets, such as API keys or credentials, that could be used for further compromise or data exfiltration.
Tags
Domain: CloudUse Case: Threat DetectionTactic: Defense EvasionData Source: GithubLanguage: eql
Severity
low
Risk Score
21
MITRE ATT&CK™

Defense Evasion (TA0005)(external, opens in a new tab or window)

↳ Impair Defenses (T1562)(external, opens in a new tab or window)

License
Elastic License v2(external, opens in a new tab or window)

Definition

Rule Type
Event Correlation Rule
Integration Pack
Prebuilt Security Detection Rules
Index Patterns
logs-github.audit-*
Related Integrations

github(external, opens in a new tab or window)

Query
text code block:
configuration where event.dataset == "github.audit" and event.type == "change" and event.action == "repository_secret_scanning.disable"

Install detection rules in Elastic Security

Detect GitHub Secret Scanning Disabled in the Elastic Security detection engine by installing this rule into your Elastic Stack.

To setup this rule, check out the installation guide for Prebuilt Security Detection Rules(external, opens in a new tab or window).