Recently Viewed Topics
Before You Begin
You must complete the following steps before you can use the Tenable for ServiceNow application.
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 develop > test > production model:
- Install your development instance.
- Create any modifications using update sets.
- Install the applications on a test environment and promote those update set changes for QA.
- Once QA has approved the changes, install in the Tenable apps on a production environment and apply the update sets. Depending on your development team, you may need to activate the connectors and import jobs.
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 https://docs.servicenow.com/bundle/madrid-servicenow-platform/page/product/mid-server/reference/r-MIDServer.html.
- For more information about MID Server Requirements, see https://docs.servicenow.com/bundle/madrid-servicenow-platform/page/product/mid-server/reference/r_MIDServerSystemRequirements.html#r_MIDServerSystemRequirements.
- For more information about MID Server memory needs, see https://docs.servicenow.com/bundle/madrid-servicenow-platform/page/product/mid-server/task/t_MIDServerOptionalConfiguration.html#t_MIDServerOptionalConfiguration.
Application scoping protects applications by identifying and restricting access to application files and data. For more information, see https://docs.servicenow.com/bundle/madrid-application-development/page/build/applications/concept/c_ApplicationScope.html#c_ApplicationScope.
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 https://docs.servicenow.com/bundle/madrid-platform-user-interface/page/administer/navigation-and-ui/reference/r_UI16BannerFrame.html
Tenable suggests creating individual ServiceNow users in Tenable.io/Tenable.sc for each of the instances. This can help prevent user request/api collisions of data.
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.
- Log in to Tenable.io.
- Create administrator accounts (e.g. development, test, production) dedicated for use with ServiceNow. These accounts are used by ServiceNow to connect to Tenable.io to retrieve asset data.
- Generate API Keys and save them for use with ServiceNow.
- Navigate to Settings > Access Groups.
- Click the All Assets group.
- Do one of the following:
- If the All Users toggle is enabled, do nothing.
- If the All Users toggle is disabled:
- Click the + button.
- 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.
- Log in to Tenable.sc.
- Create security manager 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 asset data.