We noticed the list for “Known Bots” seems VERY old and in our real traffic is missing a lot of common bots.
It seems to need a large update to include common recent bots.
Also “Exceptions” feature doesn’t include condition statements.
So adding a new bot as “Exceptions” is VERY dangerous because there is no way to limit it to known ASN or IP ranges or better than reverse DNS lookup(which is officially recommended to identify common bots like google, bing, yandex bots etcetera)
Also for “Known Bots” and “Spoofed Bots” if one is turned on it need the other, but both of them have no ignore for “Rule Action” and the minimum setting is “Alerts” which fills the edgio logs with often unnecessary logs.
“Ignore” should be made available “Rule Action”, especially since the settings rely on each other.
Additionally in my tests,
Bot Manager | Edgio Documentation documentation regarding
“The Spoofed Bots section does not apply to the 200+ known bots defined within the other category.”
If you test with a spoofed bing bot using
Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; bingbot/2.0; +http://www.bing.com/bingbot.htm) Chrome/116.0.1938.76 Safari/537.36
It is only detected when “other” is turned on in “Known Bots”.
So the documentation or behavior should be fixed.
On the other hand, bing bot should really not be in “other” but a seperate “Known Bots” as it is a major bot. This shows the Known Bots list is very old and needs updating.