Summary:
We recently implemented SecOps / Vulnerability Response integrated with our Tenable instance (working great!)
Our Info Security teams run scans only once a month, so they remain static unless you click the ‘Rescan’ UI action from ServiceNow, then it kicks off a scan in Tenable for that plugin (also works great)
We noticed when we installed the module, it came with these 2 subflows ‘'Rescan Vulnerable Item' and 'Rescan Vulnerability’’
Our thought was we could automate the rescan instead of forcing the user to hit the ‘Rescan’ button. We were thinking of maybe after the linked Change record is closed, we could utilize one of these flows to automatically kick off the Tenable rescan, so that the next day when our VIT import runs, it would auto close out the VIT (if they did the work right and remediated the VIT).
