Tenable.io Asset Integration for IoT devices

[swathibodempudi]

Did any one work on Tenable.io Asset integration for getting IoT inventory into Snow.

[cloudops]

Yes, integrating Tenable.io with ServiceNow for IoT inventory is possible. Here are the general steps:

1. **Set up Tenable.io**: First, you need to set up your Tenable.io account and configure it to scan your network for IoT devices.

2. **Create an API Key in Tenable.io**: You will need this to connect Tenable.io with ServiceNow.

3. **Install Tenable.io Integration App in ServiceNow**: ServiceNow provides a Tenable.io Integration app that you can install from the ServiceNow Store. This app provides out-of-the-box integration with Tenable.io.

4. **Configure Tenable.io Integration App**: After installing the app, you need to configure it. This includes entering the API Key you created in Tenable.io and setting up the data import schedule.

5. **Import Data**: Once the app is configured, you can start importing data from Tenable.io into ServiceNow. The data will be stored in the CMDB and can be used for asset management.

6. **Set up IoT Asset Management**: With the data imported, you can set up IoT Asset Management in ServiceNow. This includes creating asset models for your IoT devices and setting up asset lifecycle management.

7. **Monitor and Manage IoT Assets**: With everything set up, you can start monitoring and managing your IoT assets in ServiceNow. This includes tracking asset status, managing asset lifecycle, and generating reports.

For asking ServiceNow-related questions try this :
For a better and more optimistic result, please visit this website. It uses a Chat Generative Pre-Trained Transformer ( GPT ) technology for solving ServiceNow-related issues.
Link - nowgpt.ai

[swathibodempudi]

Thank you for your response.

we have Tenable Vulnerability Integration so as per Tenable vendor we enabled tenable.io for asset integration and able to transform the records created in the  Tenable.io Asset Import [sn_vul_tenable_io_asset_import] Table  to specific CI classes.  We see records end up in the following classes without having made any modifications to the connector configuration: unclassed hardware, Incomplete IP identified device and unmatched ci

Question is 

we definitely need to regroup and take a different approach to discovering these devices and properly classifying them in the CMDB as CIs, how do we do that.

Through Tenable we are getting FQDN,MAC ADDRESS, NETBIOS and HOSTNAME. There is no attributes like Serial number, Model,Device type and Manufacturer details, an unique identifier is missing to classify the data. to create a CI.