Integrate Netskope

Netskope is a cloud-based zero-trust service that secures access to enterprise applications and data in hybrid IT environments while reducing risk and simplifying security operations. See https://www.netskope.com. You can protect access to Netskope by integrating Netskope with Identity as a Service. Once integrated, users can use single sign-on to log in to their Netskope account through Identity as a Service.

Note: This integration was tested using Identity as a Service version 5.33 and Netskope version 109.1.0.1127. Other versions of Netskope may require integration and configuration steps that differ from those documented in this procedure. For other versions of Netskope, this integration guide may be used as an initial approach for integrating Gong. In the event of other issues, contact support@entrust.com for assistance.

To integrate Netskope with Identity as a Service, you must do the following:

Before you begin, open two browser windows. In one window, log in to your Gong Administrator account. In the other window, log in to your IDaaS administrator account.

Step 1: Copy the SAML configurations from Identity as a Service

Copy the SAML Configuration from Identity as a Service

1. Log into your Identity as a Service administrator account.

2. Click > Security > Applications. The Applications Lists page appears.

3. Under SAML Cloud Integrations, click SAML Configuration. The SAML Configuration dialog box appears.

This dialog box contains information you need to configure your SAML application for Identity as a Service authentication.

4. Do one of the following:

● Leave this dialog box open to reference later in this procedure.

● Copy the Entity ID, Single Sign-on URL, and Single Logout URL to a text file and save it to reference later in this procedure.

Note: Depending on the integration you are performing, you may not need all three of these SAML configuration values.

Step 2: Copy the SAML signing certificate from Identity as a Service

Copy a SAML signing certificate

1. Log in to your Identity as a Service administrator account.

2. Click > Security > Applications. The Applications List page appears.

3. Under SAML Cloud Integrations, click SAML Signing Certificates. The SAML Signing Certificates page appears.

4. Click next to the certificate to copy it to the clipboard.

You can additionally download the certificate and save it for future use.

5. Open a text editor, such as Notepad, and paste the contents of the certificate into the text file.

6. Save the file.

Note: Be sure to same the file with the .cer extension, for example, SAML_certifcate.cer.

Step 3: Configure Netskope for IDaaS authentication and download the metadata from Netskope

1. Log in to your Netskope administrator account. The Dashboard page appears.

2. Click Settings. The General page appears.

3. Click Administration > SSO. The SSO page appears.

4. Under DefaultIDP, click Netskope Settings. The Netskope Settings dialog box appears.

5. Click to download the Netskope Metadata.

6. Save the metadata file in .XML format.

7. Click the Netskope Settings more option (...).

8. Select Edit from the drop-down menu. The SSO settings page appears.

9. Under Account, ensure the following:

a. Enable is set to On.

b. Disable Force Authentication is selected.

10. In the IDP SSO URL field, enter the Single Sign-On URL you copied in Step 1: Copy the SAML Configurations from Identity as a Service.

11. In the IDP Entity ID field, enter the Entity ID you copied in Step 1: Copy the SAML Configurations from Identity as a Service.

12. In the IDP Certificate field, browse to upload the SAML Signing Certificate you downloaded in Step 1: Copy the SAML Signing Certificate from Identity as a Service.

13. Click Save.

Step 4: Add Netskope to Identity as a Service

Add Netskope as an application to Identity as a Service

1. Log into your Identity as a Service administrator account.

2. Click > Security > Applications. The Applications Lists page appears.

3. Click Add. The Select an Application Template page appears.

4. Under SAML Cloud Integrations, click Netskope. The Add Netskope page appears.

5. Enter an Application Name.

6. Enter an Application Description.

7. Optional. Add a custom application logo.

a. Click next to Application Logo. The Upload Logo dialog box appears.

b. Click to select an image file to upload.

c. Browse to select your file and click Open. The Upload Logo dialog box reappears showing your selected image.

d. If required, resize your image.

e. Click OK.

8. Select the Authentication Flow that appears to users during login.

9. Click Next. The General page appears.

10. Click Upload Metadata XML file and browse to upload the Netskope Metadata that you downloaded in Step 3: Configure Netskope for IDaaS authentication and download the Netskope metadata file.

11. Enter the SAML Session Timeout to the time when the SAML Assertion times out. The maximum is 720 minutes.

12. Enter the Max Authentication Age (seconds) to set the maximum amount of time that can elapse before a user is required to reauthenticate during a new login attempt. This applies for both SP-initiated and IDP-initiated login. Set this field to -1 to disable this feature.

13. From the SAML NameID Attribute drop-down list, select Email.

14. From the SAML NameID Encoding Format drop-down list, select Email.

15. Select the SAML Signing Certificate that you copied in Step 2: Copy the SAML signing certificate from Identity as a Service.

16. Deselect Enable Go Back Button if you do not want users to be able to go back to the Netskope login page to log in.

17. Deselect Encrypt SAML Assertion.

18. Select Show Default Assertion Consumer URL Service in the My Profile. When selected, the Default Assertion Consumer URL appears in a user's My Profile page in addition to relay states and Alternative Assertion Consumer URLs.

19. Leave the remaining settings at the default values.

20. Click Submit.

Step 5: Create a resource rule to protect access to Netskope

Create a resource rule to protect access to a SAML application

1. Log in to your Identity as a Service administrator account.

2. Click > Security > Resource Rules. The Resource Rules List page appears.

3. Click + next to the application you want to protect with a resource rule. The Add Resource Rules page appears.

4. Enter a Rule Name and Rule Description for the resource rule.

5. In the Groups list, select the group or groups of users restricted by the resource rule.

These are the groups to which the resource rule applies. If you do not select any groups, by default the resource rule applies to all groups.

6. Click Next. The Authentication Conditions Settings page appears.

7. Optional: Select Disable Single Sign-On for Application to force a user to re-authenticate whenever they attempt a new login.

8. If you do not Enable Advanced Risk Factors, do the following:

a. Select the Authentication Flow from the drop-down list. The Authentication Flow flowchart updates based on the selection.

b. Click Submit to save the Resource Rule.

9. If you want to Enable Advanced Risk Factors, complete the remaining steps in this procedure.

10. Select Enable Advanced Risk Factors to add additional risk factors to the resource rule.

11. Select Enable Strict Access for Application to set the resource rule to deny access regardless of the outcome from other resource rules. If this option is disabled for any resource rule that denies access, the user is allowed access if at least one resource rule allows access.

12. For each Advanced Risk Factor, click the Deny option to deny access to the application if the risk factor fails regardless of the results of the other risk factors.

13. Click Date/Time to set the conditions as follows:

a. Select one of the following:

– Allow Date/Time to set when a user can access the application.

– Deny Date/Time to set when the user cannot access the application.

The Date/Time Context Condition Settings appear.

b. Select the Condition Type:

– Specific Date Range Condition—Allows or denies access to the application during a select period of days.

– Time-of-day and/or Day of Week Recurring Conditions—Allows or denies access to the application on a specific time of day, day of the week, or both. Recurring times selected only apply to days not denied.

– Clear Selection—Clears existing Date and Time conditions.

c. Set the Condition Type settings, as follows:

i) Select Use local time zone to use the local time zone or deselect Use local time zone to use the local time zone and begin typing the time zone in the Begin Typing Timezone name field and select the time zone from the drop-down list.

ii) If you selected Specific Date Range Condition, click Start Date to select a start date from the pop-up calendar. Optionally, select the End Date.

iii) If you selected Time-of-Day and/or Day-of-Week, click Start Time and select the start time from the pop-up clock. Optionally set the End Time. You must also select the days of the week for the condition.

d. Click Save to return to the Authentication Conditions Settings page.

14. Click Geolocation to set the Location Condition Settings, as follows:

a. Select Allow or Deny to create an allowed or denied country list.

b. From the Selected Countries drop-down list, select the countries to add or deny access to the application. Repeat until you have added all the desired countries to the list.

c. Select Allow Anonymous IP Address to increase the risk of users authenticating from an anonymous IP.

d. Click Save to save to return to the Authentication Conditions Settings page.

15. Click Source IP Address. The IP Address Risk Setting dialog box appears. Do one of the following:

a. Select Custom and add the required IP Allowed Addresses and IP Denied Addresses.

b. Select IP List Address and select the IP List to allow or deny.

c. Select None to not restrict any IP addresses.

d. Click OK to return to the Authentication Conditions Settings.

16. Click Machine Authentication to set the Machine Authentication Condition Settings, as follows:

a. Set the Machine Authentication Risk is less than or equal to the value that the machine authenticator's total risk score must be less than during authentication to pass this condition.

The risk score is based on the attribute differences between a user's Machine Authentication information and that recorded on Identity as a Service before the condition fails. If an attribute does not match, the attribute incurs the number of risk points shown in Non-Matching Risk Points for that attribute. The Non-Matching Risk Points values of each non-matching attribute are added together, resulting in a total risk score. This score is normalized to be out of 100 as follows:

Total Risk Score = (Total Risk Points of Failing Attributes / Maximum Risk Points of All Enabled Attributes) * 100

The resource rule condition fails when the number of non-matching risk points exceeds the Machine Authentication Risk value defined in this step. A value of 0 means that a single attribute difference causes the Device Fingerprint condition to fail. The default value is 3. The value between 0-50 can be entered.

The default value is defined by the Machine Risk Limit. See Modify machine authenticator settings.

b. Click Save.

17. Define the Location History / Known Locations and Travel Velocity conditions. The Risk-Based Authentication (RBA) settings of your Identity as a Service account define the location history and travel velocity conditions. See Manage risk-based authentication settings for more information.

18. Set the Device Certificates risk factor to require the client to perform client-authenticated SSL with a certificate issued from a trusted CA to pass.

19. Set the risk score for application conditions to set the risk percentage a user receives if they fail to meet the condition, as follows:

● Click the dot next to the condition setting and slide the risk scale to the risk percentage

-or-

● Click the 0% and enter the risk points and then click OK.

The default setting is 0%. The Risk percentage determines the authentication requirements as set by the Authentication Decision. When a user attempts to authenticate to an application, the final risk percentage is the sum of all failed conditions.

20. Set the Authentication Decision risk level for Medium Risk and High Risk as follows:

a. Click the risk threshold percentage to the right of Medium Risk or High Risk. The Risk Threshold dialog box appears.

b. Enter the risk percentage.

c. Click OK.

21. Select the Authentication Flows for Low Risk, Medium Risk, and High Risk from the drop-down lists. The Authentication Flows flowchart updates based on your selections.

22. Click Submit to create the resource rule.