itman 1,659 Posted August 30, 2015 Share Posted August 30, 2015 I know this has been asked before and I thought it was supposed to be incorporated into NOD32 and Smart Security by now? Appears the Endpoint versions support *.exe, etc. in target files and applications HIPS rules. I suspect Eset locked out this feature for the consumer versions. Is there anyway to unlocked this feature perhaps by XML directive command? Or, is it possible to get a copy of the Endpoint .bin file? Link to comment Share on other sites More sharing options...
itman 1,659 Posted September 2, 2015 Author Share Posted September 2, 2015 Bump! I really need this feature folks to block crypto malware downloads. I have WIN 7 Home so I can't use SRP. I have created a HIPS rule to prevent startups in susceptible directories but that doesn't protect me against scripts, .scr, and the latest variant payloads, .exx. Also, I am a bit old fashioned in that I believe in that old truism, "An ouch of prevention is worth a pound of cure." Hence, my desire to block target file writes in susceptible directories. And yes, I know what I am doing. All HIPS rules I create like this are "ask" mode. Link to comment Share on other sites More sharing options...
Administrators Marcos 5,074 Posted September 2, 2015 Administrators Share Posted September 2, 2015 Support for wildcards in HIPS rules is planned to be added in the future. Link to comment Share on other sites More sharing options...
itman 1,659 Posted September 2, 2015 Author Share Posted September 2, 2015 Support for wildcards in HIPS rules is planned to be added in the future. Pls hurry. Thank you. Link to comment Share on other sites More sharing options...
Recommended Posts