Adds security scan workflow #127
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Introduces a new GitHub Actions workflow for security scanning. This workflow runs on pushes to the main branch and pull requests targeting main. It incorporates several security tools, including Trivy (for configuration scanning), KubeLinter, Checkov, and Gitleaks, to identify potential vulnerabilities and security issues within the codebase and Kubernetes configurations. Results are uploaded as SARIF files for integration with GitHub's code scanning features. It also uploads logs for debugging purposes.
Updates KubeLinter execution within the security scan workflow to utilize a Docker container. This change removes the previous installation steps and streamlines the linting process, ensuring consistent execution across different environments.
…rove KubeLinter execution steps
…workflow for improved scanning
…rkflow and remove deprecated ignore file
nilgaar
force-pushed
the
security/add-scan-action
branch
from
d22b529 to
c04db9b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
✅ Chore / CI enhancement – adds automated security scanning as part of the CI pipeline.
What is the current behavior?
The repository currently lacks an automated workflow to perform continuous security scanning.
Security checks such as vulnerability detection, configuration validation, and secret scanning must be done manually or are not consistently enforced.
What is the new behavior?
This PR introduces a new GitHub Actions workflow that automatically runs security scans on every push and pull request targeting the
mainbranch.It includes:
Results are uploaded as SARIF reports for integration with GitHub’s Code Scanning Alerts, and logs are stored as workflow artifacts for further debugging.