Automox - Run Worklet
The Automox - Run Worklet action executes an Automox Worklet. This removes the need to have a domain admin account on all your systems for WMI ECS. It also allows you to leverage the recipes you already have in Automox.
NOTE
To use this action, you must successfully configure an Automox adapter connection.
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.
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
- Use stored credentials from the [ADAPTER NAME] adapter (required, default: False) - Select this option to use the first connected [ADAPTER NAME] adapter credentials.
NOTE
To use this option, you must successfully configure a [ADAPTER NAME+Link] adapter connection.
The user name and the password used for the adapter connection must have the Required Permissions to perform this action.
-
XXX (required) - The hostname or IP address of the [ADAPTER NAME] server that Axonius can communicate with via the Required Ports.
-
XXX (required) - The hostname or IP address of the [ADAPTER NAME] server.
-
User name and Password (required) - The credentials for a user account that has the Required Permissions to perform this action.
-
User name and Password (required) - The credentials for a user account that has the permissions to perform this action.
-
API Key (required) - An API Key associated with a user account that has the Required Permissions to perform this action.
-
API Key (required) - An API Key associated with a user account that has permissions to perform this action.
-
Verify SSL (required, default: False) - Choose 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, default: empty) - Connect the adapter to a proxy instead of directly connecting it to the domain.
-
HTTPS Proxy User Name (optional, default: empty) - The user name to use when connecting to the value supplied in Host Name or IP Address via the value supplied in HTTPS Proxy.
- When supplied, Axonius authenticates with this value when connecting to the value supplied in HTTPS Proxy.
- When not supplied, Axonius does not perform authentication when connecting to the value supplied in HTTPS Proxy.
-
HTTPS Proxy Password (optional, default: empty) - The password to use when connecting to the server using the HTTPS Proxy.
-
-
Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Working with Axonius Compute Nodes.
-
Additional Fields
APIs
Required Ports
Axonius must be able to communicate with the value supplied in Hostname or IP Address via the following ports:
Required Permissions
The value supplied in User name must have read access to devices.
Version Matrix
This adapter has only been tested with the versions marked as supported, but may work with other versions. Please contact Axonius Support if you have a version that is not listed and it is not functioning as expected.
| Version | Supported | Notes |
|---|---|---|
For more details about other Enforcement Actions available, see Action Library.
Updated about 11 hours ago
