-
Notifications
You must be signed in to change notification settings - Fork 63
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
build docs workflow
committed
Jan 1, 2024
1 parent
bacb4cc
commit ad721b0
Showing
3 changed files
with
33 additions
and
6 deletions.
There are no files selected for viewing
4 changes: 2 additions & 2 deletions
4
docs/github/enterprise/enable_push_protection_secret_scanning.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,30 @@ | ||
--- | ||
layout: default | ||
title: Users Are Allowed To Bypass Ruleset Rules | ||
parent: Repository Policies | ||
grand_parent: GitHub Policies | ||
--- | ||
|
||
|
||
## Users Are Allowed To Bypass Ruleset Rules | ||
policy name: users_allowed_to_bypass_ruleset | ||
|
||
severity: MEDIUM | ||
|
||
### Description | ||
Rulesets rules are not enforced for some users. When defining rulesets it is recommended to make sure that no one is allowed to bypass these rules in order to avoid inadvertent or intentional alterations to critical code which can lead to potential errors or vulnerabilities in the software. | ||
|
||
### Threat Example(s) | ||
Attackers that gain access to a user that can bypass the ruleset rules can compromise the codebase without anyone noticing, introducing malicious code that would go straight ahead to production. | ||
|
||
|
||
|
||
### Remediation | ||
1. Go to the repository settings page | ||
2. Under "Code and automation", select "Rules -> Rulesets" | ||
3. Find the relevant ruleset | ||
4. Empty the "Bypass list" | ||
5. Press "Save Changes" | ||
|
||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters