Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Harden-Windows-Security-Module-v0.1.9 #140

Merged
merged 8 commits into from
Oct 17, 2023
Merged

Harden-Windows-Security-Module-v0.1.9 #140

merged 8 commits into from
Oct 17, 2023

Conversation

HotCakeX
Copy link
Owner

@HotCakeX HotCakeX commented Oct 17, 2023 •
edited
Loading

What's Changed

  1. Added -OnlyProcessMitigations optional parameter to the Unprotect-WindowsSecurity cmdlet. When used, it will only remove process mitigations applied by the Protect-WindowsSecurity cmdlet. You can read more about it in the module document.
  2. When applying the hardening measures, the prompt that asks you whether you want to set MSFT Defender Platform and Engine update channels to Beta will no longer be displayed if they are already set to Beta channel.

@HotCakeX
Added parameters to the module's cmdlets
36a2506 
The parameters allow Unprotect-WindowsSecurity cmdlet to only remove process mitigations
@HotCakeX HotCakeX added Bug 🐛 Something isn't working Enhancement 💯 New feature or request labels Oct 17, 2023
@HotCakeX HotCakeX self-assigned this Oct 17, 2023
@HotCakeX HotCakeX changed the title Added parameters to the module's cmdlets Harden-Windows-Security-Module-v0.1.9 Oct 17, 2023
@HotCakeX HotCakeX merged commit 70628ea into main Oct 17, 2023
2 checks passed
@HotCakeX HotCakeX deleted the Harden-Windows-Security-Module-v0.1.9 branch October 17, 2023 11:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@HotCakeX HotCakeX

Labels
Bug 🐛 Something isn't working Enhancement 💯 New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@HotCakeX