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

Improvement: CIS-5.7.4 The default namespace should not be used #644

Open
ad-zsolt-imre opened this issue Dec 7, 2024 · 1 comment
Open
Assignees

Comments

@ad-zsolt-imre
Copy link

ad-zsolt-imre commented Dec 7, 2024

Overview

I've go a report: CIS-5.7.4 The default namespace should not be used. It is highlighting that the kubernetes Endpoint is in the default namespace. There are no other Endpoints in the default namespace. If I'm not mistaken the related rule impl is in rules/endpoints-in-default-namespace/raw.rego.

Problem

I did some research and found that the kubernetes Endpoint is acceptable to be in the default namespace. See screenshot of the CIS benchmark below.

Screenshot 2024-12-07 at 18 04 51

Solution

I'm probably not familiar with all the frameworks you are supporting, but, it the above mentioned rule is simply based on CIS (as indicated by the title) it would be great to have it updated to ignore the kubernetes endpoint in the default namespace.

Alternatives

N/A

Additional context

N/A

@ad-zsolt-imre ad-zsolt-imre changed the title Question RE: CIS-5.7.4 The default namespace should not be used and Endpoints CIS-5.7.4 The default namespace should not be used - Improvement Dec 7, 2024
@ad-zsolt-imre ad-zsolt-imre changed the title CIS-5.7.4 The default namespace should not be used - Improvement Improvement: CIS-5.7.4 The default namespace should not be used Dec 7, 2024
@matthyx matthyx moved this to Accepted in Kubescaping Dec 10, 2024
@slashben
Copy link
Contributor

Hey Zsolt!

Interesting catch, thank you!

From the user's perspective, I think you're entirely correct. Let me check what CIS says about this; depending on that, we will fix it.

Cheers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Accepted
Development

No branches or pull requests

3 participants