-
Notifications
You must be signed in to change notification settings - Fork 294
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
How to fix SAST analysis issues reported for falco #787
Comments
As your issue concerns the Helm chart and not directly falco's source code, can you recreate this issue in https://github.com/falcosecurity/charts, please. We'll take care of the failed checks with @alacuku and even maybe verify the other charts at the same time |
Great, thanks. |
@Issif wouldn't it be simpler to transfer this issue ? |
I can't either, let me see with the other maintainers. |
Hey @kristian-kirilov-rg , You are running the |
Transferred this to the |
I'm not sure what are you speaking about. We check the Kubernetes template, there is nothing related to the namespace. |
That's what I'm talking about. The messages clearly refer to resources using the |
I see, no worries, we can exclude these. But the list I showed you above is quite big :-) |
Motivation
Hi there, our company uses checkov to perform SAST analysis for our codebase.
I know some of these things are "by design" but how to handle with the rest?
Please check logs below.
Feature
Just add the required settings in the yaml manifest ...
Alternatives
or in case of they cannot be remediated - clearly state this in the documentation and provide detailed guide how to exclude them from the scanning.
Additional context
I have downloaded the helm chart from the official repository, unpacked the archive, used helm template to show the generated yaml files and scanned them with checkov. Please check here:
Here are all the issues thrown by the checkov engine so far
The text was updated successfully, but these errors were encountered: