BigFix - Create Fixlet Action
  • 28 Jan 2024
  • 2 Minutes to read
  • Dark
  • PDF

BigFix - Create Fixlet Action

  • Dark
  • PDF

Article summary

BigFix - Create Fixlet Action creates and executes a BigFix Fixlet action on:

  • Assets that match the results of the selected saved query, and match the Enforcement Action Conditions, if defined or assets selected on the relevant asset page.

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

General Settings

  • Enforcement Set name (required) - The name of the Enforcement Set. A default value is added by Axonius. You can change the name according to your needs.
  • Add description - Click to add a description of the Enforcement Set. It is recommended to describe what the Enforcement Set does.
  • Run action on assets matching following query (required) - Select an asset category and a query. The Enforcement Action will be run on the assets that match the query parameters.
  • Action name (required) - The name of the Main action. A default value is added by Axonius. You can change the name according to your needs.
  • 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.

  • Use stored credentials from the BigFix Adapter - Select this option to use BigFix adapter credentials.

    When you select this option, the Select Adapter Connection drop-down is available, and you can choose which adapter connection to use for this Enforcement Action.

    To use this option, you must successfully configure a BigFix adapter connection.

Required Fields

These fields must be configured to run the Enforcement Set.

  1. Site name - The related site name for the Fixlet.
  2. Fixlet ID - The BigFix ID of the Fixlet the Enforcement Action will run.
  3. Bigfix Action Name (required) - a name for the action in the BigFix environment. The name should be the name from the fixlet action in BigFix
  4. Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Connecting Additional Axonius Nodes.

Additional Fields

These fields are optional.


If Use stored credentials from BigFix adapter is not enabled, these fields are required.

  1. BigFix Domain - The hostname or IP address of the BigFix server that Axonius can communicate with via the Port.

  2. Port - Enter the port.

  3. User Name and Password - The credentials for a user account that has the Required Permissions to fetch assets.

  4. Advanced Settings (optional) - Use to run a query by Relevance expression instead of the regular flow.
    To run by a Relevance expression in Advanced Settings

    1. Create a JSON file containing the parameters relevance (string) and fields (list of fields).

      For example:

    'relevance': "User-defined name",
    'fields': ['field1', 'field2']

    b. Upload the JSON file by clicking Choose file.

  5. Verify SSL - 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.

  6. HTTPS Proxy - Connect the adapter to a proxy instead of directly connecting it to the domain.

  • Gateway Name - Select the gateway through which to connect to perform the action.


Axonius uses the Action | BigFix Developer API.

Required Ports

Axonius must be able to communicate with the Bigfix server via the following ports:

  • TCP port 443
  • TCP port 80

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

Was this article helpful?

Changing your password will log you out immediately. Use the new password to log back in.
First name must have atleast 2 characters. Numbers and special characters are not allowed.
Last name must have atleast 1 characters. Numbers and special characters are not allowed.
Enter a valid email
Enter a valid password
Your profile has been successfully updated.