Branch_protection — CraftedSignal Threat Feedhttps://feed.craftedsignal.io/tags/branch_protection/Trending threats, MITRE ATT&CK coverage, and detection metadata — refreshed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioTue, 02 Jan 2024 12:00:00 +0000GitHub Enterprise Classic Branch Protection Rule Disabledhttps://feed.craftedsignal.io/briefs/2024-01-github-branch-protection-disabled/Tue, 02 Jan 2024 12:00:00 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2024-01-github-branch-protection-disabled/Detection of disabled classic branch protection rules in GitHub Enterprise, indicating potential bypass of code review and security controls, leading to unauthorized code changes and supply chain compromise.This brief focuses on the detection of disabled classic branch protection rules within a GitHub Enterprise environment. The detection is based on monitoring GitHub Enterprise audit logs for events related to the removal of branch protections. Attackers may disable these rules to bypass code review processes and introduce malicious code or vulnerabilities directly into protected branches. This action can be part of a larger attack, where adversaries first weaken security controls before injecting malicious content. Identifying and responding to these events is crucial for maintaining the integrity and security of the software supply chain. This analytic is sourced from Splunk’s security content and is designed to run on GitHub Enterprise audit logs ingested into Splunk.

Attack Chain

  1. An attacker gains unauthorized access to a GitHub Enterprise account with sufficient privileges.
  2. The attacker navigates to the repository settings within the GitHub Enterprise instance.
  3. The attacker identifies the classic branch protection rules configured for a target branch.
  4. The attacker disables one or more of these branch protection rules, such as code review enforcement or restrictions on force pushes. This generates a protected_branch.destroy event in the audit logs.
  5. The attacker commits and pushes unauthorized or malicious code directly to the protected branch, bypassing established security controls.
  6. The malicious code is merged into the main branch, potentially affecting production systems or downstream consumers of the code.
  7. The attacker may attempt to cover their tracks by deleting audit logs or manipulating other security controls.

Impact

The impact of disabled branch protection rules can be significant. Successful exploitation can lead to the introduction of vulnerabilities, malicious code, or backdoors into the software supply chain. This can result in data breaches, system compromise, and reputational damage. The number of affected systems and the extent of the damage depend on the scope and nature of the malicious code injected. The targets are GitHub Enterprise organizations that rely on branch protection rules to maintain code quality and security.

Recommendation

  • Enable GitHub Enterprise Audit log streaming to a SIEM or log management solution to capture protected_branch.destroy events as described in the GitHub Enterprise documentation.
  • Deploy the Sigma rule GitHub Enterprise Disable Classic Branch Protection Rule to detect instances where branch protection rules are disabled and tune it for your environment.
  • Investigate any alerts generated by the Sigma rule, focusing on the actor, repo, and user_agent fields to understand the context of the event.
  • Implement multi-factor authentication (MFA) for all GitHub Enterprise accounts, especially those with administrative privileges.
  • Regularly review and audit GitHub Enterprise configurations to ensure that branch protection rules are properly configured and enforced.
]]>mediumadvisorygithubbranch_protectionsupply_chain