Kandji - Update Device Blueprint

Article Summary

Share feedback

Thanks for sharing your feedback!

Kandji - Update Device Blueprint updates the Kandji blueprint of device assets for:

Assets that match the results of the selected saved query, and match the Enforcement Action Conditions, if defined or assets selected on the relevant asset page.

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

General Settings

Enforcement Set name (required) - The name of the Enforcement Set. A default value is added by Axonius. You can change the name according to your needs.
Add description - Click to add a description of the Enforcement Set. It is recommended to describe what the Enforcement Set does.
Run action on assets matching following query (required) - Select an asset category and a query. The Enforcement Action will be run on the assets that match the query parameters.
- A query only returns results for the asset type it was created for.
- Not all asset categories are supported for all Enforcement Actions.
  - See Actions supported for Activity Logs, Adapter Fetch History and Asset Investigation Modules
  - See Actions supported for Vulnerabilities.
  - See Actions supported for Software.
Action name (required) - The name of the Main action. A default value is added by Axonius. You can change the name according to your needs.
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 the Kandji Adapter - Select this option to use connected adapter credentials.
- When you select this option, the Select Adapter Connection drop-down is available, and you can choose which adapter connection to use for this Enforcement Action.

Note:

To use this option, you must successfully configure a Kandji adapter connection.

These fields must be configured to run the Enforcement Set.

New Blueprint ID - The ID of the Kandji blueprint to apply to the device.
Instance Name - The Axonius node to use when connecting to the specified host. For more details, see Connecting Additional Axonius Nodes.

These fields are optional.

Tunnel Name - For Axonius-hosted (SaaS) deployments. Select the tunnel through which to connect to perform the action.

If Use stored credentials from the Salesforce Adapter is disabled, these fields are required:

Host Name or IP Address - The host name or the IP address of the Kandji server.
API Token - The API token received from Kandji.
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.
HTTPS proxy - Connect the adapter to a proxy instead of directly connecting it to the domain.
HTTPS proxy User Name - The user name to use when connecting to the server using the HTTPS Proxy.
HTTPS Proxy Password - The password to use when connecting to the server using the HTTPS Proxy.

Use the scheduling options to execute Enforcement Actions on specific dates and times. You can also configure repeat schedules.

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

Was this article helpful?

Table of contents