Harden Windows Security v0.5.8 #332
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The reason for this change: #331
Added BruteForceProtectionLocalNetworkBlocking
code organization
Improved GUI experience
Added toggle buttons for filtration
Added GUI element for display currently displayed items count
to match the local policy changes in version 0.5.8
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What's New
Added a new policy to the Microsoft Defender Category, called BruteForceProtectionLocalNetworkBlocking. It Extends brute-force protection coverage in Microsoft Defender Antivirus to block local network addresses.
Removed Controlled Folder Access Exclusion List display from the Compliance checking results. Its
Compliantproperty was always set toN/Asince it never participated in the final security score and its only purpose was to show the file paths that exist in the exclusion list, nothing else. The exclusions list can be viewed in the Microsoft Defender's GUI or on the command line with PowerShell, if needed. With this change, there is no longer any items in the compliance check results withN/ACompliant value, they are either True or False.Improved the auto-updating mechanism.
Changed the History for the PIN Complexity policy from 3 to 1. Related
Empty log messages that only have timestamps are no longer displayed on the console or on the GUI.
Fixed a visual issue where you would start the compliance check, then switch to another tab such as protection page, and while in there, the compliance check would finish, but after switching back to Confirmation page, the total count of the items wouldn't be shown. Related
Added 2 toggle buttons to the compliance checking page in the GUI to filter the displayed results based on Compliant/Non-Compliant status.
Added an area in the confirmation page's GUI to display the live number of displayed results. Updated in real time during filter application and keyword searches.
Overall code optimization and categorization.
Increased minimum OS build requirement from 22621.3155 to 22621.3880. As already explained numerous times throughout this repo, keeping your OS up to date is the most important thing. The main reason for this change is the new Microsoft Defender features added in this update.