there is clearly written that the Behavior blocker is checking hashes only for the decisions. No HIPS controlling if HIPS is disabled.
The Behavior Blocker is an integral part of the Defense+ engine and is responsible for authenticating every executable image that is loaded into the memory. The Behavior Blocker intercepts all files before they are loaded into memory and intercepts prefetching/caching attempts for those files.[u][b] It calculates the hash of the executable at the point it attempts to load into the memory. It then compares this hash with the list of known / recognized applications that are on the Comodo safe list. If the hash matches the one on record for the executable, then the application is safe and the Behavior Blocker allows it to run. If no matching hash is found on the safelist, then the executable is 'unrecognized' and is run inside the auto-sandbox.[/b][/u] You will be notified via an alert when this happens.
so what is right?
please improve the help file if the BB really have HIPS controlling even HIPS is disabled.
HIPS = HIPS rules instance 1, tailorable by user, controlled by HIPS enable/disble
BB = HIPS rules instance 2 plus coded rules plus FW rules, non-tailorable by user, not controlled by HIPS enable/disable, controlled by BB enable/disable
HIPS run-time engine, on which HIPS rules run maybe = always on, maybe off if HIPS and BB is off.
Yes but the point is that the Help file does not say that. It makes it look like the Behavior Blocker is just a file reputation service that restricts things that are unknown to it.
Right. Like i posted at the beginning of this topic a half year ago. But nothing changed.
The mods and egemen said other things about HIPS and BB than we can read in the help file. If u read the help file, than the BB is just a hash-checker. See my post at the beginning of this topic.
So who is wrong? - the help file or the mods and egemen?
Can you please check and see if this is fixed with the newest version (6.3.294583.2937)? Please let us know whether it is fixed or you are still experiencing the problem.
Can you please check and see if this is fixed for the corresponding Help File for the newest version of CIS (7.0.313494.4115)? Please respond to this topic letting us know whether it is fixed or not.