Getting started with Security Incident Response integration with Zscaler

reference australia Updated Oct 22, 2026 2 min read get-started-with-zscaler.md
Raw file servicenow.com

Activate and set up the Zscaler Internet Access product to interface with your ServiceNow AI Platform instance and Security Incident Response product.

Setup task

Description

Assign and verify the required ServiceNow AI Platform and Security Incident Response roles.

These roles are required for configuration and verification of the expected results:- The admin role installs the integration from the ServiceNow Store and assigns the sn_si.admin role.

  • The sn_si.admin role performs the following tasks:
    • Configures the integration.
    • Creates, activates, and removes the URL Category lists.
    • Assigns the sn_si.analyst role.
  • The sn_si.analyst role creates entries and works with security incidents.

Verify that the ServiceNow core applications are installed and activated before you configure this integration.

The ServiceNow Integration Hub Enterprise Pack Installer [com.glide.hub.integrations.enterprise] plugin is required.

The Security Incident Response plugin (com.snc.security_incident) is required. This plugin automatically installs all the dependencies for the Security Incident Response product. Install and activate this plugin before you install and activate the other Security Operations applications for the integration.

Verify that the following Security Operations applications are installed and activated from the ServiceNow Store. If these applications are not already installed, install and activate each application one at a time in the following order:

  1. Security Incident Response Dependency (com.snc.si_dep)
  2. Security Integration Framework
  3. Security Support Common
  4. Security Support Orchestration
  5. Threat Intelligence Support Common
  6. Trusted Security Circles
  7. Security Operations Setup Assistant
  8. Security Incident Response

Verify the Zscaler versions.

  • This integration is supported on Zscaler Internet Access version 1.0 or later.
  • This integration is tested with the following Zscaler versions:
    • Zscaler Client Connector for Windows - 3.0
    • Zscaler Client Connector for macOS - 3.0
    • Zscaler Client Connector for Linux - Beta
    • Zscaler Cloud Connector - 6.1

Verify that you have the required Zscaler permissions and have configured access to the Zscaler Internet Access APIs.

  • You must have the admin credentials for Zscaler Internet Access.
  • You must have a valid cloud service API subscription. Zscaler Support must provide your key.
  • If you use Basic Auth, you must have Zscaler Internet Access admin credentials (user name and password). API authentication is based on a combination of the API key and Zscaler Internet Access admin credentials.
  • If you use OAuth 2.0, you must have a client ID, a client secret, and your tenant's vanity domain. For example, acme.zslogin.net.

Note: For more information on managing the Zscaler Internet Access API keys, see the Zscaler documentation.

Search documentation
Search document titles and file paths on the australia branch