Axonius - Trigger Another Set

The Axonius - Trigger Another Set action enables you to chain multiple Enforcement Sets together in a single workflow. By using this action, you can trigger another Enforcement Set to run as part of your automation process.

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

📘
Note:

Not all asset types 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.

Enforcement Set - From the dropdown menu, select the Enforcement Set that this action should trigger. The list only includes Enforcement Sets that are configured to be triggered by an event (not scheduled) and are not query-based.
Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Working with Axonius Compute Nodes.

For more details about other enforcement actions available, see Action Library.

Updated 4 days ago