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

falcon-self-hosted-registry-assessment cluster-wide permissions #370

Open
hrbasic opened this issue Feb 25, 2025 · 0 comments · May be fixed by #374
Open

falcon-self-hosted-registry-assessment cluster-wide permissions #370

hrbasic opened this issue Feb 25, 2025 · 0 comments · May be fixed by #374

Comments

@hrbasic
Copy link

hrbasic commented Feb 25, 2025

The Helm chart for falcon-self-hosted-registry-assessment is using cluster-wide permissions to read secrets:: https://github.com/CrowdStrike/falcon-helm/blob/main/helm-charts/falcon-self-hosted-registry-assessment/templates/executor-cluster-role.yaml.

If my understanding is correct, this service pulls images from a private Artifactory and performs assessments. Why does it need cluster-wide permissions to read secrets from other namespaces? This seems like a security issue.

In our use case, we use ArgoCD for deployments and do not allow other users (in this case, the team responsible for deploying this service) to create ClusterRole and ClusterRoleBinding resources. Am I missing something, could we simply use Role instead of ClusterRole?

kubectl auth can-i get secret --namespace=kube-system --as=system:serviceaccount:crowdstrike-falcon-io-shra:falcon-shra-executor  
yes
@hrbasic hrbasic linked a pull request Mar 6, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant