-
Notifications
You must be signed in to change notification settings - Fork 32
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
Control 18.10.43.10.2 Misconfigured #28
Labels
bug
Something isn't working
Comments
Good day @natilik-mikeguy Great catch and breakdown!! Thank you!! We will update the Control in the next release!! CC: @MrSteve81 |
frederickw082922
added a commit
that referenced
this issue
Feb 21, 2024
Signed-off-by: Frederick Witty <[email protected]>
Merged fix in #29 |
mfortin
pushed a commit
to mfortin/Windows-2022-CIS
that referenced
this issue
Apr 16, 2024
Signed-off-by: Frederick Witty <[email protected]> Signed-off-by: Mathieu Fortin <[email protected]>
mfortin
pushed a commit
to mfortin/Windows-2022-CIS
that referenced
this issue
Apr 16, 2024
Signed-off-by: Frederick Witty <[email protected]> Signed-off-by: Mathieu Fortin <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the Issue
Under the following file... https://github.com/ansible-lockdown/Windows-2022-CIS/blob/devel/tasks/section18.yml you have the following code:
I believe this is actually doing the opposite of what is intended. This was brought to my attention by an incident created in Microsoft Defender for Endpoint. It flagged a high severity incident that Ansible was disabling Defender protection.
Expected Behavior
I believe this should be setting the dword value to 0 as highlighted here...
https://admx.help/?Category=Windows_10_2016&Policy=Microsoft.Policies.WindowsDefender::DisableRealtimeMonitoring
I can see the confusion with the use of Disabled/Enabled. But when Enabled (dword value 1) you are Enabling the Disabling of the setting. i.e. DisableRealtimeMonitoring = true.
Control(s) Affected
18.10.43.10.2
Environment (please complete the following information):
Using git tag 2.0.0. Have checked latest devel and it is still the same.
The text was updated successfully, but these errors were encountered: