VMware CB Cloud - Change Policy by Name
- 25 Jun 2024
- 1 Minute to read
- Print
- DarkLight
- PDF
VMware CB Cloud - Change Policy by Name
- Updated on 25 Jun 2024
- 1 Minute to read
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
VMware CB Cloud - Change Policy by Name changes the VMware Carbon Black Cloud (Carbon Black CB Defense) policy assigned to each entity that is the result of the saved query supplied as a trigger (or assets selected in the asset table).
NOTE
To use the VMware CB Cloud - Change Policy by Name action, you must successfully configure a VMware Carbon Black Cloud adapter connection.
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 - 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, Adapters Fetch History, and Asset Investigation 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 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
- Policy name (required) - Specify the policy name to be assigned to the endpoint.
Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Connecting Additional Axonius Nodes.
For more details about other Enforcement Actions available, see Action Library.
Was this article helpful?