Thereafter the researches with a customer, we
have found that the mitigation profiles weren't
properly installed on the 3rd VAC, precisely on
the Arbor TMS box. The attacks to some IPs weren't
The issue is probably due to the fact that when we
add a new box in the Arbor cluster, we have to stop
all processing mitigations then reboot. while we
have only added a new box.
We have therefore stopped rebooting all profiles.
And the attacks are now well managed by the VAC3.
The BETA is made for this purpose: look up for small beasts...