Github Securlet Activation Failure: Access to CloudSOC is restricted in Github Organization

Products

• CASB Security Premium
• CASB Security Standard
• CASB Security Standard
• CASB Securlet SAAS
• CASB Security Advanced

Issue/Introduction

The customer is trying to activate the GitHub Securlet and Receives an error.

Securlet is not activated because access to CloudSOC is restricted in Github Organization

Resolution

Below are steps that often resolve "access is restricted" issue when trying to activate Github Securlet:

1) Remove 3rd Party access restrictions

1. In GitHub login as the Org owner
2. Navigate to https://github.com/organizations/<orgname>/settings/oauth_application_policy
3. Click 'Remove restrictions'
4. Retry the activation

2) Authorize Broadcom Securelet app:

1. In GitHub login as the Org owner
2. Navigate to https://github.com/settings/applications 
   
   
   
3. In the 'Authorized OAuth Apps' list click on 'Broadcom Securelet' app entry for US and 'Broadcom Securelet EU' for EU 
4. Under 'Organization access' section, locate the org you want to Activate and click 'Grant' to grant access to the organization
   
   
   
   
5. Check that client did not miss this step from Github Securlet Tech Doc: In Github, if the IP Allow list is enabled under Authentication Security add the CloudSOC IP range 144.49.240.0/21
6. Retry Github Securelet activation and it should work now

Additional Information

To confirm if the Activation is successful and the webhook is setup;

1. In GitHub login as the Org owner
2. Navigate to Org Settings > Webhooks - https://github.com/organizations/<orgname>/settings/hooks
3. You will see a list of Webhooks
4. For US it will be Broadcom Securlet and for EU it will be Broadcom Securelet EU
5. Click on the webhook entry
   
   
   
   6. You will see list of events delivered