Elastic Security Detection Rules

GitHub Protected Branch Settings Changed

Last updated 12 days ago on 2024-12-10
Created a year ago on 2023-08-29

About

This rule detects setting modifications for protected branches of a GitHub repository. Branch protection rules can be used to enforce certain workflows or requirements before a contributor can push changes to a branch in your repository. Changes to these protected branch settings should be investigated and verified as legitimate activity. Unauthorized changes could be used to lower your organization's security posture and leave you exposed for future attacks.
Tags
Domain: CloudUse Case: Threat DetectionTactic: Defense EvasionData Source: Github
Severity
medium
Risk Score
47
MITRE ATT&CK™

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

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

License
Elastic License v2(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(opens in a new tab or window)

Query
configuration where event.dataset == "github.audit"
  and github.category == "protected_branch" and event.type == "change"

Install detection rules in Elastic Security

Detect GitHub Protected Branch Settings Changed 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(opens in a new tab or window).