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
Hard_Configurator Tools
Simple Windows Hardening
Message
<blockquote data-quote="Andy Ful" data-source="post: 904790" data-attributes="member: 32260"><p>Using Logs can be sometimes uneasy for people who are not trained. But usually, one can use the time correlation between the moment when the problem happens and the time of the blocked event. This works even when we do not know if the problem is related to ConfigureDefender, FirewallHardening, or Simple Windows Hardening. If there is no time correlation, then the problem is caused in most cases by another security application.</p><p></p><p>In the case of FirewallHardening, one has to remember that the executable from the Log has to be also on the FirewallHardening Blocklist. If not, then the Internet connection is blocked, but not by FirewallHardening. The Log in FirewallHardening shows all blocked events for outbound connections, also these events that are caused by Windows privacy settings, applications that restrict Windows telemetry, etc.</p></blockquote><p></p>
[QUOTE="Andy Ful, post: 904790, member: 32260"] Using Logs can be sometimes uneasy for people who are not trained. But usually, one can use the time correlation between the moment when the problem happens and the time of the blocked event. This works even when we do not know if the problem is related to ConfigureDefender, FirewallHardening, or Simple Windows Hardening. If there is no time correlation, then the problem is caused in most cases by another security application. In the case of FirewallHardening, one has to remember that the executable from the Log has to be also on the FirewallHardening Blocklist. If not, then the Internet connection is blocked, but not by FirewallHardening. The Log in FirewallHardening shows all blocked events for outbound connections, also these events that are caused by Windows privacy settings, applications that restrict Windows telemetry, etc. [/QUOTE]
Insert quotes…
Verification
Post reply
Top
