Interested in a ServiceNow event built for developers? Registration for now[dev]26 is officially open!

IP-based Certificate Discovery - How are Certificates related to Servers(CMDB CI) in OOTB CIM?

Dinh Nguyen
Kilo Sage
Hi everyone,
I'm investigating the OOTB behavior of Certificate Inventory and Management (CIM) when running IP-based Certificate Discovery.
From my understanding, the discovery process retrieves certificate information through the TLS Port Probe and stores certificate-related data within CIM. However, I'm trying to understand how the discovered certificates are associated with the server where the certificate is deployed.
  • Does discovery collect both certificate information and server/host information?
  • Are certificates and servers stored in separate tables?
  • How does CIM relate a discovered certificate to the server where it is deployed?
  • Is there a reference field or relationship table between Certificate records and CMDB CIs?
  • Which tables/fields should be checked to verify this relationship?

Please someone help me.

Thankyou!

1 ACCEPTED SOLUTION

f I understand correctly, IP-based Certificate Discovery can discover both the certificate information and the server/host where the certificate is deployed. Also, the certificate and the server/host are stored as two separate records, right? - Yes

Does this mean that after running IP-based Certificate Discovery, deployed certificates are recorded in the Installed Certificates table, and the Server field represents the server on which the certificate is deployed? - yes, you will also have a relation created in cmdb_rel_ci table with unique certificate and server. if you click on unified map on the certificate workspace you will be able to see it. We have done customization, created a cmdb_ci field which is populating the ci on the the UC form it self. 

 

Regards, 

Pratiksha

 

View solution in original post

6 REPLIES 6

It's done automatically. If you want the CI to be present on the form then that would be the customisation. 

Thankyou so much @Pratiksha