-
Notifications
You must be signed in to change notification settings - Fork 168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Suggestion]: Offer Removal of telemetry and pre-installed apps from the OS in Harden Windows Security Module #479
Comments
Related discussion |
New Feature: Introduced the ability to remove built-in apps using the Harden Windows Security module. This functionality is available on a dedicated page. The list of removable apps is stored in a JSON file, providing flexibility and extensibility. New Feature: Added a new page for managing Optional Windows Features. While the Harden Windows Security module already includes an Optional Features category in the hardening measures section, this new page allows for granular control, enabling you to fine-tune which features to enable or disable. It also includes additional optional features that can be removed. Compliance Checking Enhancement: Added support for VBScript compliance checks. Code Improvements: Implemented several code enhancements and optimizations. UI Enhancements: Updated the button styles on the ASR Rules and Unprotect pages. The new design replaces the previous animated buttons with play icons, offering a cleaner and more modern look. This PR also completes the first half of this feature request: [Suggestion]: Offer Removal of telemetry and pre-installed apps from the OS in Harden Windows Security Module #479
First half of this is already done: #506 |
Finished this PR, implemented the following 14 policies as a sub-category of the Miscellaneous category, called "Reduced Telemetry".
Windows Restricted Traffic Limited Functionality Baseline provided here https://learn.microsoft.com/en-us/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services, isn't recommended to be used at all. It disables important security functionalities. What I implemented in the Harden Windows Security module consist of 14 policies for now and they do not harm security at all. More policies can be added in the future after further review and tests. |
Are you sure the Security measure is not already implemented?
Please explain your new Security measure suggestion
Basically implement what Microsoft suggests in here
https://learn.microsoft.com/en-us/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services
The text was updated successfully, but these errors were encountered: