For GitHub repositories, Snyk scans your manifest files for security vulnerabilities, and scans your Kubernetes configuration files for misconfigurations and security issues as well. For configuration files, once scanned, Snyk reports on any misconfigurations based on the policies your administrator has implemented, and makes recommendations for fixing accordingly.
An administrator should integrate your organization with your preferred Git repository and enable detection of configuration files as described here.
You must have a Snyk account and your configuration files should be in either JSON or YAML format.
We currently scan configuration files for Deployments, Pods and Services.
If you already imported your repositories for testing before cloud configuration file detection was enabled by your administrator, then you should re-import that repository again in order to import the relevant JSON or YAML configuration files:
Every time a repository is scanned:
Every supported manifest file and every supported configuration file is imported as a separate project, grouped together per repository, similar to this example:
If you re-imported the repository in order to import the cloud configuration files, then Snyk imports and tests the configuration files and also re-tests the already imported application manifest files - displaying the test time as "now".
Click the project link you're interested in, to view the scan results and to correct your configuration files accordingly:
For more information about these results, see Working with your Kubernetes configuration file test results.