Cisco Meraki - Update Client Policy
- 16 Mar 2023
- 1 Minute to read
- Print
- DarkLight
- PDF
Cisco Meraki - Update Client Policy
- Updated on 16 Mar 2023
- 1 Minute to read
- Print
- DarkLight
- PDF
Article Summary
Share feedback
Thanks for sharing your feedback!
Cisco Meraki - Update Client Policy updates the Client Policy in Cisco Meraki for each of the entities that are the result of the saved query supplied as a trigger (or devices selected in the asset table).
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, Adapter 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
These fields must be configured to run the Enforcement Set.
- Device Policy (optional) - Select a Device Policy. The following policies are available, 'whitelisted', 'blocked', 'normal', 'group policy'.
- Policy Name (optional) - Enter a Policy Name.
For more details about other Enforcement Actions available, see Action Library.