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.

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

Fix 18.10.82.1 #35

Merged
merged 1 commit into from
Mar 28, 2024
Merged

Fix 18.10.82.1 #35

merged 1 commit into from
Mar 28, 2024

Conversation

SwaffelSmurf
Copy link
Contributor

Overall Review of Changes:
The registry key associated with control "18.10.82.1 Ensure 'Enable MPR notifications for the system' is set to 'Disabled'" is incorrectly configured. It should have a value of 0 to indicate the disabled state

Issue Fixes:
N/A

Enhancements:
The value for EnableMPR was adjusted from 1 to 0 to ensure compliance.

How has this been tested?:
Tested on a Windows 11 23H2 VM, since it has the new admx files, according to Microsoft Tech Community. Enabled the policy setting to disabled state, resulting in the creation of the registry key with a value of 0.

Added the key manually on a hardened Windows Server 2022 test VM. Then verified the control in Rapid7 InightVM which resulted in a pass.

oval-org.cisecurity.benchmarks.microsoft_windows_server_2022-def-3607688: PASS

Based on the following 1 results:

At least one specified Windows registry information entry must match the given criteria. At least one evaluation must pass.

Entry 1 findings: PASS
hive: HKEY_LOCAL_MACHINE
key: SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
name: EnableMPR
type: reg_dword
value: 0

Signed-off-by: Ivo Muijtjens <[email protected]>
Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Congrats on opening your first pull request and thank you for taking the time to help improve Ansible-Lockdown!
Please join in the conversation happening on the Discord Server as well.

Copy link
Contributor

@georgenalen georgenalen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

Copy link
Contributor

@MrSteve81 MrSteve81 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved

@frederickw082922
Copy link
Contributor

Great find @SwaffelSmurf ! Thank you!

@MrSteve81 MrSteve81 merged commit 63a6b7a into ansible-lockdown:devel Mar 28, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants