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

Update path between CIS releases #93

Open
bmphbWV0 opened this issue Feb 6, 2024 · 1 comment
Open

Update path between CIS releases #93

bmphbWV0 opened this issue Feb 6, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@bmphbWV0
Copy link

bmphbWV0 commented Feb 6, 2024

Feature Request or Enhancement

Summary of Request
Providing a shell script or any tool to upgrade defaults/main.yml vars for custom needs.

Describe Alternatives You've Considered
You provide default values for your vars in defaults/main.yml, that we can adapt for our needs.
I already did the migration from 1.1.1 to 1.2.0, then 1.2.0 to 1.3.0, and this is painful and time consuming to check if each task in the previous version has the same task number, variable name, variable value in the new version.
Is it possible to provide a script that will generate a new variable file based on a provided file to have an easier way to implement new versions of CIS hardening for Windows ?

@bmphbWV0 bmphbWV0 added the enhancement New feature or request label Feb 6, 2024
@animatco
Copy link

I would agree, that it would make life easier for those wanting to always have the latest version of the code with-out regression testing. One point though from a security standpoint, never run code with out going through it and testing on a segregated network . You always need to check that the code is what you are expecting and not something that can be dangerous or malevolent. This is in general for any code you may use that you did not write.

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

2 participants