VPR Score on certain Tenable plugin records are not updated by running Tenable.io Vulnerabilities integration jobSummary After running Tenable.io Vulnerabilities integration job, the user may observe the VPR score on some Tenable plugin records is not updated. Therefore, the VPR score in the Tenable plugin records in the Service instance is inconsistent with the VPR score shown in Tenable.io console. Facts There are two major reasons that could lead to this issue. The first one is ServiceNow replies on the Tenable.io Plugin integration job to update the Tenable Plugin records. Tenable.io Vulnerabilities integration job only updates with Plugin family information but not with all Third-Party plugin entry information. The second reason is this could be a data issue on Tenable side. When VPR score gets updated on Tenable side for certain Plugin records the modification_date of that Plugin record could remain as unchanged. Because ServiceNow only updates the Plugin record on the instance when imported Plugin data has newer modification_date values, hence in this case, the VPR score may not be updated for existing Plugin records on the instance. Below is a sample Plugin data snippet showing the modification_date for the TEN-155762 plugin was on "2021-12-03T00:00:00Z". The imported VPR score is 8.5 and in the VPR section the VPR was actually updated at "2021-12-15T05:23:07Z". The Plugin update time is unchanged when VPR gets updated. So after import this Plugin record into ServiceNow the VPR score will not be updated if the existing Plugin record in ServiceNow still has the old update date/time. Release All ServiceNow instance releases Instructions Compare with the two major reasons above so users have two possible solutions here. The first solution is to always run Tenable.io Plugin integration job to import the Tenable Plugin information. Change the [Import Since] field value back to the date earlier than the modification_date of that Plugin record and rerun the job. This is to make sure all information for the Plugin record could be updated in ServiceNow instance.If the first solution can not update the VPR score for certain Plugin records, please follow above screenshot to check the Plugin information in the imported Tenable payload. If the VPR update date is newer than the Plugin modification_date value then this confirms it is a data issue in Tenable side and users should engage with Tenable support to make sure Plugin record can be updated when VPR score is getting updated.