You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
The text was updated successfully, but these errors were encountered:
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
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
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 thedefault
namespace. There are no other Endpoints in thedefault
namespace. If I'm not mistaken the related rule impl is inrules/endpoints-in-default-namespace/raw.rego
.Problem
I did some research and found that the
kubernetes
Endpoint is acceptable to be in thedefault
namespace. See screenshot of the CIS benchmark below.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 thedefault
namespace.Alternatives
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered: