Before You Begin

You must complete the following steps before you can use the Tenable for ServiceNow application.

In ServiceNow

Tenable suggests you work with your internal ServiceNow Administrator or ServiceNow Consultant to help setup the apps and to follow ServiceNow’s process for development which uses a development > test > production model:

  • Install your development instance and tune as necessary.
  • Create any modifications using update sets.
  • Install the applications on a test environment and promote those update set changes for quality assurance in your test environment.
  • Once approved in your test environment, install the Tenable apps on a production environment and apply the update sets.

Note: You need unique credentials for each ServiceNow environment.

ServiceNow MID Server

The ServiceNow MID Server application facilitates communication and movement of data between the platform and external applications, data sources, and services. There can be several MID servers in an environment with some dedicated for development/testing and others dedicated to production. If your Tenable.sc resides behind a firewall on your internal network, you must use the MID server to access its data.

  • For more information about the ServiceNow MID server, see the MID server section in the ServiceNow documentation.
  • For more information about MID Server Requirements, see the MID server system requirements in the ServiceNow documentation.
  • For more information about MID Server memory needs, see the Set the MID Server JVM memory size section in the ServiceNow documentation.

ServiceNow Scoped Application

Application scoping protects applications by identifying and restricting access to application files and data. For more information, see the Application Scope section in the ServiceNow documentation.

Enabling the Application picker under the developer tab in the ServiceNow UI configuration menu simplifies the Tenable for ServiceNow application configuration. For more information, see the System settings for the user interface (UI) section in the ServiceNow documentation.

In Tenable

Tenable requires creating individual ServiceNow users in Tenable.io/Tenable.sc for each of your ServiceNow instances. This helps prevent rate limiting, data collision, etc.

Examples:

  • sn_dev
  • sn_test
  • sn_prod

By segmenting the users you can also limit the amount of data used in your development and test environments. In Tenable.io, you can set up an Access Group and limit the data to specific assets to simplify the import and testing of data. In Tenable.sc, you can create a query that limits the data presented to the development and test users. To determine the best dataset to use for your development and test environments, speak with your Tenable administrator. They can also help you ensure ServiceNow displays the best data by setting up appropriate scan cadences.

Create Tenable.io API keys

Note: You must create unique API keys for use with ServiceNow.

  1. Log in to Tenable.io.
  2. Create administrator accounts (e.g. development, test, production) dedicated for use with ServiceNow. These accounts are used by ServiceNow to connect to Tenable.io retrieve asset data.
  3. Generate API Keys and save them for use with ServiceNow.
  4. Navigate to SettingsAccess Groups.
  5. Click the All Assets group.
  6. Do one of the following:
    • If the All Users toggle is enabled, do nothing.
    • If the All Users toggle is disabled:
      1. Click the + button.
      2. Add the ServiceNow users you created in step 2.

Create Tenable.sc API Users

Note: You must create unique API users for use with ServiceNow.

  1. Log in to Tenable.sc.
  2. Create security manager accounts or Create security analyst accounts (e.g. development, test, production) with full access dedicated for use with ServiceNow. These accounts are used by ServiceNow to connect to Tenable.sc to retrieve data and kick off remediation scans.