Forking of private repositories in the organization is allowed

Rule Details

Cortex AppSec Rule ID	APPSEC_CICD_153
Category	Data Protection
Severity	MEDIUM

Impact

Forking is permitted on private repositories within an organization, enabling users with 'read' permissions to fork a repository to another organization or user account. This could lead to a decrease in security as SAML SSO may not be mandatory for authentication when accessing a forked repository. Another security concern is that pull requests can be generated from forked repositories, which may result in a PPE attack.

Recommended Solution - Buildtime

It is recommended to prevent forking of repositories at the highest possible level (organization or enterprise, as applicable). Refer to the following instructions: https://docs.github.com/en/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.