- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-20-2022 07:33 AM
Hello,
I am tasked with setting up the Tenable Connector to sync assets from ServiceNow to Tenable. I followed the instructions on Tenable Developer site and it works but there's a "but".
In one run I can only import up to 100 asset IPs which should be okay for the daily imports but for the first one I need to raise the 100 IPs limit but can't figure it out. There's no system property or field that would carry this import limit.
Has anyone experienced this and is there a way to raise it or some other workaround?
Thank you
Patrik
Solved! Go to Solution.
- Labels:
-
Vulnerability Response
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-23-2022 02:38 AM
The limitation is on Tenable side and cannot be changed in ServiceNow. The limit is 100 IP addresses per asset. Some CIs have a couple of hundred of IPs paired with them on [cmdb_ci_network_adapter] and/or [cmdb_ci_ip_address].
Workaround:
- In the Tenable Connector record find the CMDB Outbound Map field and open the reference record
- Open the script for IPv4
- You can either comment out that part of script where you're pushing these IPs into the array (comment out the entire GlideRecord query not just one line) and you'll be left with the last part where you're pushing on the IP directly on the CI record
OR
Update the script to stop pushing the IPs when the array has 100 IPs in it
This probably shouldn't be happening in the first place but that's how we decided to deal with the issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-23-2022 02:38 AM
The limitation is on Tenable side and cannot be changed in ServiceNow. The limit is 100 IP addresses per asset. Some CIs have a couple of hundred of IPs paired with them on [cmdb_ci_network_adapter] and/or [cmdb_ci_ip_address].
Workaround:
- In the Tenable Connector record find the CMDB Outbound Map field and open the reference record
- Open the script for IPv4
- You can either comment out that part of script where you're pushing these IPs into the array (comment out the entire GlideRecord query not just one line) and you'll be left with the last part where you're pushing on the IP directly on the CI record
OR
Update the script to stop pushing the IPs when the array has 100 IPs in it
This probably shouldn't be happening in the first place but that's how we decided to deal with the issue