Configure ServiceNow Instance for SaaS Security Posture Management
Configure ServiceNow Instance for SaaS Security Posture Management
The installation instructions describe how to integrate your ServiceNow account with Netskope. To configure ServiceNow for SaaS Security Posture Management, you need to authorize Netskope as a web application client to access your ServiceNow account. To configure ServiceNow for SaaS Security Posture Management, there are two parts to this procedure:
- Configure ServiceNow API Access
- Configure a ServiceNow Instance in the Netskope UI
Configure ServiceNow API Access
To configure the ServiceNow API endpoint:
-
Log in to your ServiceNow account as an admin user.
-
Click on All, search and click on “Application Registry”.
-
Click New to create a new application registry.
-
Click Create an OAuth API endpoint for external clients.
-
Enter a name. The Client ID and Client Secret are auto generated. Note down the Client ID and Secret; you will need these to create the ServiceNow instance in the Netskope UI.
You do not have to provide any value for Redirect URL and Logo URL.
The default value of the refresh token lifespan is 86,400 seconds (approx. 100 days). After that, the token will not be valid, and data will not be accessible. Netskope recommends to enter a minimum value of 31,536,000 seconds (approx. 1 year) to ensure accessibility. Once the refresh token expires, the app instance in Netskope UI will be shown as inactive. You should re-grant the ServiceNow app instance in the Netskope UI. -
When finished, click Submit.
Configure a ServiceNow Instance in the Netskope UI
Make sure you don’t have any ACL/IP ACL, business rules, or data policy constraints before setting up the instance.
ServiceNow administrator is a ServiceNow user used for the instance onboarding process and this ServiceNow administrator should have a set of roles mentioned in the following table. To add new roles to the ServiceNow user, refer to the Assign a role to a user link.
To Check Roles of a ServiceNow User:
-
Navigate to All > User Administration > Users and then open a user record.
-
Click on the Roles tab and check the list of roles present.
| Table | Role | Usage | Netskope Feature |
|---|---|---|---|
| incident | ITIL | Access records from the Incident table. | API Data Protection |
| problem | ITIL | Access records from the Problem table. | API Data Protection |
| sys_db_object | ITIL | Get Incident and Problem table records. | API Data Protection |
| sys_properties | Admin | Get system properties configurations records. | Netskope SSPM |
| sys_user | ITIL | Get system user records. | Netskope SSPM |
| sys_audit | Admin | Get system audit records for other tables to fetch delete information. | Netskope SSPM |
| sys_user_role | ITIL | Get roles assigned to a particular user. | Netskope SSPM |
| oauth_entity | Admin | Get OAuth Entity records. | Netskope SSPM |
| oauth_credential | Admin | Get OAuth Credential records. | Netskope SSPM |
Note
- If your setup involves a combination of API Data Protection and SSPM, ensure that the ServiceNow administrator has access to all the 6 tables. If your setup includes SSPM only, ensure that the ServiceNow administrator has admin role access. If the admin role is not provided, only a few sys_properties records will be visible and you can miss the user deletion information.
- Though the tables above require the ITIL role, it is recommended to give the admin role to all the tables so that API Data Protection can access the delete notifications from ServiceNow.
To authorize Netskope to access your ServiceNow instance:
- Log in to the Netskope tenant UI and go to Settings > Configure App Access > Classic > SaaS.
- Select the ServiceNow icon, and then click Setup Instance.
- The Setup Instance window opens. Enter the following details:
- Enter the name of the ServiceNow account instance.
Note
If your ServiceNow login URL is https://my_instance.service-now.com/, then enter my_instance as the instance name.
- 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.
Also, you have the option to run the policy at intervals (15 minutes, 30 minutes, 45 minutes, 60 minutes, and 24 hours).
- Enter the email address of the ServiceNow administrator.
Note
- To identify the email address of the ServiceNow administrator account, log in to your ServiceNow account, navigate to User Administration > Users. Click the administrator user and note down the email address.
- Netskope does not support SAML-based SSO for ServiceNow. The ServiceNow administrator email address must be a local user.
- Enter the name of the ServiceNow account instance.
- Click Save, then click Grant Access for the app instance you just created. You will be prompted to enter the following details:
- ServiceNow Admin – Enter the user ID of the ServiceNow administrator.
Note
To identify the user ID of the ServiceNow administrator account, log in to your ServiceNow account, navigate to User Administration > Users. Click the administrator user and note down the user ID.
- ServiceNow Password – Enter the password of the ServiceNow administrator.
- Enter Client ID – Enter the client ID you noted when you configured the ServiceNow API access.
- Enter Client Secret – Enter the client secret you noted when you configured the ServiceNow API access.
Click Grant. When the configuration results page open, click Close.
- ServiceNow Admin – Enter the user ID of the ServiceNow administrator.
Refresh your browser and you will see a green check icon next to the instance name.
Next, you should configure a security posture policy. To do so, see SaaS Security Posture Management Policy Wizard.
