Hi Oren
Great video, just a followup I think I am missing something.
I was under the impression that if you don't need a protection to not enable it, that if you enable it will launch the content inspection to, steam,parse,cmi protections, looking for traffic that might match this protection.
example: when ssl poodle vulnerability come out, We added protection for it., because the servers were vulnerable, but once the servers are patched , OS was patched, then there was no more need to keep the protection enable any more,
I think maybe my confusion might be related to performance, maybe I have been here to long and the engine has change
but I remember having a customer with worm catcher protection enable, and this was spiking up all the cpu high, because ALL http traffic was being inspected for a worm, when customer patch his window servers, against code red/nimba vulnerabilities, then we disable worm catch and his cpu went down.
thanks,
Manuel