-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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 1.9 Control Node Checks 1.1.13, 1.1.14 show fail with correct permissions/ownership. no actual output reported #1644
Comments
@btray900 Thanks for reporting.
|
Debug for 1.1.13 attached, @mozillazg |
@btray900 Please changes kube-bench/cfg/cis-1.9/master.yaml Line 192 in 5a3fd1d
to
kube-bench/cfg/cis-1.9/master.yaml Line 210 in 5a3fd1d
to
then try again. |
@btray900 nice catch thanks. |
@andypitcher Feel free to send a pull request. Thanks! |
@mozillazg IMO This issue can be now closed, since #1649 has been merged. Thanks again @btray900 ! |
Overview
CIS 1.9 implements a permission and ownership check for /etc/kubernetes/admin.conf and /etc/kubernetes/super-admin.conf.
The tested control node shows 600 for both files, as well as root:root ownership but the check is reporting FAIL for both
1.1.13
and1.1.14
inmaster.yaml
forcis-1.9
Also CIS 1.9 master.yaml 1.1.14 has an incorrect remediation path (chmod versus chown) for super-admin.conf.
How did you run kube-bench?
kube-bench --benchmark cis-1.9 --json
What happened?
Permissions and ownership are correct, but benchmark reports FAIL.
Actual output is not captured for CIS-1.9
[Comparison] Actual output was captured as expected for CIS-1.8
What did you expect to happen:
The tests would pass due to the correct permissions and ownership for the admin.conf and super-admin.conf on Kubernetes 1.29.4
Environment
kube-bench: v0.8.0
kubernetes: 1.29.4
The text was updated successfully, but these errors were encountered: