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
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
Other security for Windows, Mac, Linux
WD + ConfigureDefender set HIGH + OSA: A Match Made in Heaven?
Message
<blockquote data-quote="plat" data-source="post: 897116" data-attributes="member: 74969"><p>I use FirewallHardening. It applies block rules related to various legitimate Windows processes. Things like Powershell.ise, lsass and telnet should never be making outbound calls to any port at any time. For third-party software rules plus those of Windows processes, you could consider something like a front-end or full-fledged firewall utility (TinyWall, etc) instead.</p><p></p><p>The FWH interface has a logging feature you can enable if you want, to study any effects. But again, I don't think H_C bothers with anything non-Window-related. Never had an issue with it, myself.</p><p></p><p>For OSArmor and SysHardener, I'm less gung-ho about them now that Windows 2004 is out. The developer should be making some statements about subscription costs and changelogs so that one can make informed decisions. Until then, I've removed NVT products myself.</p></blockquote><p></p>
[QUOTE="plat, post: 897116, member: 74969"] I use FirewallHardening. It applies block rules related to various legitimate Windows processes. Things like Powershell.ise, lsass and telnet should never be making outbound calls to any port at any time. For third-party software rules plus those of Windows processes, you could consider something like a front-end or full-fledged firewall utility (TinyWall, etc) instead. The FWH interface has a logging feature you can enable if you want, to study any effects. But again, I don't think H_C bothers with anything non-Window-related. Never had an issue with it, myself. For OSArmor and SysHardener, I'm less gung-ho about them now that Windows 2004 is out. The developer should be making some statements about subscription costs and changelogs so that one can make informed decisions. Until then, I've removed NVT products myself. [/QUOTE]
Insert quotes…
Verification
Post reply
Top