Set up ServiceNow for Integration

1. Mapping method: Use ServiceNow Classes Add support for the Purdue levels to which OT devices are assigned.

   If you want to use the ServiceNow IoT Device table as the mapping method, skip this step and proceed to step 2.

   This mapping method, using ServiceNow classes, focuses on OT devices, and all but one of the OT device attributes that IoT Security sends ServiceNow are predefined in the ServiceNow Configuration Item class. The one attribute for OT devices that must be added is for Purdue Level assignments.

   Because ServiceNow classes use an inheritance system, child classes inherit attributes added to their parent classes. Therefore, when you add PANW Purdue Level as a device attribute to the Configuration Item class, it’s listed as Added there, and it’s listed as Derived in the Hardware class, which is a child class of Configuration Item and inherits all its attributes. The following steps describe how to add the attribute to the Configuration Item class.

   It’s possible to use the class mapping method to map attributes for other device types such as IoT and IT devices. However, you might need to configure additional attributes for them in ServiceNow and you must modify XSOAR integration jobs for ServiceNow to include a mapping of their device type, category, or profile in IoT Security to the appropriate class in ServiceNow. In this configuration step, it’s assumed that you are only interested in having IoT Security send ServiceNow OT device attributes.

   1. Select All at the top of the ServiceNow page, enter ci class in the Filter navigator field, and then select CI Class ManagerHierarchy.
   2. Select Configuration ItemAttributesAdded and then double-click Insert a new row.
   3. Enter PANW Purdue Level as the Column label and then click the green check mark.
      ServiceNow automatically creates u_panw_purdue_level as the entry in the Column name field to indicate it’s a user-defined attribute.
   4. Leave the other settings for Type, Max length, and so on at their default values and Save.
2. Mapping method: Use ServiceNow IoT Device Table Create or edit a ServiceNow table for receiving device records from IoT Security.

   If you are creating a new table, do step 2.1. If you are editing an existing table, go to step 2.2. If you are using ServiceNow classes instead of the IoT device table as the mapping method, skip this step.

   1. To create a table in ServiceNow for receiving device records from IoT Security, filter the navigation menu by entering System Definition in the Filter navigator field, click TablesNew, and then enter the following:
      Label: Zingbox discovered devices
      Name: The name field autofills, automatically prepending u_, converting any uppercase characters to lowercase, and converting spaces and dashes to underscores to connect words. It automatically converts Zingbox discovered devices in the Label field to u_zingbox_discovered_devices in the Name field.
      Zingbox discovered devices is the default label and u_zingbox_discovered_devices is the default name to which IoT Security sends device records. If you use any another table with a different label, you must change the ServiceNow Discovered IoT Device Table Name in the two IoT Security jobs that send device records to this table: PANW IoT Bulk Export To Servicenow and PANW IoT ServiceNow Integration. For example, if you enter IoT Security discovered devices for the label in ServiceNow, which automatically generates u_iot_security_discovered_devices as the table name, then enter u_iot_security_discovered_devices in the two ServiceNow jobs in IoT Security
      Extends table: Your new table must extend the Configuration Item. Search for Configuration Item and choose it from the list.
   2. Add the following custom column labels to the table so that ServiceNow can receive inventory updates from IoT Security and populate these table columns with data:
      The following are default column labels. If you use another cmdb device table with different column labels, you must change the corresponding default values in the two IoT Security jobs that send data to this table. The column labels are case sensitive. For example, category is different from Category.
      category
      profile
      iot_tag
      iot_vendor
      iot_model
      iot_os
      iot_ssid
      iot_site
      iot_vlan
      iot_wired_wireless
      os_support

   3. When done, click Submit.
   4. After adding the custom column labels, the table will consist of predefined and custom columns. To display a smaller set of relevant columns, click the Zingbox discovered devices label on the Tables page, scroll down past the table and click Show List in the Related Links section, and then click the Personalize List icon (

      ). Use the left and right arrows to move column labels so that only the ones you want to see are in the Selected pane and then click OK.

3. Create a ServiceNow table for receiving security incidents from IoT Security.

   1. From the ServiceNow Tables page, click New and enter the following:
      Label: Enter Zingbox alerts vulnerability incident.
      Name: The name field autofills, automatically prepending u_, converting any uppercase characters to lowercase, and converting spaces and dashes to underscores to connect words. It converts Zingbox alerts vulnerability incident in the Label field to u_zingbox_alerts_vulnerability_incident in the Name field.
      Extends table: Your new table must extend the Task configuration Item. Choose Task from the list.

   2. When done, click Submit.
4. Add custom table columns to the table.

   1. Return to the table configuration page to edit it.
      The table consists of a set of predefined table columns. You will add two custom column labels to let ServiceNow receive comments from IoT Security about security incidents and provide links to the Security Alert Details and Vulnerability Details pages.
   2. Click New at the top of the table on the Columns tab.
      In the Dictionary Entry form that appears, enter the following and then click Submit:
      Type: String
      Column label: Comments
      Column name: u_comments (automatically fills based on the label)
      Max length: 4,000 (characters)
   3. To add the next column label, click New again, enter the following, and click Submit:
      Type: URL
      Column label: Security incident
      Column name: u_security_incident (automatically fills)
   4. Because ServiceNow displays a large set of columns, it’s useful to reduce the number to those of interest. To do this, click the Zingbox alerts vulnerability incident label on the Tables page, scroll down past the table and click Show List in the Related Links section, and then click the Update Personalized List icon (

      ). Use the left and right arrows to move column labels so that only the following are in the Selected pane and then click OK.

5. Create a ServiceNow user account for XSOAR to use when connecting to ServiceNow and sending it device attributes, alerts, and vulnerabilities.

   1. Navigate to System SecurityUsers, click New, enter a user ID and password, and make sure the Password needs reset check box is cleared. Leave the other fields empty and click Submit.
      Remember the user ID and password because you will enter these later when configuring the ServiceNow instance in XSOAR.
   2. On the Users page, click the user ID of the account you just created to return to the account settings.
   3. To add roles to the user account, scroll down the page, click the Roles tab, and then click Edit. Search for the following four roles one by one and add them to the Roles List:
      rest_api_explorer (This is required so that IoT Security can connect to ServiceNow through its API.)
      u_zingbox_alerts_vulnerability_incident_user
      u_zingbox_discovered_devices_user
      web_service_admin
      If you use an existing device table whose label is not “Zingbox discovered devices”, the third role shown above will be a different name.

   4. Click Save to add the roles to the user account.
   5. On the user account settings page, click Update to save the updated settings.

   This completes the ServiceNow setup.