.png){kind=logo}
Cisco Meraki - Update Client Policy
- 30 Jun 2024
- 1 Minute to read
- Print
- DarkLight
- PDF
Cisco Meraki - Update Client Policy
- Updated on 30 Jun 2024
- 1 Minute to read
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for 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.
Note:
- 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.
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.
Required Fields
These fields must be configured to run the Enforcement Set.
- Device Policy - Select a Device Policy. The following policies are available, 'whitelisted', 'blocked', 'normal', 'group policy'.
- Policy Name - Enter a Policy Name.
For more details about other Enforcement Actions available, see Action Library.
Was this article helpful?