---
updatedAt: 2025-10-23T16:48:34.000Z
agentTools:
  projectIndex: https://docs.axonius.com/llms.txt
---

# Palo Alto Networks IoT Security - Tag assets

**Palo Alto Networks IoT Security - Tag assets** adds tags in IoT Security for:

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

See [Creating Enforcement Sets](/docs/create-ec-set) to learn more about adding Enforcement Actions to Enforcement Sets.

<Accordion title="When accessing an enforcement action using the API, you must use the backend form of field names. " icon="fa-info-circle">
  Use the [Syntax Helper](/docs/using-the-syntax-helper) to find the correct name. In the enforcement action, enable **Configure Dynamic Values** and select **Syntax Helper**.


  <Image src="https://raw.githubusercontent.com/Axonius/ax-docs-pub/refs/heads/main/img/action_center/SyntaxHelperForAPIECs.png" width="550px" />

</Accordion>

<Callout icon="📘" theme="info">
  ### Note

  - Not all asset types are supported for all Enforcement Actions.
  - See Actions supported for [Activity Logs, Adapters Fetch History, and Asset Investigation modules](/docs/creating-queries-filters#using-activity-log-adapter-fetch-history-asset-investigation-and-findings-queries-in-enforcement-actions).
  - See Actions supported for [Aggregated Security Findings](https://docs.axonius.com/docs/vulnerabilities#using-aggregated-security-findings-queries-in-enforcement-actions).
  - See Actions supported for [Software](software#using-software-queries-in-enforcement-actions).
</Callout>

## 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** *(optional)* - Toggle on to enter a Dynamic Value statement. See [Creating Enforcement Action Dynamic Value Statements](https://docs.axonius.com/docs/config-ec-conditions) to learn more about Dynamic Value statement syntax.

* **Use stored credentials from the Palo Alto Networks IoT Security (Zingbox) adapter** - Select this option to use the first connected [Palo Alto Networks IoT Security](/docs/paloaltonetworks-iot) adapter credentials.

  <Callout icon="📘" theme="info">
    Note

    * To use this option, you must successfully configure a [Palo Alto Networks IoT Security](/docs/paloaltonetworks-iot) adapter connection.
    * The user name and the password used for the adapter connection must have the required permissions to add tags.
  </Callout>

* **Tags** - The name of the new tag to add. Type the name of a tag and press **Enter**. Multiple tags can be added. To add a tag as a *key:value* pair, separate the key and value with a : (colon).

* **Compute Node**  - The Axonius node to use when connecting to the specified host. For more details, see [Working with Axonius Compute Nodes](https://docs.axonius.com/docs/connecting-additional-axonius-nodes).

## Additional Fields

These fields are optional.

<Callout icon="💡" theme="warn">

  ## Connection and Credentials

When **Use stored credentials from the adapter** is toggled off, some of the connection fields below are required to create the connection, while other fields are optional.

  * **Hostname** _(default: `https://api.kennasecurity.com`)_ - The URL for the Kenna Security Platform admin panel. This may be a default domain or a company specific URL.

  * **API Token** _(optional)_ - Specify your account API key or an API token you have created.

  * **Verify SS&#x4C;_&#x20;(Optional)_**_&#x20;(default: enabled)&#x20;_- Selects whether to verify the SSL certificate of the server against the CA database inside of Axonius.  For more details, see [SSL Trust & CA Settings](/docs/certificate-settings#ssl-trust-ca-settings). This setting is enabled by default on all new adapter settings. If you need to disable SSL verification, make sure you disable this setting._)_&#x20;

  * **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**.
</Callout>

## Required Ports

Axonius must be able to communicate with the value supplied in [Hostname or IP Address](#parameters) via the following port:

* TCP port 80

## APIs

Axonius uses the [Palo Alto Networks IoT Security](https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/iot/iot-security-api/iot-security-api-reference.pdf) API.

## Required Permissions

The credentials of the user account used to add tags must have permission to write tags to assets.

## Version Matrix

This Enforcement Action has only been tested with the versions marked as supported, but may work with other versions. Please contact [Axonius Support](mailto:support@axonius.com) if you have a version that is not listed and it is not functioning as expected.

| Version                                        | Supported | Notes |
| ---------------------------------------------- | --------- | ----- |
| Palo Alto Networks IoT Security (Zingbox) v1.0 | Yes       |       |

***

For more details about other enforcement actions available, see [Action Library](/docs/action-library).