Contents x
    Kenna - Replace Tag in Assets
    • 22 Sep 2024
    • 1 Minute to read
    • Print
    • Dark
      Light
    • PDF
    Contents

    Kenna - Replace Tag in Assets

    • Updated on 22 Sep 2024
    • 1 Minute to read
    • Print
    • Dark
      Light
    • PDF
    Article summary

    Kenna - Replace Tag in Assets replaces Kenna tags for each of the entities that are the result of the saved query supplied as a trigger (or devices selected in the asset table).

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

    Note:

    General Settings

    • 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.

    Required Fields

    These fields must be configured to run the Enforcement Set.

    • Use stored credentials from the Kenna adapter (required, default: False) - Select this option to use the first connected Kenna Security Platform adapter credentials.
      NOTE
      • To use this option, you must successfully configure a Kenna Security Platform adapter connection.
      • The user name and the password used for the adapter connection must have the required permissions to replace tags.
    • New tag name (required) - The new name of the tag.
    • Tag to replace (required) - The old name of the tag.
      NOTE
      • Only one tag can be replaced at a time.

    Additional Fields

    These fields are optional.

    • Kenna Security Platform URL - The URL for the Kenna Security Platform admin panel. This may be a default domain or a company specific URL.

    • API Token - Specify your account API key or an API token you have created.

    • 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.

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

    Was this article helpful?
    What's Next