GitHub onboarding is now available in Next-Gen SaaS Security Posture Management (SSPM). As part of this change, new GitHub instances can no longer be onboarded from Classic SSPM.
Existing GitHub instances continue to function in Classic SSPM, but must be migrated to Next-Gen SSPM.
Why do I need to migrate my GitHub instance?
Netskope is moving GitHub support to Next-Gen SSPM. Classic SSPM support for GitHub will be phased out, and existing instances must migrate to continue functioning without interruption.
How do I migrate my GitHub instance?
1. Log in to the Netskope tenant UI and go to Settings > Configure App Access >Next Gen > Security Posture.
2. Select the GitHub icon.
3. A list of GitHub organization accounts eligible for migration appears. For the GitHub organization instance you want to migrate, install the Next-Gen GitHub App. Follow step 1 in Onboard GitHub. Select the GitHub instance you want to migrate.
4. Click the three dots to the right of the instance name.
5. Select Regrant.
6. Authenticate the regrant when prompted.
Migration starts automatically after you authenticate. The Classic instance remains active during migration and is removed automatically once migration completes.
What happens to my Classic instance during migration?
The Classic instance remains active and continues to function while migration is in progress. Once migration completes, the Classic instance is removed automatically. You don’t need to manually delete it.
Do I need to onboard GitHub again if I’m a new user?
No. If you haven’t onboarded GitHub yet, onboard it directly in Next-Gen SSPM. See Onboard GitHub for instructions. This migration process doesn’t apply to you.