Org Default Permissions
More Info:
The default permission given to new organization users should be set to none. Read permissions risk exposing private repositories, while write or admin permissions risk sensitive access to repositories for new users.
Risk Level
Medium
Address
Security
Compliance Standards
Remediation
Using Console
The misconfiguration of “Org Default Permissions” means that the default permission level for new repositories in your GitHub organization is set to a level that is too permissive. To remediate this misconfiguration in GitHub using the GitHub console, follow these steps:
- Log in to your GitHub account and navigate to your organization’s page.
- Click on the “Settings” tab in the top right corner of the page.
- In the left-hand menu, click on “Member privileges.”
- Scroll down to the “Repository permissions” section and locate the “Default repository permission” dropdown menu.
- Select the appropriate permission level that you want to set as the default for new repositories. For example, if you want to limit access to only organization members, select “Read” or “Write” access for “Organization members” only.
- Click on the “Save” button at the bottom of the page to save your changes.
By following these steps, you have successfully remediated the “Org Default Permissions” misconfiguration for your GitHub organization using the GitHub console.
Using CLI
The “Org Default Permissions” misconfiguration in GitHub refers to the default permission levels set for new members in the organization. To remediate this using GitHub CLI, follow these steps:
-
Open your terminal and log in to your GitHub account using the GitHub CLI command
gh auth login
. -
Once you are logged in, use the following command to view the current default permission level for new members in your organization:
Replace
<org-name>
with the name of your GitHub organization. -
If the default permission level is set to “read,” use the following command to change it to “write”:
Replace
<org-name>
with the name of your GitHub organization. -
If the default permission level is set to “admin,” use the following command to change it to “write”:
Replace
<org-name>
with the name of your GitHub organization.Note that setting
default_repository_permission_locked
totrue
will prevent members from changing their own permission levels. -
Verify that the default permission level has been updated by running the command in step 2 again.
By following these steps, you will have successfully remediated the “Org Default Permissions” misconfiguration for GitHub using GitHub CLI.
Using Python
The misconfiguration “Org Default Permissions” in GitHub means that new repositories created within the organization inherit default permissions that may not be appropriate for the organization’s security policies. To remediate this misconfiguration, you can use the GitHub API with Python to update the default repository permissions for the organization.
Here are the step-by-step instructions to remediate this misconfiguration for GitHub using Python:
-
Generate a Personal Access Token (PAT) with the necessary permissions to update the organization’s settings. You can do this by going to your GitHub account settings, selecting “Developer settings”, and then “Personal access tokens”. Create a new token with the “admin:org” scope.
-
Install the PyGitHub library, which is a Python wrapper for the GitHub API. You can install it using pip:
-
Use the PyGitHub library to authenticate with the GitHub API using the PAT you generated in step 1:
-
Use the
get_default_repository_permission
method to check the current default repository permission for the organization: -
If the default repository permission is not “none”, use the
set_default_repository_permission
method to update it to “none”: -
Run the Python script to update the default repository permission for the organization.
By following these steps, you can remediate the “Org Default Permissions” misconfiguration for GitHub using Python.