Onboard a ServiceNow App to SSPM
Table of Contents
Expand all | Collapse all
-
-
- Allowed List of IP Addresses
-
- Begin Scanning a Bitbucket App
- Begin Scanning a Box App
- Begin Scanning ChatGPT Enterprise App
- Begin Scanning a Cisco Webex Teams App
- Begin Scanning a Confluence App
- Begin Scanning a Confluence Data Center App
- Begin Scanning a Dropbox App
- Begin Scanning a GitHub App
- Begin Scanning a Gmail App
- Begin Scanning a Google Drive App
- Begin Scanning a Jira App
- Begin Scanning a Jira Data Center App
- Begin Scanning a Microsoft Exchange App
- Begin Scanning Office 365 Apps
- Begin Scanning a Microsoft Teams App
- Begin Scanning a Salesforce App
- Begin Scanning a ServiceNow App
- Begin Scanning a ShareFile App
- Begin Scanning a Slack Enterprise App
- Begin Scanning a Slack for Pro and Business App
- Begin Scanning a Workday App (Beta)
- Begin Scanning a Zendesk App
- Begin Scanning a Zoom App
- Reauthenticate to a Cloud App
- Verify Permissions on Cloud Apps
- Start Scanning a Cloud App
- Rescan a Managed Cloud App
- Delete Cloud Apps Managed by Data Security
- API Throttling
- Configure Classification Labels
- Microsoft Labeling for Office 365
- Google Drive Labeling
- Configure Phishing Analysis
- Configure WildFire Analysis
-
-
-
- What is an Incident?
- Assess New Incidents on Data Security
- Filter Incidents
- Configure Slack Notification Alerts on Data Security
- Security Controls Incident Details
- Track Down Threats with WildFire Report
- Customize the Incident Categories
- Close Incidents
- Download Assets for Incidents
- View Asset Snippets for Incidents
- Analyze Inherited Exposure
- Email Asset Owners
- Modify Incident Status
-
-
-
- What’s SaaS Security Inline?
- Navigate To SaaS Security Inline
- SaaS Visibility for NGFW
- SaaS Visibility and Controls for NGFW
- SaaS Visibility for Prisma Access
- SaaS Visibility and Controls for Panorama Managed Prisma Access
- SaaS Visibility and Controls for Cloud Managed Prisma Access
- Activate SaaS Security Inline for NGFW
- Activate SaaS Security Inline for VM-Series Firewalls with Software NGFW Credits
- Activate SaaS Security Inline for Prisma Access
- Connect SaaS Security Inline and Strata Logging Service
- Integrate with Azure Active Directory
-
-
- SaaS Policy Rule Recommendations
- App-ID Cloud Engine
- Guidelines for SaaS Policy Rule Recommendations
- Predefined SaaS Policy Rule Recommendations
- Apply Predefined SaaS Policy Rule Recommendations
- Create SaaS Policy Rule Recommendations
- Delete SaaS Policy Rule Recommendations
- Enable SaaS Policy Rule Recommendations
- Modify Active SaaS Policy Rule Recommendations
- Monitor SaaS Policy Rule Recommendations
-
- Enable Automatic Updates for SaaS Policy Rule Recommendations on Cloud Managed Prisma Access
- Import New SaaS Policy Rule Recommendations on Cloud Managed Prisma Access
- Update Imported SaaS Policy Rule Recommendations on Cloud Managed Prisma Access
- Remove Deleted SaaS Policy Rule Recommendations on Cloud Managed Prisma Access
- Manage Enforcement of Rule Recommendations on NGFW
- Manage Enforcement of Rule Recommendations on Panorama Managed Prisma Access
- Change Risk Score for Discovered SaaS Apps
-
-
-
-
- Onboarding Overview for Supported SaaS Apps
- Onboard an Aha.io App to SSPM
- Onboard an Alteryx Designer Cloud App to SSPM
- Onboard an Aptible App to SSPM
- Onboard an ArcGIS App to SSPM
- Onboard an Articulate Global App to SSPM
- Onboard an Atlassian App to SSPM
- Onboard a BambooHR App to SSPM
- Onboard a Basecamp App to SSPM
- Onboard a Bitbucket App to SSPM
- Onboard a BlueJeans App to SSPM
- Onboard a Box App to SSPM
- Onboard a Bright Security App to SSPM
- Onboard a Celonis App to SSPM
- Onboard a Cisco Meraki App to SSPM
- Onboard a ClickUp App to SSPM
- Onboard a Confluence App to SSPM
- Onboard a Contentful App to SSPM
- Onboard a Convo App to SSPM
- Onboard a Couchbase App to SSPM
- Onboard a Coveo App to SSPM
- Onboard a Crowdin Enterprise App to SSPM
- Onboard a Customer.io App to SSPM
- Onboard a Databricks App to SSPM
- Onboard a Datadog App to SSPM
- Onboard a DocHub App to SSPM
- Onboard a DocuSign App to SSPM
- Onboard an Envoy App to SSPM
- Onboard an Expiration Reminder App to SSPM
- Onboard a Gainsight PX App to SSPM
- Onboard a GitLab App to SSPM
- Onboard a Google Analytics App to SSPM
- Onboard a Google Workspace App to SSPM
- Onboard a GoTo Meeting App to SSPM
- Onboard a Grammarly App to SSPM
- Onboard a Harness App to SSPM
- Onboard a Hellonext App to SSPM
- Onboard an IDrive App to SSPM
- Onboard an Intercom App to SSPM
- Onboard a Jira App to SSPM
- Onboard a Kanbanize App to SSPM
- Onboard a Kanban Tool App to SSPM
- Onboard a Kustomer App to SSPM
- Onboard a Lokalise App to SSPM
- Onboard a Microsoft Azure AD App to SSPM
- Onboard a Microsoft Outlook App to SSPM
- Onboard a Microsoft Power BI App to SSPM
- Onboard a Miro App to SSPM
- Onboard a monday.com App to SSPM
- Onboard a MongoDB Atlas App to SSPM
- Onboard a MuleSoft App to SSPM
- Onboard a Mural App to SSPM
- Onboard an Office 365 App to SSPM
- Onboard an Okta App to SSPM
- Onboard a PagerDuty App to SSPM
- Onboard a RingCentral App to SSPM
- Onboard a Salesforce App to SSPM
- Onboard an SAP Ariba App to SSPM
- Onboard a ServiceNow App to SSPM
- Onboard a Slack Enterprise App to SSPM
- Onboard a Snowflake App to SSPM
- Onboard a SparkPost App to SSPM
- Onboard a Tableau Cloud App to SSPM
- Onboard a Webex App to SSPM
- Onboard a Workday App to SSPM
- Onboard a Wrike App to SSPM
- Onboard a YouTrack App to SSPM
- Onboard a Zendesk App to SSPM
- Onboard a Zoom App to SSPM
- Onboarding an App Using Azure AD Credentials
- Onboarding an App Using Okta Credentials
- Register an Azure AD Client Application
- View the Health Status of Application Scans
- Delete SaaS Apps Managed by SSPM
Onboard a ServiceNow App to SSPM
Connect a ServiceNow instance to SSPM to detect posture risks.
For SSPM to detect posture risks in your ServiceNow instance, you must onboard your
ServiceNow instance to SSPM. Through the onboarding process, SSPM connects to a
ServiceNow API and, through the API, scans your ServiceNow instance for
misconfigured settings. If there are misconfigured settings, SSPM suggests a
remediation action based on best practices.
SSPM gets access to your ServiceNow instance through OAuth 2.0 authorization. To
enable OAuth 2.0 authorization, you first register an OAuth 2.0 integration
application in ServiceNow before onboarding your ServiceNow instance in SSPM. During
the onboarding process, you are prompted to log in to ServiceNow and to grant SSPM
the access it requires.
You can also use the OAuth 2.0 application to enable SSPM to create tickets in ServiceNow. To enable ServiceNow
ticketing, you link SSPM to a ServiceNow instance from the
Ticketing Settings page. To enable ticketing, SSPM requires the same information
that it requires for onboarding ServiceNow. However, onboarding ServiceNow for
configuration scans and linking to ServiceNow for ticketing are two separate
procedures. When you are creating your OAuth 2.0 application in ServiceNow, be aware
that SSPM uses different redirect URLs depending on whether you are onboarding
ServiceNow for configuration scans or linking to ServiceNow for ticketing. Your
OAuth 2.0 integration application can specify both of these redirect URLs.
To onboard your ServiceNow instance, you complete the following actions:
Collect Information for Accessing Your ServiceNow Instance
Item | Description |
---|---|
Client ID | SSPM will access a ServiceNow API through an OAuth 2.0 application that you create. ServiceNow generates the Client ID to uniquely identify the application. |
Client Secret | SSPM will access the ServiceNow API through an OAuth 2.0 application that you create. ServiceNow generates the Client Secret, which SSPM uses to authenticate to the application. |
Instance URL | The unique URL for your ServiceNow instance. |
As you complete the following steps, make note of the values of the items
described in the preceding table. You will need to enter these values during
onboarding to enable SSPM to access your ServiceNow instance.
- From SSPM, get the redirect URLs that you will need when you register your OAuth 2.0 application in ServiceNow. For onboarding, you must specify the redirect URL for onboarding for scans. If you also want to enable ServiceNow ticketing from SSPM, you must also specify the redirect URL for ticketing.To get the redirect URL for onboarding ServiceNow for scans, you will begin the onboarding procedure in SSPM, but you will not complete the procedure.
- From the Add Application page in SSPM ( Posture SecurityApplicationsAdd Application), click the ServiceNow tile.
- On the Posture Security tab, Add
New instance.SSPM displays a configuration page for onboarding a ServiceNow instance. The Redirect URL field displays the redirect URL value.
- Copy the redirect URL and paste it into a text file.Do not continue to the next step unless you have copied the redirect URL. You will need to specify this URL later when you are configuring your OAuth 2.0 integration application.
If you also want to link SSPM to the ServiceNow instance for ticketing, get the redirect URL for ticketing. To get this redirect URL, you will begin the procedure for linking SSPM to ServiceNow for ticketing, but you will not complete the procedure.- Select SaaS SecuritySettings Workflow Ticketing Settings.
- Add Link for ServiceNow.The login page for linking to a ServiceNow instance is displayed. The Redirect URL field displays the redirect URL value. Copy the redirect URL and paste it into a text file.Do not continue to the next step unless you have copied the redirect URL. You will need to specify this URL later when you are configuring your OAuth 2.0 integration application.
Create an authentication scope to limit access to ServiceNow REST APIs.During onboarding, you will log in to a ServiceNow account and will grant SSPM access to that account. SSPM will get access to your ServiceNow account through an OAuth 2.0 integration application that you will create. By default, the OAuth token will have full access to the REST APIs that the ServiceNow account can access. Although SSPM will access only the Table API, the OAuth token will allow more access than SSPM requires. Before you create the OAuth 2.0 integration application, create an authentication scope, which will limit SSPM's access to only the Table API. You can create a scope that allows SSPM read-access only or full read and write access to the Table API. Later, you will assign this scope to your OAuth 2.0 application.- Log in to ServiceNow as an administrator.
- Make sure the REST API Auth Scope plugin (com.glide.rest.auth.scope) is activated in ServiceNow. To verify that the plugin is activated, navigate to System Definition Plugins and use the search field to locate the plugin. If the plugin is not installed, refer to the ServiceNow documentation to install and activate the REST API Auth Scope plugin.
- Create the authentication scope.
- Navigate to the Authentication Scopes table (sys_auth_scope.list) by using the filter navigator.
- Click New to define the authentication scope.
- Specify a meaningful Name for your
authentication scope, such as SSPM Connector. You can
optionally specify a longer
Description.Make note of the authentication scope name. You will need to specify this name later when you are configuring a REST API Auth Scope and your OAuth 2.0 integration application.
- Submit.
- Create a REST API Auth Scope and link it to your authentication
scope.The REST API Auth Scope is where you will limit SSPM access to the Table API only. You can allow SSPM full read and write access to perform all HTTP methods, or you can limit SSPM to read-only access (GET method only).
- Navigate to the REST API Auth Scopes list (System Web ServicesAPI Auth ScopesREST API Auth Scope).
- Click New to define the REST API Auth Scope.
- In the Name field, specify a name for your REST API Auth Scope.
- From the REST API list, select Table API.
- Configure the REST API Auth Scope to allow SSPM full read
and write access (all HTTP methods) to the Table API, or
read-only access (HTTP GET method only).
- Read-only Access: Configuring the REST API
Auth Scope for reduced, read-only access will enable
SSPM to perform configuration scans, risky account
scans, and third-party plugin scans. However, SSPM
will not be able to perform automated remediation of
misconfigured settings.To configure the REST API Auth Scope for read-only access, complete the following steps:
- Deselect the Apply auth scope to all http methods in this API checkbox.
- From the HTTP Method list, select GET.
- Read and Write Access: Configuring the REST
API Auth Scope for full read and write access will
enable SSPM to perform configuration scans, risky
account scans, and third-party plugin scans. It will
also enable SSPM to perform automated remediation of
misconfigured settings.To configure the REST API Auth Scope for Read and Write access, select the Apply auth scope to all http methods in this API checkbox.
- Read-only Access: Configuring the REST API
Auth Scope for reduced, read-only access will enable
SSPM to perform configuration scans, risky account
scans, and third-party plugin scans. However, SSPM
will not be able to perform automated remediation of
misconfigured settings.
- In the Auth Scope field, specify the name of the authentication scope that you created earlier. This specification links the REST API Auth Scope to the authentication scope.
- Submit.
Create your OAuth 2.0 application in ServiceNow.- Log in to ServiceNow as an administrator.
- Navigate to the Application Registries page (System OAuth Application Registry).
- From the Application Registries page, create a New application.
- ServiceNow prompts you to select the type of OAuth application that
you want to create. Specify that you want to Create an
OAuth API endpoint for external
clients.ServiceNow displays a dialog for configuring your OAuth 2.0 application.
- Fill in your OAuth 2.0 application details using the fields that
ServiceNow provides.
- Specify the Redirect URL for onboarding ServiceNow, and, optionally, the redirect URL for linking to ServiceNow for ticketing. If you are adding both redirect URLs, separate the two URLs with a comma.
- Under Auth Scopes, add the authentication scope that you created earlier.
- Submit.ServiceNow registers your new OAuth 2.0 application and displays the Application Registries page. The Application Registries page now lists your OAuth 2.0 application.
- Open your OAuth 2.0 application and copy the Client ID and Client
Secret into a text file.Do not continue to the next step unless you have copied the Client ID and Client Secret. You must provide this information to SSPM during the onboarding process.
Connect SSPM to Your ServiceNow Instance
By adding a ServiceNow app in SSPM, you enable SSPM to connect to your ServiceNow instance for scanning. - From the Add Application page ( Posture SecurityApplicationsAdd Application), click the ServiceNow tile.On the Posture Security tab, Add New instance.On the configuration page, enter your Instance URL and the application credentials (Client ID and Client Secret).Specify whether you are granting SSPM Read Permissions only or Read and Write Permissions.The option you choose depends on how you configured the authentication scope to limit access. If you configured the authentication scope to allow only the GET method, select Read Permissions. If you configured the authentication scope to allow access to all HTTP methods, select Read and Write Permissions.The onboarding page lists the API scopes that SSPM will access to complete scans and to perform automated remediation.Connect.SSPM redirects you to the ServiceNow log in page.Log in using a ServiceNow administrator account.ServiceNow displays a consent form.Review the consent form and Allow access to the account.If you also want to create ServiceNow tickets from SSPM, link SSPM to the ServiceNow instance. You link SSPM to ServiceNow from the Ticketing Settings page (SaaS SecuritySettings Workflow Ticketing Settings).