Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Inactive Support Threads
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Software
Security Apps
ESET
Can I use OSArmor with customized HIPS rules?
Message
<blockquote data-quote="Parsh" data-source="post: 875880" data-attributes="member: 58090"><p>Yes. I have had those rules with OSArmor by the side.</p><p>However if you've disabled process execution from the wscripts and cscripts and disabled script execution itself, there's no need for these rules. You might not have the ntvdm.exe in your system. It's an old component that allows 16-bit applications on 32-bit Windows, as well as the execution of 16-bit and 32-bit DOS applications. You can disable execution of 16-bit NTVDM processes in OSArmor.</p><p></p><p>And if the script interpreters are executed from non-standard locations, OSArmor blocks them under "Suspicious Processes".</p><p>Still if you wish to set those HIPS rules, 'block a process' in either app only.</p><p>ESET's list is quite small and standard though. For RW protection, you can also refer to their <a href="https://support.eset.com/en/kb6132-configure-firewall-rules-for-eset-endpoint-security-to-protect-against-ransomware" target="_blank">FW recommendations</a> if you haven't tried yet. SysHardener also has a good general list of processes to block in FW.</p><p></p><p>W.r.t. learning mode, make sure to not indulge into any risky or suspicious activity for the time being. And do it on a system you consider clean.</p></blockquote><p></p>
[QUOTE="Parsh, post: 875880, member: 58090"] Yes. I have had those rules with OSArmor by the side. However if you've disabled process execution from the wscripts and cscripts and disabled script execution itself, there's no need for these rules. You might not have the ntvdm.exe in your system. It's an old component that allows 16-bit applications on 32-bit Windows, as well as the execution of 16-bit and 32-bit DOS applications. You can disable execution of 16-bit NTVDM processes in OSArmor. And if the script interpreters are executed from non-standard locations, OSArmor blocks them under "Suspicious Processes". Still if you wish to set those HIPS rules, 'block a process' in either app only. ESET's list is quite small and standard though. For RW protection, you can also refer to their [URL='https://support.eset.com/en/kb6132-configure-firewall-rules-for-eset-endpoint-security-to-protect-against-ransomware']FW recommendations[/URL] if you haven't tried yet. SysHardener also has a good general list of processes to block in FW. W.r.t. learning mode, make sure to not indulge into any risky or suspicious activity for the time being. And do it on a system you consider clean. [/QUOTE]
Insert quotes…
Verification
Post reply
Top