As you can see in IDS event section few threats session are allowing, so just wanted to know more about how we can prevent to such threat, it should be blocked by default from the meraki side, but session is allowing from source IP is not our Lan subnet & from where its making session with our MX IP that i am not able to understand. could please help to understand to flow so that i can handle this type case itself.
My corporate office is implementing some new threat detection service throughout our organization, and I need to allow a few ips so they won't get blocked by the Meraki Firewall. I know how to do this on my ASA, but I can't seem to figure it out on our MX64 and MX84. Any help is appreciated.
Feb 21 6:25:34 IDS Alert 98.195.67.12:500 77.231.32.146:500 Allowed SERVER-WEBAPPZyxel unauthenticated IKEv2 command injection attempt
Feb 21 6:25:34 IDS Alert 98.195.67.12:500 77.231.32.146:500 Allowed SERVER-WEBAPPZyxel unauthenticated IKEv2 overflow attempt
Feb 21 6:00:16 IDS Alert 98.194.65.92:500 77.231.32.146:500 Allowed SERVER-WEBAPPZyxel unauthenticated IKEv2 command injection attempt
Feb 21 6:00:16 IDS Alert 98.194.65.92:500 77.231.32.146:500 Allowed SERVER-WEBAPPZyxel unauthenticated IKEv2 overflow attempt