-
Notifications
You must be signed in to change notification settings - Fork 76
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
Should sshd-13 check for INFO instead of VERBOSE? #127
Comments
@atomic111 What do you think? At this point we set this to VERBOSE ssh-baseline/controls/sshd_spec.rb Line 166 in d2e1fe0
|
@shoekstra you are right the CIS recommends to set it Info, but from a security point of view, it is better to set it to verbose, because then you see more possible attacks on ssh. I prefer checking for Verbose |
as far I can remember one of important differences was related to the fingerprints of logged-in keys: none in info but in verbose. Can somebody confirm that? We can also accept both options in the baseline... |
We could make this an attribute and leave the default to verbose. This would allow other users to change their default if they need to. |
@chris-rock sounds good to me as well. Another option might be like: its('LogLevel') { should match(/^VERBOSE|INFO$/) } |
I think a common attribute between the 2 profiles should do the trick. The default value is set on That way, there is no regression on any profile and a user can make them compatible by just setting the attribute. |
Hi,
I've been running the ssh-baseline for sometime and recently ran the CentOS 7 CIS-1 baseline and the
xccdf_org.cisecurity.benchmarks_rule_5.2.3_Ensure_SSH_LogLevel_is_set_to_INFO
control fails:This baseline recommends setting it to
VERBOSE
; shouldsshd-13
be updated to check forINFO
instead?Stephen
The text was updated successfully, but these errors were encountered: