You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’ve yet to complete a full accounting, but running the cis_windowsserver2019_v110 configuration is resulting in a number of incorrectly configured registry entries.
For example, settings configuring values that should end up in “hklm\software\policies\microsoft\windows\windows search” are actually ending up in “hklm\software\policies\microsoft\windows\windowssearch”. Notice the missing space between windows and search.
I’ve noticed the same issue with the Windows NT, Network Connections, Group Policy, etc. I’m guessing whatever script was used to generate the DSC config wasn’t accounting for spaces in the registry path. But it also calls into question how much testing was done to ensure the system actually meets the CIS benchmark after running this config.
The text was updated successfully, but these errors were encountered:
I’ve yet to complete a full accounting, but running the cis_windowsserver2019_v110 configuration is resulting in a number of incorrectly configured registry entries.
For example, settings configuring values that should end up in “hklm\software\policies\microsoft\windows\windows search” are actually ending up in “hklm\software\policies\microsoft\windows\windowssearch”. Notice the missing space between windows and search.
I’ve noticed the same issue with the Windows NT, Network Connections, Group Policy, etc. I’m guessing whatever script was used to generate the DSC config wasn’t accounting for spaces in the registry path. But it also calls into question how much testing was done to ensure the system actually meets the CIS benchmark after running this config.
The text was updated successfully, but these errors were encountered: