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
Hard_Configurator Tools
FirewallHardening tool
Message
<blockquote data-quote="wat0114" data-source="post: 1081952" data-attributes="member: 91306"><p>[USER=101396]@Azazel[/USER]</p><p></p><p>I think I understand your question, and it actually made me curious to view the list of LOLBins being blocked in FirewallHardening.</p><p></p><p>if you look at the list of LOLBins blocked in FirewallHardening, it can be seen that Andy has carefully chosen only those that will not break Windows functionality when they are blocked. Microsoft in their infinite wisdom has created an absolutely mind boggling myriad of rules in latest Windows versions for both inbound and outbound networking, most of which are not required for most home users. Things were so much simpler in XP days, made increasingly more complex with each Windows release since then.</p><p></p><p>As [USER=59691]@Kongo[/USER] mentions above, keeping logging enabled, especially if you perceive network breakage for something is happening, can be very useful for narrowing down the problem.</p></blockquote><p></p>
[QUOTE="wat0114, post: 1081952, member: 91306"] [USER=101396]@Azazel[/USER] I think I understand your question, and it actually made me curious to view the list of LOLBins being blocked in FirewallHardening. if you look at the list of LOLBins blocked in FirewallHardening, it can be seen that Andy has carefully chosen only those that will not break Windows functionality when they are blocked. Microsoft in their infinite wisdom has created an absolutely mind boggling myriad of rules in latest Windows versions for both inbound and outbound networking, most of which are not required for most home users. Things were so much simpler in XP days, made increasingly more complex with each Windows release since then. As [USER=59691]@Kongo[/USER] mentions above, keeping logging enabled, especially if you perceive network breakage for something is happening, can be very useful for narrowing down the problem. [/QUOTE]
Insert quotes…
Verification
Post reply
Top