Verify Push Protection Setting
Type: Rule
ID: github-repo-push-protection
Source: v2/rules/github/repository/push-protection.yaml
Rego Source: push-protection.rego
Labels: GitHub, Repository
Verify secret_scanning_push_protection is configured in the GitHub repository.
note
This rule requires Github Repository Discovery Evidence. See here for more details.
tip
Signed Evidence for this rule IS NOT required by default but is recommended.
warning
Rule requires evaluation with a target. Without one, it will be disabled unless the --all-evidence flag is provided.
Usage example
uses: github/repository/push-protection@v2
Mitigation
Ensures that push protection is enabled, reducing the risk of unauthorized changes.
Description
This rule ensures that push protection is enabled in the GitHub repository. It performs the following steps:
- Checks the repository settings for push protection.
- Verifies that push protection is enabled.
Evidence Requirements:
- Evidence must be provided by the Scribe Platform's CLI tool through scanning GitHub repository settings.
Evidence Requirements
| Field | Value |
|---|---|
| signed | False |
| content_body_type | generic |
| target_type | data |
| predicate_type | http://scribesecurity.com/evidence/discovery/v0.1 |
| labels | - platform=github - asset_type=repository |