Discovered Item of the latest detection for a VIT is not reflecting on the VIT table list view.

[AbhishekK212227]

Hi Team,

For one VIT there are two records under vulnerable item detection (detections) tab. 

One record is of Stale status and another record is of Open status. Moreover, both records discovered item are different.

Ideally if one status is of stale status then automatically discovered item must be updated to the new and this should show in list view but this not happening. In list view old discovered item value is showing i.e, for the stale one.

We found that one resource tag is missing in the old discovered item.

How to add the missing resource tag with script/fix script.

we need the latest Discovered item in the list view so that the assignment can be done properly using the assignment rule.
Since the newly updated tags are not available getting updates on the older Discovered item this is causing discrepancies.

could anyone help me on this with script.

Thanks..!

[andy_ojha]

Hey @AbhishekK212227 

As you might have seen, there have been some enhancements to bubble up data from the most recent open Detection, on a given Vuln Item.

That said the observation you raise here is valid - for reflecting the more up-to-date Discovered Item, on a VIT when multiple Detections are involved (spanning more than one Discovered Item).

In the meantime, would you be able to up-vote an existing Enhancement Request for this that was opened a few days ago:

• NOW Support - Idea Portal - Enhancement for more recent Disc Item to be reflected on VIT  

[AbhishekK212227]

Hi @andy_ojha 

Is there any workaround to fix this?

Will this enhancement this highlighted issue?

Moreover, when this will be implemented?

Thanks for your help.

Regards,

Abhishek

[andy_ojha]

Hey there,

While there are no planned dates for this, the Enhancement Request was updated to 'In Review', yesterday - which is a positive step forward.

Will update this thread if additional details become available.

Would also suggest opening a NOW Support Case for more technical direction and to have this tracked for your environment / implementation - and reference the Thread here, the Enhancement Request and desire to have a Fix Script or Workaround.

[Jainish Jain]

Hi @AbhishekK212227, We are also facing the same issue, we have implemented a related link that will update the record with the latest detection found. Or you can intro weekly job to do the same.