BigFix - Remove Asset

BigFix - Remove Asset removes assets from BigFix for:

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.

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.

Use stored credentials from the BigFix Adapter - Select this option to use the BigFix connected adapter credentials.
- When you select this option, the Select Adapter Connection drop-down becomes available. Select the adapter connection to use for this Enforcement Action.
To use this option, you must successfully configure a BigFix adapter connection.

These fields must be configured to run the Enforcement Set.

Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Connecting Additional Axonius Nodes.

These fields are optional.

BigFix Domain - The hostname or IP address of the BigFix server that Axonius can communicate with via the Port.
Port - Enter the port.
User Name and Password - The credentials for a user account that has the Required Permissions to perform this action.
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

a. 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.
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.
Gateway Name - Select the Gateway through which to connect to perform the action.

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

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