[SEC-2180] Enable automated container scanning#15
Merged
axrk merged 1 commit intoSep 3, 2025
Conversation
axrk
added
automerge
Author
|
@pleo-io/team-data-services Can I get an approval please ? 🙏 |
axrk
deleted the
sec-2180-measure-and-enforce-container-scanning-adoption
branch
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
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's the change
This PR introduces the new scheduled container scanning workflow using Wiz CLI, now part of our security baseline for all repositories.
The scanning workflow will be added to all repos, but the logic includes a Dockerfile presence check. If no Dockerfile is found, the scan is skipped automatically, which prevents additional build time or errors introduced.
What’s included:
.github/workflows/security-container-scanning.yamlto your workflow config.Actions needed
🔹 If your repository has containers, please review the
setWizContainerDockerfilePathvalue in templates.yaml (default is root) to ensure they are properly scanned. For now, only one value per repo is supported so please only input one path.For additionnal details, please refer to the user documentation.
🔹 Since the centralized-templates version is upgraded, you'll have to also merge an additionnal automated PR created by file-distributor (titled “chore(ci-deps): Update files based on repository configuration”), for the changes to be complete.
See more details here : CI / CD at Pleo
If you are concerned about any changes, please feel free to comment here or reach out to #ask-security.