Cisco Meraki MX L7 Firewall v1.1.0

About the connector

Cisco Meraki MX L7 Firewall gives administrators complete control over the users, content, and applications on their network. This connector facilitates automated operations to fetch firewall rules, update the firewall rules etc.

This document provides information about the Cisco Meraki MX L7 Firewall Connector, which facilitates automated interactions, with a Cisco Meraki MX L7 Firewall server using FortiSOAR™ playbooks. Add the Cisco Meraki MX L7 Firewall Connector as a step in FortiSOAR™ playbooks and perform automated operations with Cisco Meraki MX L7 Firewall.

Version information

Connector Version: 1.1.0

Authored By: Fortinet

Certified: No

Release Notes for version 1.1.0

Following enhancements have been made to the Cisco Meraki MX L7 Firewall Connector in version 1.1.0:

• Updated the connector to use the Cisco Meraki MXx L7 Firewall API version v1.

Installing the connector

Use the Content Hub to install the connector. For the detailed procedure to install a connector, click here.

You can also use the yum command as a root user to install the connector:

yum install cyops-connector-cisco-meraki-mx-l7-firewall

Prerequisites to configuring the connector

• You must have the credentials of Cisco Meraki MX L7 Firewall server to which you will connect and perform automated operations.
• The FortiSOAR™ server should have outbound connectivity to port 443 on the Cisco Meraki MX L7 Firewall server.

Minimum Permissions Required

• Not applicable

Configuring the connector

For the procedure to configure a connector, click here

Configuration parameters

In FortiSOAR™, on the Connectors page, click the Cisco Meraki MX L7 Firewall connector row (if you are in the Grid view on the Connectors page) and in the Configurations tab enter the required configuration details:

Actions supported by the connector

The following automated operations can be included in playbooks and you can also use the annotations to access operations:

operation: Get Network L7 Firewall Rules

Input parameters

Output

The output contains the following populated JSON schema:

{
    "rules": [
        {
            "policy": "",
            "type": "",
            "value": ""
        }
    ]
}

operation: Update Network L7 Firewall Rules

Input parameters

{
    "rules": [
      {
        "policy": "deny",
        "type": "application",
        "value": {
          "id": "meraki:layer7/application/67",
          "name": "Xbox LIVE"
        }
      },
      {
        "policy": "deny",
        "type": "host",
        "value": "google.com"
      },
      {
        "policy": "deny",
        "type": "blacklistedCountries",
        "value": [
          "AX",
          "CA"
        ]
      }
    ]
}

Output

The output contains the following populated JSON schema:

{
    "rules": [
        {
            "policy": "",
            "type": "",
            "value": ""
        }
    ]
}

operation: Get Network L7 Firewall Rules Application Categories

Input parameters

Output

The output contains the following populated JSON schema:

[
    {
        "applicationCategories": [
            {
                "id": "",
                "name": "",
                "applications": [
                    {
                        "id": "",
                        "name": ""
                    }
                ]
            }
        ]
    }
]

Included playbooks

The Sample - Cisco Meraki MX L7 Firewall - 1.1.0 playbook collection comes bundled with the Cisco Meraki MX L7 Firewall connector. These playbooks contain steps using which you can perform all supported actions. You can see bundled playbooks in the Automation > Playbooks section in FortiSOAR™ after importing the Cisco Meraki MX L7 Firewall connector.

• Get Network L7 Firewall Rules
• Get Network L7 Firewall Rules Application Categories
• Update Network L7 Firewall Rules

Note: If you are planning to use any of the sample playbooks in your environment, ensure that you clone those playbooks and move them to a different collection since the sample playbook collection gets deleted during connector upgrade and delete.