Meraki

Detection rules for Cisco Meraki data sources. Each rule includes its MITRE ATT&CK mapping, impact rating, and a description of what it detects. These rules analyze events with the data type firewall-meraki, which the Cisco Meraki integration sends.

This category contains 7 detection rules.

RuleCategoryTechniqueImpact (C/I/A)
Air Marshal Rogue Access Point DetectionInitial AccessT1200 - Hardware AdditionsC:3 / I:3 / A:2
Evil Twin Access Point DetectionWireless SecurityT1557 - Adversary-in-the-MiddleC:3 / I:3 / A:1
Meraki Advanced Malware Protection AlertExecutionT1204.002 - User Execution: Malicious FileC:3 / I:3 / A:2
Meraki Client VPN Brute Force AttemptsCredential AccessT1110 - Brute ForceC:3 / I:2 / A:1
Meraki IDS High Priority Intrusion AlertInitial AccessT1190 - Exploit Public-Facing ApplicationC:3 / I:3 / A:2
Rogue SSID DetectionInitial AccessT1200 - Hardware AdditionsC:3 / I:3 / A:2
Wireless Intrusion AttemptsReconnaissanceT1595.002 - Active Scanning: Vulnerability ScanningC:3 / I:3 / A:2

Rule Example

Below is an example of a rule definition for Air Marshal Rogue Access Point Detection (view in repository):

# Rule version v1.0.0

dataTypes:
  - firewall-meraki
name: Air Marshal Rogue Access Point Detection
impact:
  confidentiality: 3
  integrity: 3
  availability: 2
category: Initial Access
technique: "T1200 - Hardware Additions"
adversary: origin
references:
  - https://documentation.meraki.com/General_Administration/Monitoring_and_Reporting/Syslog_Event_Types_and_Log_Samples
  - https://documentation.meraki.com/MR/Monitoring_and_Reporting/Air_Marshal
  - https://attack.mitre.org/techniques/T1200/
description: |
  Detects when Meraki Air Marshal identifies rogue access points or unauthorized SSIDs in the wireless environment. This could indicate malicious wireless infrastructure attempting to intercept traffic or perform man-in-the-middle attacks.

  Next Steps:
  1. Verify if the detected BSSID and SSID are known legitimate access points that may not be properly registered
  2. Check the RSSI value to determine proximity - higher values indicate the rogue AP is closer to your infrastructure
  3. Use wireless scanning tools to physically locate the rogue access point using the BSSID
  4. Review network traffic logs for any suspicious connections to unknown wireless networks
  5. Check if any sensitive data might have been exposed through connections to the rogue AP
  6. Consider implementing MAC address filtering or 802.1X authentication to prevent unauthorized connections
  7. Document the incident and update the wireless security policy if needed
where: |
  equals("log.eventType", "airmarshal_events") &&
  equals("log.type", "rogue_ssid_detected") &&
  exists("log.bssid") &&
  greaterOrEqual("log.rssi", -50)
groupBy:
  - lastEvent.dataSource
  - lastEvent.log.merakiType
  - lastEvent.log.bssid

Rule Details

Air Marshal Rogue Access Point Detection

Detects when Meraki Air Marshal identifies rogue access points or unauthorized SSIDs in the wireless environment. This could indicate malicious wireless infrastructure attempting to intercept traffic or perform man-in-the-middle attacks.

Evil Twin Access Point Detection

Detects evil twin attacks where a rogue access point mimics a legitimate corporate SSID to intercept wireless traffic. Meraki Air Marshal identifies spoofed SSIDs that match corporate network names but originate from unauthorized hardware.

Meraki Advanced Malware Protection Alert

Detects a malicious file disposition reported by Meraki Advanced Malware Protection (AMP), including retrospective reclassification of a previously downloaded file. A scanned download identifies the requesting client as the event origin and the remote file server as the event target; the alert therefore treats the remote server as the adversary side. Retrospective records can lack both endpoints. A disposition does not establish execution or compromise. A valid SHA-256 groups reports for the same file. When the hash is missing or malformed, the actual ingress event ID keeps that record separate; it is not treated as a file or attacker identity.

Meraki Client VPN Brute Force Attempts

Detects at least ten explicit AnyConnect VPN authentication failures within fifteen minutes from the same source IP, collector, and Meraki appliance. Connection teardown and site-to-site tunnel negotiation failures do not establish a credential failure.

Meraki IDS High Priority Intrusion Alert

Detects high and medium priority intrusion detection alerts from Meraki IDS/IPS system. These alerts indicate potential exploitation attempts, malicious traffic patterns, or known attack signatures detected by the Snort engine.

Rogue SSID Detection

Detects the legacy Air Marshal rogue SSID event, indicating an access point detected on the wired LAN. A rogue SSID does not by itself establish corporate SSID spoofing; the separate spoofing event is used for Evil Twin detection.

Wireless Intrusion Attempts

Detects the start of a wireless packet flood reported by Meraki, including the documented deauthentication packet event. The matching end-of-flood event is recovery telemetry and does not trigger a new alert.