-
Notifications
You must be signed in to change notification settings - Fork 191
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
CIS 4.1.1.3 #85
CIS 4.1.1.3 #85
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that is a helpful improvement @tomhaynes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tomhaynes makes sense. thanks for chaning this
@chris-rock @atomic111 this change has broken the tests for chef-os-hardening. As we currently are not managing the audit configuration, any ideas how to handle this? (I do not have time to implement it now) Should we create an issue in the implementation repo and disable this test for now? |
I created dev-sec/chef-os-hardening#182 and dev-sec/chef-os-hardening#181 |
We could pin to released versions of the benchmark... |
@chris-rock Hm, okay. But this would lead to a recurrent version repining, right? |
yes, unfortunately. I am open to any other idea |
@chris-rock I do not have any other idea :\ For me personally its easier to live with a current setup (#55 would make it even better). But if somebody has a better idea, I would be also happy to hear it |
For CIS v2.1:
4.1.1.3 Ensure audit logs are not automatically deleted:
Audit:
Run the following command and verify output matches:
max_log_file_action = keep_logs