Configure GitHub Instance for SaaS Security Posture Management

Configure GitHub Instance for SaaS Security Posture Management

The installation instruction describes how to integrate your GitHub account with Netskope. To configure GitHub for SaaS Security Posture Management, you need to authorize Netskope as a web application client to access your GitHub account. To configure GitHub for SaaS Security Posture Management, there are two parts to this procedure:

  • Install the Introspection for GitHub app in the GitHub organization account

  • Configure GitHub instance in the Netskope UI

Prerequisites:

  • You should have a GitHub enterprise cloud license to integrate GitHub with SaaS Security Posture Management (SSPM).

– Any non-enterprise licensed GitHub instances that are already integrated with SaaS Security Posture Management will stop receiving repository updates. You should upgrade your license and then re-grant the GitHub instance.
– If you have already configured GitHub for API Data Protection, you need not install the GitHub app yet again. You can edit the existing GitHub instance under Settings > Configure App Access > Classic > SaaS and enable the Security Posture checkbox and re-grant the app instance.

Install Introspection for GitHub App in GitHub

To install the Introspection for GitHub app in the GitHub organization:

– Ensure that you are logged in to your GitHub organization account before accessing the github URLs.
– If you are not sure of the management plane location of your tenant, contact your sales representative or Netskope support.
  1. Log in to www.github.com using your GitHub organization account.

  2. Based on the location of your Netskope tenant, install the Introspection for GitHub app from the following URLs:

  3. Click Install.

  4. Select the organization name > All repositories and click Install.

– Keep the installation options unchanged.
– Once you install the app, Netskope seeks consent for a set of permissions from your GitHub account. To know more about the permissions, see Permissions Required for GitHub.

Once installed, you should see a successful message. Proceed to configure the GitHub instance in Netskope UI.

If you have configured IP allow list in your Github Organization environment, you need to add Netskope IP address in the list as per your Home POP to access your Github details in Netskope. Refer Netskope SSPM IP addresses for Allowlisting to add IPs to the list.

Configure GitHub Instance in the Netskope UI

To authorize Netskope to access your GitHub instance:

  1. Log in to the Netskope tenant UI and go to Settings > Configure App Access > Classic > SaaS.

  2. Select the GitHub icon, and then click Setup Instance.

  3. The Setup Instance window opens. Enter the following details:

    • Instance Name: Enter the name of the GitHub organization. The instance name must be same as the GitHub organization name. It is case-sensitive.

    • Instance Type: Select the Security Posture checkbox. Select this option to allow Netskope to continuously scan through your SaaS app to identify and remediate risky SaaS app misconfigurations and align security posture with best practices and compliance standards. You can choose to run the policy at intervals of 15/30/45/60 minutes.

    • Admin Username: Enter the GitHub username of the administrator. The username must be same as the GitHub username of the administrator that you used to install the Introspection for GitHub app. It is case-sensitive.

    • Admin Email: Enter the email address associated with the GitHub username.

  4. Click Save, then click Grant Access for the app instance you just created. You will be prompted to log in with your admin username and password, and then click Grant Access. When the configuration results page opens, click Close.

Refresh your browser, and you should see a green check icon next to the instance name.

If you rename Github organization after you have onboarded the instance in Netskope, the existing integration will stop working. You will have to onboard an instance again in Netskope with the new Github organization’s name. You can delete the old instance with the previous organization’s name.

Next, you should configure a security posture policy. To do so, see SaaS Security Posture Management Policy Wizard.

Share this Doc

Configure GitHub Instance for SaaS Security Posture Management

Or copy link

In this topic ...