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

[project candidate] consider settings that are OS standard to be true even if the responsible registry setting does not exist #455

Open
TuemmlerKelch opened this issue Nov 13, 2023 · 0 comments
Labels
enhancement New feature or request
Milestone

Comments

@TuemmlerKelch
Copy link
Collaborator

TuemmlerKelch commented Nov 13, 2023

A lot of settings are properly configure from the get-go and just to be considered unsafe if manually created in a non-compliant way.
Cis benchmarks have a lot of insight on this topic.

This should be implemented for
Windows 11 + Server 2022
Windows 10 + Server 2019
and maybe for Server 2016, too

@TuemmlerKelch TuemmlerKelch added the enhancement New feature or request label Nov 13, 2023
@TuemmlerKelch TuemmlerKelch added this to the 5.8 milestone Nov 13, 2023
@TuemmlerKelch TuemmlerKelch changed the title consider settings that are OS standard to be true even if the responsible registry setting does not exist [project candidate] consider settings that are OS standard to be true even if the responsible registry setting does not exist Mar 12, 2024
@TuemmlerKelch TuemmlerKelch removed this from the 5.9.0 milestone Mar 12, 2024
@TuemmlerKelch TuemmlerKelch added this to the On Hold milestone Mar 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant