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

Difference between scanning cluster using CLI and running it as a pod within the cluster #541

Open
wxnks opened this issue Aug 25, 2023 · 0 comments
Labels
question Further information is requested

Comments

@wxnks
Copy link

wxnks commented Aug 25, 2023

What are you trying to achieve

I'm trying to understand if there is a difference between running kube-hunter using the cli option and running in a pod. If yes, what is the preferred/best way to scan clusters (using cli or running as a pod)?

Minimal example (if applicable)

I observed that he reports generated when scanning using the cli option and when running kube-hunter in a pod within the cluster are different. From these results, I could not fully understand whether i missed to add flags while running the scan within the cluster or these two methods of scanning are not the same.

While using the cli option I got the report that I have one vulnerability in my cluster, whereas running the same scan in the pod did not show the vulnerability.

I applied the job.yaml file to run in the pod.

@wxnks wxnks added the question Further information is requested label Aug 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant