Halo - Create or Update Device

Article summary

Did you find this summary helpful?

Thank you for your feedback

Halo - Create or Update Device creates or updates devices for:

Assets returned by the selected query or assets selected on the relevant asset page.

See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.

Note:

Not all asset categories are supported for all Enforcement Actions.
- See Actions supported for Activity Logs, Adapters Fetch History, and Asset Investigation modules.
- See Actions supported for Vulnerabilities.
- See Actions supported for Software.

Required Fields

These fields must be configured to run the Enforcement Set.

Action name - The name of this Enforcement Action. The system sets a default name. You can change the name.
Configure Dynamic Values - Toggle on to enter a Dynamic Value statement. See Creating Enforcement Action Dynamic Value Statements to learn more about Dynamic Value statement syntax.

Use stored credentials from HaloITSM adapter - Select this option to use credentials from the adapter connection. By default, the first connection is selected.
- When you select this option, the Select Adapter Connection drop-down becomes available. Select the adapter connection to use for this Enforcement Action.
Note:
To use this option, you must successfully configure a HaloITSM adapter connection.
Action to perform - Select between Halo - Create Device and Halo - Update Device.
Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Connecting Additional Axonius Nodes.

These fields are optional.

Client Name - The name of the Halo client to update or create the device for.
Site Name - The name of the Halo customer site on which to update or create the device.
Asset Type Name - The name of the Halo asset type.
Is Inactive - Select whether the device is active or not.
Map Axonius fields to Halo asset fields - Use the Field Mapping Wizard to map Axonius fields to fields in external systems. In this way you can transfer data found in Axonius into the external system as part of the configuration of relevant enforcement actions. The wizard shows you which fields exist on the Axonius system, allowing you to map them easily. For details, see Axonius to External Field Mapping.

Host Name or IP Address - The hostname or IP address of the HaloITSM server.
User Name and Password - The credentials for a user account that has permission to fetch assets.
Application Client ID - The Client ID of the application that is requesting to authenticate the user.
Tenant - Used with hosted solutions of Halo to specify the tenant in the URL.
Verify SSL (optional) - 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.
HTTPS Proxy (optional) - Connect the adapter to a proxy instead of directly connecting it to the domain.
HTTPS Proxy User Name (optional) - The user name to use when connecting to the server using the HTTPS Proxy.
HTTPS Proxy Password (optional) - The password to use when connecting to the server using the HTTPS Proxy.

Gateway Name - Select the Gateway through which to connect to perform the action.

Axonius uses the Halo REST API.

Axonius must be able to communicate via the following port:

The stored credentials, or those provided in Connection and Credentials, must have permission to perform this Enforcement Action.

For more details about other Enforcement Actions available, see Action Library.

Was this article helpful?

Table of contents