Bug 2066674 - [ingress-operator] - Minimize wildcard/privilege Usage in Cluster and Local Roles
Summary: [ingress-operator] - Minimize wildcard/privilege Usage in Cluster and Local R...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.8
Hardware: x86_64
OS: Linux
low
low
Target Milestone: ---
: ---
Assignee: aos-network-edge-staff
QA Contact: Hongan Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-22 10:10 UTC by Simon Reber
Modified: 2022-12-19 20:56 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-12-19 20:56:19 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Simon Reber 2022-03-22 10:10:41 UTC
According http://static.open-scap.org/ssg-guides/ssg-ocp4-guide-cis.html#xccdf_org.ssgproject.content_rule_rbac_wildcard_use the usage of wildcard in ClusterRole and Roles should be prevented as best as possible.

Further, one should refrain from using `cluster-admin` permissions to comply with CIS security requirements.

It's therefore requested to review the below serviceAccount and their associated Roles as they were found not to be compliant with the above and restrict permissions further to the extend possible.

 - system:serviceaccount:openshift-ingress-operator:ingress-operator

Comment 1 Miciah Dashiel Butler Masters 2022-03-22 16:59:00 UTC
Setting blocker-.  

I have the same questions for this BZ as I have for bug 2066670:  

> Further, one should refrain from using `cluster-admin` permissions to comply
> with CIS security requirements.

Which clusterrole or binding is this referring to?  

Is this request part of a larger audit of cluster operators?

Comment 4 mfisher 2022-12-19 20:56:19 UTC
This issue is stale and has been closed because it has been open 90 days or more with no noted activity/comments in the last 60 days.  If this issue is crucial and still needs resolution, please open a new jira issue and the engineering team will triage and prioritize accordingly.


Note You need to log in before you can comment on or make changes to this bug.