-
Notifications
You must be signed in to change notification settings - Fork 353
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement defaultArmor
option
#595
Comments
SGTM, handling in CRD can be kept in different issue altogether and can be done later. |
@nyrahul as Rahul said we can handle the CRD part later. |
Just noted the CRD Part so as keep it as a later action item.
@nam-jaehyun A global option, if someone doesn't want to individually configure file/network/future more options like caps maybe. |
@daemon1024, do we need a global option if we have specific options for |
KubeArmor didn't have a configurable default mode of operations. This commit introduces a configurable default armor mode as well changes in enforcement system to act accordingly. Ref kubearmor#595 Signed-off-by: daemon1024 <[email protected]>
When KubeArmor is equipped with default armor block/audit each of the telemetry events generated needs to be an alert. This commit introduces changes to the policy matcher to update our logs to implicit block/audit alerts based on the default armor mode. Ref kubearmor#595 Signed-off-by: daemon1024 <[email protected]>
KubeArmor didn't have a configurable default mode of operations. This commit introduces a configurable default posture as well changes in enforcement system to act accordingly. Ref kubearmor#595 Signed-off-by: daemon1024 <[email protected]>
When KubeArmor is equipped with default posture block/audit each of the telemetry events generated needs to be an alert. This commit introduces changes to the policy matcher to update our logs to implicit block/audit alerts based on the configured default posture. Ref kubearmor#595 Signed-off-by: daemon1024 <[email protected]>
When KubeArmor is equipped with default posture block/audit each of the telemetry events generated needs to be an alert. This commit introduces changes to the policy matcher to update our logs to implicit block/audit alerts based on the configured default posture. Ref kubearmor#595 Signed-off-by: daemon1024 <[email protected]>
When KubeArmor is equipped with default posture block/audit each of the telemetry events generated needs to be an alert. This commit introduces changes to the policy matcher to update our logs to implicit block/audit alerts based on the configured default posture. Ref kubearmor#595 Signed-off-by: daemon1024 <[email protected]>
KubeArmor didn't have a configurable default mode of operations. This commit introduces a configurable default posture as well changes in enforcement system to act accordingly. Ref kubearmor#595 Signed-off-by: daemon1024 <[email protected]>
When KubeArmor is equipped with default posture block/audit each of the telemetry events generated needs to be an alert. This commit introduces changes to the policy matcher to update our logs to implicit block/audit alerts based on the configured default posture. Ref kubearmor#595 Signed-off-by: daemon1024 <[email protected]>
KubeArmor didn't have a configurable default mode of operations. This commit introduces a configurable default posture as well changes in enforcement system to act accordingly. Ref kubearmor#595 Signed-off-by: daemon1024 <[email protected]>
When KubeArmor is equipped with default posture block/audit each of the telemetry events generated needs to be an alert. This commit introduces changes to the policy matcher to update our logs to implicit block/audit alerts based on the configured default posture. Ref kubearmor#595 Signed-off-by: daemon1024 <[email protected]>
KubeArmor didn't have a configurable default mode of operations. This commit introduces a configurable default posture as well changes in enforcement system to act accordingly. Ref kubearmor#595 Signed-off-by: daemon1024 <[email protected]>
When KubeArmor is equipped with default posture block/audit each of the telemetry events generated needs to be an alert. This commit introduces changes to the policy matcher to update our logs to implicit block/audit alerts based on the configured default posture. Ref kubearmor#595 Signed-off-by: daemon1024 <[email protected]>
KubeArmor didn't have a configurable default mode of operations. This commit introduces a configurable default posture as well changes in enforcement system to act accordingly. Ref kubearmor#595 Signed-off-by: daemon1024 <[email protected]>
When KubeArmor is equipped with default posture block/audit each of the telemetry events generated needs to be an alert. This commit introduces changes to the policy matcher to update our logs to implicit block/audit alerts based on the configured default posture. Ref kubearmor#595 Signed-off-by: daemon1024 <[email protected]>
KubeArmor didn't have a configurable default mode of operations. This commit introduces a configurable default posture as well changes in enforcement system to act accordingly. Ref kubearmor#595 Signed-off-by: daemon1024 <[email protected]>
When KubeArmor is equipped with default posture block/audit each of the telemetry events generated needs to be an alert. This commit introduces changes to the policy matcher to update our logs to implicit block/audit alerts based on the configured default posture. Ref kubearmor#595 Signed-off-by: daemon1024 <[email protected]>
KubeArmor didn't have a configurable default mode of operations. This commit introduces a configurable default posture as well changes in enforcement system to act accordingly. Ref kubearmor#595 Signed-off-by: daemon1024 <[email protected]>
When KubeArmor is equipped with default posture block/audit each of the telemetry events generated needs to be an alert. This commit introduces changes to the policy matcher to update our logs to implicit block/audit alerts based on the configured default posture. Ref kubearmor#595 Signed-off-by: daemon1024 <[email protected]>
KubeArmor didn't have a configurable default mode of operations. This commit introduces a configurable default posture as well changes in enforcement system to act accordingly. Ref kubearmor#595 Signed-off-by: daemon1024 <[email protected]>
When KubeArmor is equipped with default posture block/audit each of the telemetry events generated needs to be an alert. This commit introduces changes to the policy matcher to update our logs to implicit block/audit alerts based on the configured default posture. Ref kubearmor#595 Signed-off-by: daemon1024 <[email protected]>
Feature Request
Implement
defaultPosture
option in CLI and CRDIs your feature request related to a problem? Please describe the use case.
Bug:
KubeArmor doesn't have a default posture in global context in case we only have from Source based policies.
Feature:
Add an option to audit events instead of blocking in case of whitelisting policies.
Describe the solution you'd like
Add options in KubeArmor to have a configurable default posture.
Initial Goals
-defaultArmor
CLI optiondefaultFileArmor
- default position for both files/processesdefaultNetworkArmor
cc @nyrahul @nam-jaehyun
The text was updated successfully, but these errors were encountered: