Github Push Protection Bypass Detected

 1title: Github Push Protection Bypass Detected
 2id: 02cf536a-cf21-4876-8842-4159c8aee3cc
 3status: experimental
 4description: Detects when a user bypasses the push protection on a secret detected by secret scanning.
 5references:
 6    - https://docs.github.com/en/enterprise-cloud@latest/code-security/secret-scanning/push-protection-for-repositories-and-organizations
 7    - https://thehackernews.com/2024/03/github-rolls-out-default-secret.html
 8author: Muhammad Faisal (@faisalusuf)
 9date: 2024-03-07
10tags:
11    - attack.defense-evasion
12    - attack.t1562.001
13logsource:
14    product: github
15    service: audit
16    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'
17detection:
18    selection:
19        action|contains: 'secret_scanning_push_protection.bypass'
20    condition: selection
21falsepositives:
22    - Allowed administrative activities.
23level: low

References

• About push protection - GitHub Enterprise Cloud Docs

  

  Push protection blocks contributors from pushing secrets to a repository and generates an alert whenever a contributor bypasses the block. Push protection can be applied at the repository, organization, and user account level.

  
  Read More

• GitHub Rolls Out Default Secret Scanning Push Protection for Public Repositories

  

  GitHub's new default push protection has got your back, scanning for secrets in public repos

  
  Read More

Related rules

• AMSI Bypass Pattern Assembly GetType
• AWS CloudTrail Important Change
• AWS Config Disabling Channel/Recorder
• AWS GuardDuty Important Change
• Add SafeBoot Keys Via Reg Utility