- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-19-2023 05:36 PM
Hi,
I have a question about unclassified hardware. If i have a CI that has multiple DNS names or FQDN's, how is the best way to list these on a CI so that VR can match the name to a CI?
Would adding them to the DNS names for NIC's field on a network adapter be the best for this? or can you list multiple FQDN;s in the FQDN field?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-25-2023 05:24 PM
Well it doesnt but was trying to find where this would be stored and the FQDN was the only field on a CI that was close. Anyway, the answer is below from ServiceNow Support.
We do have an OOTB table that is intended to hold DNS Names, cmdb_ci_dns_name, however this table does not have a direct relation to a CI, it instead relates DNS Names to IP Addresses (many-to-many relationship) and an IP Address will have a one-to-one relation with a CI. If you also use ITOM Discovery you will find find that the table is already well-populated but you may have to manually input the DNS names for the virtual host webserver config you described in your case submission.
Looking at the features of Vulnerability Response (VR) it appears that there may be an OOTB solution for the CI Lookup Rule required to match on cmdb_ci_dns_name as the documentation refers to "DNS Name" in the list of default options, however, this may be referring to FQDN on the CI itself.
If there is not an OOTB CI Lookup Rule, fear not, you are able to script your own logic for the CI lookup where you would start from the cmdb_ci_dns_name table, and follow the relations along until you get to the CI you are looking for.
See the docs for more info on what the implementation would look like on the VR side: KB1233680 - Create a Vulnerability Response CI lookup rule - Perma Link [Public]
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-21-2023 01:17 PM
Hi Justin, how can a CI have multiple FQDN?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-25-2023 05:24 PM
Well it doesnt but was trying to find where this would be stored and the FQDN was the only field on a CI that was close. Anyway, the answer is below from ServiceNow Support.
We do have an OOTB table that is intended to hold DNS Names, cmdb_ci_dns_name, however this table does not have a direct relation to a CI, it instead relates DNS Names to IP Addresses (many-to-many relationship) and an IP Address will have a one-to-one relation with a CI. If you also use ITOM Discovery you will find find that the table is already well-populated but you may have to manually input the DNS names for the virtual host webserver config you described in your case submission.
Looking at the features of Vulnerability Response (VR) it appears that there may be an OOTB solution for the CI Lookup Rule required to match on cmdb_ci_dns_name as the documentation refers to "DNS Name" in the list of default options, however, this may be referring to FQDN on the CI itself.
If there is not an OOTB CI Lookup Rule, fear not, you are able to script your own logic for the CI lookup where you would start from the cmdb_ci_dns_name table, and follow the relations along until you get to the CI you are looking for.
See the docs for more info on what the implementation would look like on the VR side: KB1233680 - Create a Vulnerability Response CI lookup rule - Perma Link [Public]
