Field mappings for VR integration
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-16-2023 09:22 AM
Hi Team,
We are integrating VR with our vulnerability scanner through custom integration. I am able to map the fields of the endpoint with OOB VIT table fields like First seen, last seen, preferred solution, SD, Description, CI, CVE, IP Address, Port, Protocol etc but still there are few fields which doesn't match with OOB fields.
My question is, do you guys recommend to create custom fields for these fields or is there any recommended way to do it? I have seen Qualys creating new tab and its fields under that tab to import the data. Do you recommend to create new fields for this custom integration as well?
If I do that, If we expect the integration with other vulnerability scanner then we end up creating lot of fields per integration.
Please suggest your expert advice.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-16-2023 10:21 AM
HI @SM16 ,
I trust you are doing great.
I would recommend that you create custom fields for the data that cannot be mapped to existing OOB VIT table fields. This will allow you to capture all the necessary data from your vulnerability scanner and store it in a structured manner within ServiceNow.
Creating a new tab with custom fields, as Qualys has done, is also a viable option. However, it may not be necessary unless you have a large number of custom fields or a complex data structure.
Regarding the concern about creating too many fields per integration, it is important to consider the scope of the integration and the data that needs to be captured. If the integration involves significantly different data structures, it may be necessary to create additional fields to accommodate the new data. However, if the data structures are similar, it may be possible to reuse existing fields.
In any case, it is important to carefully consider the design of the data model and consult with stakeholders to ensure that the solution meets their needs and is scalable for future integrations.
Was this answer helpful?
Please consider marking it correct or helpful.
Your feedback helps us improve!
Thank you!
Regards,
Amit Gujrathi
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-07-2024 12:49 PM
Interested in why a custom integration is being used versus the one provided with the VR license?