Create ServiceNow Asset
  • 13 Sep 2022
  • 7 Minutes to read
  • Dark
    Light
  • PDF

Create ServiceNow Asset

  • Dark
    Light
  • PDF

The Create ServiceNow Asset action creates an asset in ServiceNow for each entity retrieved from the saved query supplied as a trigger (or from the entities selected in the asset table).

To configure the Create ServiceNow Asset action, from the Action Library, click Manage CMDB Assets, and then click Create ServiceNow Asset.

Connection Settings

  1. Use stored credentials from the ServiceNow adapter (required, default: False) - Select this option to use the first connected ServiceNow adapter credentials.
    NOTE
    To use this option, you must successfully configure a ServiceNow adapter connection.
  2. ServiceNow domain (optional, default: empty) - URL for the ServiceNow admin panel.
    NOTE
    If Use stored credentials from the ServiceNow adapter is disabled, this field is required.
  3. User name and Password (optional, default: empty) - To connect to ServiceNow, you will need to create a user with action privileges.
    NOTE
    If Use stored credentials from the ServiceNow adapter is disabled, these fields are required.
  4. Client ID and Client Secret (optional) - The OAuth Client ID and Client Secret for OAuth access to ServiceNow. Refer to OAuth 2.0 with Inbound REST for full details on how to obtain the OAuth Token.
  1. Refresh Token - When using the OAuth method of authentication, enter the value of the Refresh Token issued by a ServiceNow instance.
  2. Verify SSL - Select whether to verify the SSL certificate of the server against the CA database inside of Axonius. For more details, see SSL Trust & CA Settings.
  3. HTTPS Proxy (optional) - Connect the adapter to a proxy instead of directly connecting it to the domain.

Action Settings

  1. CMDB CI table name (optional, default: cmdb_ci_computer) - Specify the table that the CI will be created in.

    • If supplied, Axonius will create the CI in the specified table.
    • If not supplied, Axonius will create the CI in cmdb_ci_computer table.
  2. Additional fields (optional, default: empty) - Specify additional fields to be added as part of the ServiceNow asset as key/value pairs in a JSON format. For example: {"field1": "value1", "field2": "value2"}.

    • If supplied, Axonius will add the specified fields and values to the created asset in ServiceNow. If one of the specified fields is invalid, the request might fail.
    • If not supplied, Axonius will not add any additional fields to the created asset in ServiceNow.
  3. Do not map default Axonius fields (required) - Select whether to map the set of default Axonius fields to the ServiceNow asset.

    • If enabled, default Axonius fields will not be mapped to the ServiceNow asset.
    • If disabled, default Axonius fields will be mapped to the ServiceNow asset. For details, see Default Field Mapping.
  4. Map Axonius fields to ServiceNow fields (optional) - Use the Field Mapping Wizard to map Axonius fields to fields in ServiceNow. In this way you can transfer data found in Axonius into ServiceNow. The wizard shows you which fields exist on the Axonius system, allowing you to map them easily.

    NOTE
  5. Use IdentifyReconcile API endpoint to create computer (optional)

    • If supplied, the asset will be created in ServiceNow via the Identification and Reconciliation (IdentifyReconcile) API. The supplied value will be used as the source for the new created asset.
      • The Identification and Reconciliation (IdentifyReconcile) API uses the Identification and Reconciliation engine (IRE) to minimize creation of duplicate Configuration Items (CIs) and to reconcile CI attributes by only accepting information from authorized sources when updating the Configuration Management Database (CMDB).
      • It is recommended to use ‘Axonius’ as the source value.
    • If not supplied, the asset will be created in ServiceNow via the Table API, and the CMDB will be updated directly.
  6. Use first IP address only (required) - Select whether the first IP address to be added to the ServiceNow asset.

    • If enabled, only the device's first IP address will be added to the ServiceNow asset.
    • If disabled, all the device's IP addresses will be added to the ServiceNow asset.
  7. IP addresses delimiter (optional, default: /) - Specify the delimiter to separate between multiple IP addresses added to the ServiceNow asset.

    • If supplied, the specified delimiter will be used to separate between multiple IP addresses added to the ServiceNow asset.
    • If not supplied, the default delimiter will be used to separate between multiple IP addresses added to the ServiceNow asset.
  8. Use first MAC address only (required, default: True) - Select whether the first MAC address to be added to the ServiceNow asset.

    • If enabled, only the device's first MAC address will be added to the ServiceNow asset.
    • If disabled, all the device's MAC addresses will be added to the ServiceNow asset.
  9. MAC addresses delimiter (optional, default: /) - Specify the delimiter to separate between multiple MAC addresses added to the ServiceNow asset.

    • If supplied, the specified delimiter will be used to separate between multiple MAC addresses added to the ServiceNow asset.
    • If not supplied, the default delimiter will be used to separate between multiple MAC addresses added to the ServiceNow asset.
  10. Create ServiceNow asset even if device's asset entities include ServiceNow (required, default: False) - Select whether to create a new ServiceNow asset even if one of the device's asset entities has been fetched from ServiceNow.

    • If enabled, an asset will be created in ServiceNow even if one of the device's asset entities has been fetched from ServiceNow.
    • If disabled, an asset will not be created in ServiceNow even if one of the device's asset entities has been fetched from ServiceNow.
  11. CIDR exclude list (optional, default: empty) - Specify a comma-separated list of CIDRs to be excluded.

    • If supplied, Axonius will not add to ServiceNow IP addresses in the IP range of the specified CIDRs.
    • If not supplied Axonius will add to ServiceNow IP addresses in any IP range.
  12. Additional fields to use by querying ServiceNow (optional) -This set of fields allows you to enrich the query data by specifying a ServiceNow table and mapping the fields in the ServiceNow table to Axonius fields. You then specify the mapping between the query table and the table where the EC will create the asset.

    Enter the requried information in the following fields:

    • Table Name - the source table for query data.

    • Axonius to source table query mapping - Define the mapping between Axonius fields and the ServiceNow source table.

      • Axonius fields - Select the Axonius fields you want to use to enrich the ServiceNow table. The fields used to query the table (e.g. using the device IP address of the Axonius field, to search the table to find an entry with that IP address).
      NOTE
      If an axonius field is missing from the mapping (i.e. a device doesn’t have this field), the query for that device will be skipped. Only the first result from each query for each device will be used (i.e. for a device, every query from ServiceNow will only have a single result).
    • Source table fields to Destination table fields mapping (optional) - Mapping from the ServivceNow source table to the destionation table fields. Define the fields in a JSON formatted file, as follows:

      {“source_table_field“: “dest_table_field“, “source_table_field_2“: “dest_table_field_2“}
      

      Reference fields from the source table will be mapped to the destination table using their “display_value“.

  13. CIDR include list (optional, default: empty) - Specify a comma-separated list of CIDRs to be included.

    • If supplied, Axonius will only use ServiceNow IP addresses in the IP range of the specified CIDRs.
    • If not supplied Axonius will add to ServiceNow IP addresses in any IP range.
  14. Additional fields to use by quering ServiceNow (optional) - This option allows you to specify an “external enrichment query“ (by specifying a ServiceNow table, and a mapping between Axonius fields to ServiceNow fields). You then specify mapping between the source table (the query table) to the destination table (the table where the EC will create the asset).

    This ServiceNow query is performed for every device the EC is run for.

    The result of the ServiceNow query is appended to the created asset (based on the mapping between the source table to the destination table).

  15. Create ServiceNow asset for each installed software (required, default: False) - Select whether to create a new ServiceNow asset for each of the devices' installed software.
    * If enabled, an asset will be created in ServiceNow also for each of the devices' installed software.
    * If disabled, an asset will be created in ServiceNow only for the device.

  16. Number of parallel requests (optional) - The maximum number of requests that can be sent to ServiceNow simultaneously. If the total number of requests is lower than the limit, only the total request count is sent.

  17. Retry count (required, default: 1) - If the action fails, Axonius will retry to execute it this many times for each device.

  18. Perform bulk insert (insertMultiple) (optional) - When checked, the assets created by the action are inserted to ServiceNow in bulk.

    NOTE
    • This option cannot be used with “Use full URL for device creation“ or “Use IdentifyReconcile API endpoint to create computer“ options.
    • When using this option, the table name configured in “CMDB CI table name“ must extend sys_import_set_row.

Default Field Mapping

When the Create ServiceNow Asset action creates an asset in ServiceNow for each of the query results entities, the asset in ServiceNow is created with a set of attributes populated based on the following mapping:

Axonius Device Field ServiceNow Attribute
Asset Name / Host Name name
Device Manufacturer manufacturer
Device Manufacturer Serial / BIOS Serial serial_number
Network Interfaces: IPs ip_address
Network Interfaces: MAC mac_address
OS Type os

Required Permissions

  • IdentifyReconcile API - The value supplied in User name must have the 'itil' or 'asset' role to use this API.

To learn more about configuring Enforcement Sets, see Configuring Enforcement Sets.


First name must have atleast 2 characters. Numbers and special characters are not allowed.
Last name must have atleast 1 characters. Numbers and special characters are not allowed.
Enter a valid email
Enter a valid password
Your profile has been successfully updated.