How a Vulnerability is mapped with the VIT Record.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited a week ago
Hi Team,
I would like to understand that, how a Vulnerability is mapped or attached with the VIT ticket/on a CI, what process or rule make this happen?
Regards,
Abz
- Labels:
-
Now Assist for SecOps
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
You have a VUL (Vulnerability) that has multiple VITs (Vulnerable Items) related/children to the Vulnerability. The reason for this parent/child is because this vulnerability can be on multiple servers, etc... in your environment. The VUL (Vulnerability) is not fully remediated until all VITs are closed/remediated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a week ago
In ServiceNow Vulnerability Response (VR), a Vulnerability Item (VIT) is typically created from a vulnerability detected on an asset by a scanner such as Tenable, Qualys, Rapid7, Wiz, etc.
The mapping works like this:
Scanner Finding
↓
Vulnerability Entry (Vulnerability Definition)
↓
Asset / CI
↓
Vulnerability Item (VIT)
