Skip to main content

ServiceNow Integration for CMDB and Incident Creation

Alex Patnick avatar
Written by Alex Patnick
Updated this week

Faddom can be integrated with ServiceNow to populate the CMDB database with your application maps and any servers not already showing that Faddom discovers. The standard data that will be imported for each server includes -

  • Hostname

  • IP address

  • OS information

  • Dependencies

  • Software

  • CVEs

  • List of the Application Maps to which the servers belong

In addition, specific information per data source is also included

AWS

Account ID

Instance ID

Instance Name

Instance Type

Region

Subnet ID

Availability Zone

Azure

Region

Resource Group

Subscription ID

VM ID

VM Name

VM Size

GCP

Instance ID

Instance Name

Instance Type

Project ID

Region

Nutanix

Host Name

VM Primary IP

Prism Central IP

VMWare

VM Name

VM Primary IP

Virtualization Host

vCenter Server

Creating ServiceNow Incidents From Faddom

You can push Faddom alerts to ServiceNow to create incidents based on predefined criteria within the Faddom UI. For detailed instructions on how to do this, please refer to the ServiceNow section of our Notifications guide.

Integrating Faddom Data Into ServiceNow

Prerequisites

  1. Two plugins are required. The majority of customers will already have these, but if not, please be aware that there may be additional costs/licensing from ServiceNow, you can find these under Plugins in the Application Menu

    1. com.snc.cloud.api

    2. vulnerability response

  2. In the left menu, search for Tables under System Definition, then search for Software Instance table then select the Application Access tab. Ensure the Can Create and Can Update checkboxes are selected and saved


  3. Search for Scripts - Background in the right menu, then run gs.invalidateCache() and select Global Scope

  4. It may be necessary to have a mid-server setup to ensure Faddom can communicate with your ServiceNow Instance. For further information, you can see the ServiceNow Mid Server documentation

  5. The actions below can only be performed by a user with the Admin role in the target ServiceNow instance

  6. You need the appropriate Update Sets and XML files at the bottom of this article

Procedure

  1. Login into ServiceNow with your admin credentials

  2. In the left navigation pane, search for Update Sets.

  3. Click on Retrieved Update Sets under the System Update Sets module.

  4. Scroll down to the bottom and click on Import Update Sets from XML. For more information see the ServiceNow documentation on Update Sets

    Import_links.png

  5. Upload the XML file Faddom Integration App.xml and click Upload

  6. Repeat for the Faddom Update Sets.xml and Faddom Update Sets 2.xml in order.

  7. Locate the imported update set in the list of retrieved update sets. Search for Faddom

  8. Click on each update set in turn to open it. ​

  9. Click on Preview Update Set in the top left or right

  10. You will encounter some errors regarding external data; these can be resolved by selecting all the options, then going to Actions > Accept remote update sets

  11. After previewing, click on Commit Update Set on the top right or left bottom

    Commit.png

  12. If any other conflicts appear, resolve them before proceeding.

  13. Click Commit Update Set to apply the changes to the instance

  14. Wait for the commit process to complete

  15. Import the XML files by going to CI Identifier table and right-clicking on a column and selecting Import XML. Do this for all the XML files

    1. Switch the scope to Faddom (if not already)

    2. Right-click on any column header, select Import XML, and import XML3

    3. Switch the scope back to Global ​

    4. Right-click on any column header, select Import XML, and import the following files: XML1, XML2, XML4, XML5, XML6, XML7, XML8 and XML9
      ​​

  16. In the left navigation pane, search for Studio​

  17. Click on Studio under the System Applications module. A new tab opens.

  18. Search for Faddom Application

  19. Scroll down and select Faddom Rest APIs.

  20. Under the Authentication tab, click the magnifying glass icon next to Basic Auth Profile.

  21. Create a local or LDAP user in Faddom for the integration. This can be done by following our guide, How To Setup User Access

  22. In the newly opened window, enter your username and password

  23. Next, you will see the different HTTP Methods that Faddom is importing, you will need to open each one to amend the endpoint, which should be the IP address of your Faddom server (by default it's 0.0.0.0)

    1. If you need to use a MidServer, you will need to select it per job under HTTP Request

  24. After updating it, you can test the HTTP Method by clicking on the ‘Test’ button under Related Links

    HTTP.png

  25. Once all the HTTP methods are working fine and returning the HTTP Status code of 200, move to the next step. If you have any other issues, see the Troubleshooting section

  26. Look for Delete Jobs under Faddom Application

  27. ​Schedule each job to run in the below order. This is needed to ensure the latest data in Faddom is populated correctly in ServiceNow

  28. Once all jobs are scheduled, look for Studio in the Application Menu

  29. This will open up your Studio and you can search for the Faddom Application

  30. Navigate to Faddom RestAPIs at the bottom

  31. To import all the data and schedule the jobs, navaigate to Scheduled Data Import.

  32. To run the data import automatically on a schedule, navigate to the Schedule Data Imports, and enter each job and set it to run in the order below. The first four jobs can be run at the same time, while the second four should be scheduled for later (we recommend at least one hour gap). Please make sure the timezone is the same as the one above for the delete jobs (see point 27).

    1. Faddom Get Servers Job

    2. Faddom Get Software Job

    3. Faddom CVE Import

    4. Faddom Application Service Job

    5. Faddom Server Software Relationship Import

    6. Faddom CVE Software relation

    7. Faddom Server to Server Job

    8. Faddom Application to Server Job

Viewing The Data

  1. Search for Faddom in the Application Navigator.

  2. You will see the links to all the related tables under the Faddom Application Menu.

  3. You then select the table you are interested in seeing

  4. Once the table loads you can select individual objects to see detailed information

  5. For example, to see your Faddom Application Maps, you select Applications and you will see a list. You can then select the Show Dependency View to see the map in ServiceNow (opens a new tab).

Troubleshooting

If your HTTP methods are returning an SSL certificate error, you can change the following under System Property > Set com.glide.communications.httpclient.verify_hostname to False

However, this is not recommended by ServiceNow, and the other option is to install a self-signed SSL certificate on the Faddom server. You can do this by following our guide on Changing the Faddom server SSL certificate

Update Sets and XML Files

Attachment icon
Did this answer your question?