Possible Github Push Protection Bypass Detected (via audit)
This rule detects when a user bypasses the push protection on a secret detected by secret scanning.
Sigmalowv1
sigma
possible-github-push-protection-bypass-detected-via-audit
title: Possible Github Push Protection Bypass Detected (via audit)
id: 0498b05a-4bea-56ee-bdde-b2e7fae4eccd
status: stable
description: This rule detects when a user bypasses the push protection on a secret detected by secret scanning.
references:
- https://attack.mitre.org/techniques/T1685/
- https://docs.github.com/en/enterprise-cloud@latest/code-security/secret-scanning/push-protection-for-repositories-and-organizations
- https://thehackernews.com/2024/03/github-rolls-out-default-secret.html
author: Huntrule Team
date: 2026-06-23
tags:
- attack.defense-impairment
- attack.t1685
logsource:
product: github
service: audit
definition: 'Requirements: The audit log streaming feature must be enabled to be able to receive such logs. You can enable following the documentation here: https://docs.github.com/en/enterprise-cloud@latest/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise#setting-up-audit-log-streaming'
detection:
selection:
action|contains: 'secret_scanning_push_protection.bypass'
condition: selection
falsepositives:
- Unknown
level: low
Known false positives
- Unknown
Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.