IP Address Enrichment - Cisco Meraki

Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊

↑ Back to Content Index

---

This playbook checks if malicious IP address is blocked or unblocked by Cisco Meraki MX network.

Attribute	Value
Type	Playbook
Solution	CiscoMeraki
Source	View on GitHub

Logic App Connectors

This playbook uses 2 Logic App connectors / built-in actions:

Connector / Action	Type	Connections	Actions
azuresentinel	Managed	1	2
MerakiConnector	Custom	1	4

Action parameters (URLs, paths, function IDs)

azuresentinel (Managed)

Action	Method	Endpoint	Other
Add_comment_to_incident	post	/Incidents/Comment	—
Entities_-_Get_IPs	post	/entities/ip	—

MerakiConnector (Custom)

Action	Method	Endpoint	Other
Get_Network_Appliance_Firewall_L3_Firewall_Rules	get	/networks/@{encodeURIComponent(items('For_each_Network')?['id'])}/appliance/firewall/l3FirewallRules	—
Get_Network_Appliance_Firewall_L7_Firewall_Rules	get	/networks/@{encodeURIComponent(items('For_each_Network')?['id'])}/appliance/firewall/l7FirewallRules	—
Get_Networks	get	/organizations/@{encodeURIComponent(body('Filter_Organization')?[0]?['id'])}/networks	—
Get_Organizations	get	/organizations	—

Additional Documentation

📄 Source: IP-Address-Enrichment/readme.md

Cisco Meraki IP Address Enrichment Playbook

Summary

When a new Microsoft Sentinel incident is created, this playbook gets triggered and performs the below actions:

1. Fetches a list of potentially malicious IP addresses.
2. For each IP address in the list, checks if the IP address is blocked by L3 firewall rule or L7 firewall rule in MX network.

• If IP address is part of both L3 firewall rule and L7 firewall rule but not blocked by either of the rules, then Incident Comment is created saying IP address allowed by firewall.
• If IP address is part of either L3 firewall rule or L7 firewall rule and blocked by the rule, then Incident Comment is created saying IP address is blocked.
• If IP address is not part of either L3 firewall rule or L7 firewall rule, then Incident Comment is created saying IP address not found in any rule.

Pre-requisites for deployment

1. Deploy the Cisco Meraki Custom Connector before the deployment of this playbook under the same subscription and same resource group. Capture the name of the connector during deployment.
2. Cisco Meraki API Key should be known to establish a connection with Cisco Meraki Custom Connector. Refer here
3. Organization name should be known. Refer here

Deployment Instructions

1. Deploy the playbook by clicking on the "Deploy to Azure" button. This will take you to deploy an ARM Template wizard.

2. Fill in the required parameters for deploying the playbook.

Parameter	Description
Playbook Name	Enter the playbook name without spaces
Cisco Meraki Connector name	Enter the name of Cisco Meraki custom connector without spaces
Organization Name	Enter organization name

Post-Deployment Instructions

a. Authorize API connection

• Once deployment is complete, go under deployment details and authorize Cisco Meraki connection.

1. Click the Cisco Meraki connection
2. Click Edit API connection
3. Enter API Key
4. Click Save

b. Configurations in Sentinel

• In Microsoft sentinel analytical rules should be configured to trigger an incident with IP addresses.
• Configure the automation rules to trigger the playbook.

Playbook steps explained

When Microsoft Sentinel incident creation rule is triggered

Captures potentially malicious or malware IP addresses incident information.

Entities - Get IPs

Get the list of IPs as entities from the Incident.

Check if Organization exists

• If organization name exists in list of organizations associated with the account, then get list of networks associated with the organization.
• If organization name does not exist, then terminate with the error that organization not found.

For each malicious IP received from the incident

• Checks if the IP address is part of L3 firewall rule or L7 firewall rule in MX network.
  • If IP address is part of both L3 firewall rule and L7 firewall rule but not blocked by either of the rules, then Incident Comment is created saying IP address allowed by firewall.
  • If IP address is part of either L3 firewall rule or L7 firewall rule and blocked by the rule, then Incident Comment is created saying IP address is blocked.
  • If IP address is not part of either L3 firewall rule or L7 firewall rule, then Incident Comment is created saying IP address not found in any rule.
• Add incident Comment from all the cases.

Incident comment

---

Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊

↑ Back to Playbooks · Back to CiscoMeraki