[New Rule] Kubernetes Suspicious Change to Privileges of Running Security Context #2302
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
…rity Context ## Issue #2032 ## Summary This rule detects when a user modifies a running pod/container to run in privileged mode or to run as root. A highly privileged container has access to the node's resources and breaks the isolation between containers. Processes in a privileged container are essentially equivalent to root on the host. If compromised, an attacker can use the privileged container to gain access to the underlying host. Gaining access to the host may provide the adversary with the opportunity to achieve follow-on objectives, such as establishing persistence, moving laterally within the environment, or setting up a command and control channel on the host.
imays11
added
blocked
OS: Linux
Rule: New
…o-running-podcontainer-security-context
…o-running-podcontainer-security-context
|
Closing, testing revealed this behavior is not allowed by default. |
imays11
deleted the
2032-new-rule-kubernetes-suspicious-change-to-running-podcontainer-security-context
branch
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.
Issue
#2032
Summary
This rule detects when a user modifies a running pod/container to run in privileged mode or to run as root. A highly privileged container has access to the node's resources and breaks the isolation between containers. Processes in a privileged container are essentially equivalent to root on the host. If compromised, an attacker can use the privileged container to gain access to the underlying host. Gaining access to the host may provide the adversary with the opportunity to achieve follow-on objectives, such as establishing persistence, moving laterally within the environment, or setting up a command and control channel on the host.