# Ensure organization base repository permission is set to read or none

- Source: https://support.icompaas.com/support/solutions/articles/a_1790019217102532-ensure-organization-base-repository-permission-is-set-to-read-or-none
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [Version Control System (VCS)](https://support.icompaas.com/support/solutions/c_1781179095087930) › [GitHub](https://support.icompaas.com/support/solutions/folders/f_1781179116560328)
- Last updated: 2026-10-26
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

Description:

This control ensures that the organization’s base repository permission is set to Read or No permission. The base permission is the minimum level of access every organization member automatically receives to all repositories in the organization.

  

Rationale:

A high base permission, such as Write or Admin, grants every member the ability to modify or administer all repositories, regardless of their role. Setting the base permission to Read or No permission enforces least privilege, ensuring that write and administrative access is granted explicitly through teams or individual repository roles.

  

Impact:

-   Members no longer receive write or admin access to all repositories by default.
    
-   Members who need write or admin access must be granted it through teams, repository roles, or direct collaborator access.
    
-   May temporarily disrupt members who relied on the base permission until explicit access is granted.
    
-   Enforces least privilege and reduces the risk of unauthorized changes.
    

  

Default Value:

-   Read. Organization owners can change the base permission to No permission, Read, Write, or Admin.
    

  

Remediation:

Test Plan:

1.  Sign in to GitHub as an organization owner.
    
2.  Click your profile picture in the upper-right corner, select Organizations, and select the target organization.
    
3.  Select Settings.
    
4.  In the Access section of the sidebar, select Member privileges.
    
5.  Under Base permissions, verify that the selected permission is Read or No permission.
    

6.  If the base permission is set to Write or Admin, follow the Implementation Steps to remediate the issue and repeat the test.
    

  

Implementation Steps:

1.  Sign in to GitHub as an organization owner.
    
2.  Review the organization’s teams and repository access, and grant write or admin access explicitly to members who require it.
    
3.  Click your profile picture in the upper-right corner, select Organizations, and select the target organization.
    
4.  Select Settings.
    
5.  In the Access section of the sidebar, select Member privileges.
    

6.  Under Base permissions, open the dropdown and select Read or No permission.
    

7.  Review the summary of changes and click Change base permission to confirm.
    

  

Backout Plan:

1.  Sign in to GitHub as an organization owner.
    
2.  Click your profile picture in the upper-right corner, select Organizations, and select the target organization.
    
3.  Select Settings.
    
4.  In the Access section of the sidebar, select Member privileges.
    
5.  Under Base permissions, open the dropdown and select the previous permission level.
    
6.  Review the summary of changes and click Change base permission to confirm.
    
7.  Verify that members have the expected access to organization repositories.
    

  

References:

-   [Setting Base Permissions for an Organization](https://docs.github.com/en/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/setting-base-permissions-for-an-organization)
    
-   [Repository Roles for an Organization](https://docs.github.com/en/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/repository-roles-for-an-organization)

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.
