Contents x
    Cisco Meraki - Update Client Policy
    • 01 Jan 2025
    • 2 Minutes to read
    • Print
    • Dark
      Light
    • PDF
    Contents

    Cisco Meraki - Update Client Policy

    • Updated on 01 Jan 2025
    • 2 Minutes to read
    • Print
    • Dark
      Light
    • PDF
    Article summary

    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:

    Required Fields

    These fields must be configured to run the Enforcement Set.

    • 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 Cisco Meraki adapter - Select this option to use credentials from the adapter connection. By default, the first connection is selected.
      • When you select this option, the Select Adapter Connection drop-down becomes available. Select the adapter connection to use for this Enforcement Action.
      Note:
      To use this option, you must successfully configure a Cisco Meraki adapter connection.

    • Compute Node - 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.

    • Device Policy - Select a Device Policy. The following policies are available, 'whitelisted', 'blocked', 'normal', 'group policy'.
    • Policy Name - Enter a Policy Name.

    Connection and Credentials

    When Use stored credentials from the adapter is toggled off, some of the connection fields below are required to create the connection, while other fields are optional.

    • CiscoMeraki Domain - The full URL of the Cisco Meraki server.
    • API Prefix and API Key - If necessary, include how these are generated or obtained.
    • VLAN Exclude List - Enter a list of VLANs from which devices are not fetched.
    • Exclude No VLAN Clients - Select to not fetch devices which are not associated with a VLAN.
    • SSID Exclude List - Specify a comma-separated list of SSIDs.
    • 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.

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

    Was this article helpful?
    What's Next