Tenable third-party library update not updating

[danielgarner]

Is there an additional job or script that can help update the Tenable Third-Party Library records in VR? It is impacting downstream records and update, especially risk calculators off of the scanner Risk Rating.

An example: TEN-161691 was initially considered Critical from Tenable, then carried over in transforms and records within VR. That Tenable plugin was downgraded from Critical to Info after two months. This change from Tenable was never updated in the Third-Party table and maintained the incorrect Risk Rating. 

Please advise for any troubleshooting steps.

[Martin Dewit]

Take a look at your Tenable Plugin integration's date field and past integration runs for any failures for troubleshooting. There may have been a failed run that skipped a date sequence, etc. You could also walkthrough the Tenable Integration Setup Assistant to ensure every thing is set to your requirements, specifically the date fields and query filters. Just looking at the documentation, the plugins integration has a query filter. For example you could be filtering out Info severity, so it could have excluded TEN-161691 since it was downgraded to Info.

For a fix, I would back-date the Plugin integration date field to at least before TEN-161691 was created and run it. It should update/create any TPEs between then and now.