Importance of CMDB after VR implementation
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-11-2022 06:21 AM
I have recently read up on a lot of documents and videos on proper VR configuration prior to production deployment. A lot of it had to do with a properly configured and established CMDB. Well, my organization setup VR before even starting to mature our CMDB. We have many discrepancies with our Qualys VR data and matching with our CMDB. We have brought up to the CMDB team the importance for VR. I see it like this: we have so much good data from Qualys (IP, DNS, Hostname, Vulnerabilites, etc) and it seems the CMDB team prefers their own methods of discovery. Their discovery is still in beginning stages, so we either try to persuade them to use existing good data from Qualys, or we sit and wait until their discovery is at finished and deployed across the enterprise.
How can we get CMDB team buy-in post production deployment on using existing Qualys/VR data to mature the CMDB (as a result improving both databases, VR and CMDB).
- Labels:
-
Vulnerability Response
- 1,504 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-22-2023 08:17 PM
Hi Ganesh,
If the CI is identified using the look up rules, then the CI would not be updated. But if it is identified using IRE, then the CI fields may be updated based on the CMDB Reconciliation Rules.
Details of CI matching through VR can be found over here: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0998706
Details of CMDB Reconciliation Rules can be found over here: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0756709