Automox Actions

Actions for Automox #

  • Patch Device. Applies all available software patches to one or more devices.

  • Reboot Device. Reboots one or more devices.

Use Cases #

Below are the possible use cases for these actions:

  • Patch Device. You could patch devices that are out-of-date to mitigate potential vulnerabilities

  • Reboot Device. You could reboot devices after installing updates.

Prerequisites #

Before you can execute actions on Automox devices, you must first configure an API connection to Automox. To do this, see the instructions for creating an Automox connector in Lucidum: https://lucidum.io/docs/automox/.

Workflows #

Automox Configuration #

automox_config.png
  • Configuration Name. Identifier for the Configuration. This name will appear in the Lucidum Action Center.

  • URL. The URL of the Automox console, for example, https://console.automox.com.
  • API Key. An API Key associated with a user account that has read and write access to automox devices. From the Automox console Settings page, select the API tab to access your API keys. Then generate and copy an API key.

Create or Edit an Action #

You can create the following types of Actions for Automox:

  • Patch Device. Applies all available software patches to one or more devices.

  • Reboot Device. Reboots one or more devices.

To create an action for Automox:

  1. In the Create a New Action page, in the General step, enter:

    automox_new_action1.png
    • Action Type. Select Automox from the pulldown options. You can specify which action (patch device or reboot device) later in these steps.

    • Configuration Name. Select an action configuration from the pulldown options.

    • Action Name. Identifier for the action. This name will appear in the Lucidum Action Center.

    • Description. Description of the action.

  2. Click the Next (>) icon.

  3. In the Filters page, click Configure Filters.

    filters_page.png
  4. The Build a Query page appears.

    build_query1_updated.png
  5. In the Build a Query page, you define the query for the assets or users that the action will act upon.

  6. Click Next.

  7. In the Build a Current Query page, enter the fields, operators, and values for the query. For existing actions, the query is already loaded in this page.

    build_query2_updated.png
  8. For details on creating and editing queries in Lucidum, see the section on Building Queries.

    NOTE: To optimize performance, the default time range is Current. If you need to access historical data, contact Lucidum Custom Success for help on using historical data without affecting performance.

  9. Click the Apply (page and pencil) icon.

  10. Click the Next (>) icon.

  11. In the Schedule step, enter:

    automox_new_action3.png
    • Schedule Type. Define the schedule for the action. Choices are:

      • Recurrence. Specify a frequency for the recurring schedule.

      • After Data Ingestion. The action is executed after data ingestion, which happens at least once every 24 hours and can also be triggered manually.

    • Do not trigger the action unless. Specify the number of results from Filters as a prerequisite for executing the action.

  12. Click the Next (>) icon.

  13. In the Details step, enter the following:

    automox_new_action4.png
    • Output Fields. For the records selected with the Filters field, specify the columns to display. When creating or editing the query in the Filters field, you can select these fields in the Query Results page > Edit Column button.

    • Device Action. Automox action to execute. Choices are:

      • PATCH_DEVICE

      • REBOOT_DEVICE.