Discovered Item Source Data not updating after initial record creation w/ Tenable

[tstocking]

We are using the Tenable SC solution and have some devices with the Tenable Agent installed that are not syncing back the full source data listed in Tenable on the initial Discovered Item record creation. We confirmed that Tenable is showing us the right data (like OS). Since we can delete the discovered item, how can we force the source data to get refreshed from Tenable?

[Chris McDevitt]

I have seen this before:

https://community.servicenow.com/community?id=view_idea&sysparm_idea_id=4f60fc04db503054d58ea345ca9619d4&sysparm_idea_table=x_snc_com_ideation_idea&sysparm_module_id=enhancement_requests

Test the next upcoming VR release and see if that does not address your issue. If you look at an app's Store history, you can predict the next release time frame....

🙂

[tstocking]

Hi Chris,

I didn't see a release note specifically mentioning this and your idea submission. Do you know if it was included?

[Mike322]

Hi Chris,

We're past the 16.1 release and it still doesn't seem to work.

Our discovered item is created from a Rapid7 integration and the API is sending the updated values. The host tag field is also updated but the payload still contains faulty information. So our lookup rules still fail.

What do you suggest we do?

Kind regards,

Mike

[Chris McDevitt]

Um.... so the DI population is integration plugin-dependent. This thread is for Tenable.... and in the latest release to the Tenable plugin, they made some adjustments to how DI are updated.

You are going to need to open a ticket on this for the Rapid7 plugin / Store Application.