Autoclose Vulnerable items on Retired CIs
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-24-2022 04:57 PM
We just upgraded to VR version 15, where autoclose retired CIs is a checkbox, which we have checked. However, we changed some CIs to retired state and their vulnerable items have not closed after multiple days. Is there somewhere in VR we can look to show why this feature is not working?
Thanks,
Andrew
- Labels:
-
Vulnerability Response
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-24-2022 06:02 PM
Hi,
Which column in cmdb you using to mark asset retired?
Thanks,
Shivam

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-25-2022 01:10 AM
Hello Andrew,
I believe you are following the below procedure/configuration steps
Configuration steps-
- Navigate to Vulnerability Response > Auto-Close Configuration > Configuration Item Lifecycle.
- To automatically close vulnerable items associated with the retired CIs, select the Auto-close VIs linked to retired CIs check box.
- Select Update.
- Note: If a CI is already retired before the Auto-close VIs linked to retired CIs option is enabled, VIs are created only for new detections from scanners. The state of these VIs is Closed and the substate is CI Decommissioned.
-
You cannot reopen VIs whose state is CI decommissioned, using the Reopen or Bulk Edit options.
For more info, Please see this Automatically close vulnerable items related to retired CIs
Please Mark ✅ Correct/helpful, if applicable, Thanks!!
Regards
Sulabh Garg
Regards
Sulabh Garg

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-25-2022 01:30 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-25-2022 11:23 AM