I actually might change the name of the “Anti-Malware and Anti-Exploit Contextual Engine” option to Smart Window Hardening. Quite simply, the best of both worlds, but it is going to take a little bit of time. The whole point of DefenderUI Pro is to include all possible attacks and to block what actually needs to be blocked and allow what actually needs to be allowed, in other words, smart windows hardening. OSArmor includes most or all of the potential attacks, but a lot of the options are disabled because enabling these options would interfere with normal operation. SWH is quite limited in scope and only blocks certain attacks, for example there is no anti-exploit or vulnerable process mechanism that I have found. It simply breaks way too much stuff and the user is left wondering why his computer is not working properly. I have said for a very long time now that I am not a huge fan of globally and blindly blocking anything. Several people have asked about how DefenderUI Pro is different from SWH and OSArmor. These new features are only a couple of weeks old, so it is going to take some time to finish writing the rules. Guys, there are going to be blocks, that is the whole point of the beta test… at least we know the mechanism is working.
0 kommentar(er)
