- 23 Mar 2023
- 2 Minutes to read
- Print
- DarkLight
- PDF
BigFix - Remove Asset
- Updated on 23 Mar 2023
- 2 Minutes to read
- Print
- DarkLight
- PDF
BigFix - Remove Asset removes assets from 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.
- A query only returns results for the asset type it was created for.
- Not all asset categories are supported for all Enforcement Actions.
- See Actions supported for Activity Logs and Adapter Fetch History Modules
- See Actions supported for Vulnerabilities.
- See Actions supported for Software.
- 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 Action Conditions - Toggle on to enter a condition statement. See Configuring Enforcement Action Conditions to learn more about condition 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 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.
- Instance Name - 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.
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 fetch assets.
Advanced Settings (optional) - Use to run a query by Relevance expression instead of the regular flow.
To run by a Relevance expression in Advanced SettingsCreate 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 - 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 - Connect the adapter to a proxy instead of directly connecting it to the domain.
- Tunnel Name - For Axonius-hosted (SaaS) deployments. Select the tunnel through which to connect to perform the action.
APIs
Axonius uses the Action | BigFix Developer API.
Required Ports
Axonius must be able to communicate with the Bigfix server via the following ports:
- 52311 (default port)
For more details about other Enforcement Actions available, see Action Library.