Censor suspicious environment variables #268
Open
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.
This pull request intends to censor suspicious found environment variables.
Previously any suspicious environment variable found was being leaked during
CIS-DI-0010
checkpoint assessment as seen below:With this PR the same finding would be:
Notice that the environment variable now isn't leaked on the output to stdout. This also applies to any other export format.
This is important since Dockle might inadvertently leak production (or other environment) credentials on a CI/CD pipeline