Vulnerability Response: VIT impacted services not sync with the current service of the CI
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
6 hours ago
We are experiencing an issue in Vulnerability Response where the impacted service on a Vulnerable Item (VIT) is not being populated after recalculation. The impacted service is derived from the Related Services table (sn_vul_m2m_ci_services), which is a VR‑maintained cache populated by the service‑impact recalculation logic. The affected CI has been validated to be correct in CMDB: it is linked to a valid Application Service, the service‑derivation logic (CIUtils().servicesAffectedByCI()) successfully returns a service, and the CI now has recent scan data with the last scan date being today, meaning it fully meets the 90‑day scan eligibility requirement.
As part of troubleshooting, we explicitly reset the Discovered Item (sn_sec_cmn_src_ci) field has_impacted_services to pending to re‑queue the CI for processing. We also deleted existing or stale entries in the sn_vul_m2m_ci_services table for the CI to ensure a clean recalculation, then ran both the OOTB “Set related CI services for VI” job and our wrapper job “Adecco – Refresh VUL Services,” which uses the same BusinessServiceUtil logic. Despite these steps, the CI remains stuck in has_impacted_services = pending after the job runs, and no new record is written to sn_vul_m2m_ci_services.
