use cap_drop/cap_add in docker instead of privileged=true #6237
Conversation
This file contains 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
privileged=true should be always avoided as stated by Owasp [1] and CIS [2]. Instead, use cap_drop/cap_add as fine-grained capability mechanism. [1] https://cheatsheetseries.owasp.org/cheatsheets/Docker_Security_Cheat_Sheet.html [2] https://www.cisecurity.org/benchmark/docker
ra1nb0w
force-pushed
the
feat/docker-compose_cap_drop
branch
from
cd02605 to
2cbc4af
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Contribution Guidelines
What does this PR include?
Short Description
privileged=true should be always avoided as stated by Owasp [1] and
CIS [2]. Instead, use cap_drop/cap_add as fine-grained capability
mechanism.
[1] https://cheatsheetseries.owasp.org/cheatsheets/Docker_Security_Cheat_Sheet.html
[2] https://www.cisecurity.org/benchmark/docker
Affected Containers
Did you run tests?
What did you tested?
tested with a new installation and a dummy domain
What were the final results? (Awaited, got)
avoiding the usage of
privileged=true