IPS and other intrusion systems all linked and shared with other OMADA devices
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hear me out here.
Lets say my OMADA detects a flood attack from a specific IP. Then auto blocks said IP. Now what if that IP is sent to a central list on the " cloud ". Now other OMADA users routers can get that IP, and add to a block list.
Example, my OMADA network gets attacked by IP 34.23.22.13. My equipment auto blocks it and sends that IP to a global list. Joe Dirt living in Germany has his OMADA system configured to access that list, and thus pre adds that bad IP.
I'm explaining it kinda simple, and it would be more then just the type of attack I used as example.It would be anything that would benefit others by sharing it. There would need some kinda of protection to prevent "bad" OMADA users from injecting legit or good IP's. Example, little Joie getting all the GOOGLE IP's put on the block list. This can be solved by requiring XX OMADA systems to add a blocked IP. Example, it would require 130 OMADA managed networks to report the same bad IP / attack.
I feel something like this would add value to the OMADA line.
It could also be controlled if the OMADA user wants to participate, and what lists they want to be linked in. Example, Global, Asia, S-America,,, OR if someone just wants the list internal. That last one, internal, would apply to those with many sites in one OMADA controller. Example, I have 32 sites on my OMADA controller. So in my case, the attak list would cover all 32 sites connected to my controller.
