CI getting created in classes other than Incomp IP identified device, Unclassed H/w and Unmatched CI

[Maloy Banerjee1]

Hi All,

I have a situation where I see CIs getting created in classes other than Incomplete IP identified device, Unclassed Hardware, and Unmatched CI.

My client's requirement is, that the integration should only pick existing CIs from ServiceNow CMDB and no new CIs should be created in any other classes apart from Incomplete IP identified device, Unclassed Hardware, and Unmatched CI.

In my case CIs are getting created in IP address and Network Adaptor class.

Is there any way to stop this?

* Note: I am running only 2 scheduled jobs - Tenable.sc Fixed Vulnerabilities Integration and Tenable.sc Open Vulnerabilities Integration

Regards,

Maloy Banerjee

[Aaron Molenaar]

Sounds also possible that auto-promote function is not working to roll uphill from records like IP or NIC to the parent CI record. Reference: https://docs.servicenow.com/bundle/vancouver-security-management/page/product/security-operations-co...

[Maloy Banerjee1 · Accepted solution]

Thanks for your reply. I got the answer from the below link.

https://docs.servicenow.com/bundle/sandiego-security-management/page/product/vulnerability-response/...

If the MAC address is available, the network adapter entry is created and related to the unclassed hardware CI. If both the IP and MAC addresses are available, the IP address CI is also created and related to the unclassed hardware CI.