Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Alert Policy for KubeArmor #1750

Open
daemon1024 opened this issue May 8, 2024 · 3 comments
Open

Alert Policy for KubeArmor #1750

daemon1024 opened this issue May 8, 2024 · 3 comments
Labels
enhancement New feature or request

Comments

@daemon1024
Copy link
Member

Feature Request

As a User I want an alert
when

  1. ppid = 0
  2. tty != null

Is your feature request related to a problem? Please describe the use case.

As a User I want to identify kubectl exec calls

Describe the solution you'd like

TBD
@daemon1024 daemon1024 added the enhancement New feature or request label May 8, 2024
@Ayush9026
Copy link

Ayush9026 commented May 8, 2024 •
edited
Loading

/assign @Ayush9026 @daemon1024 sir i will solve this issue.

@yp969803
Copy link

/assign

@yp969803
Copy link

@daemon1024 shoudn't the PPID=1, as the container entrypoint process (pid=1 wrt the container) starts the kubectl exec process?

@yp969803 yp969803 mentioned this issue Jul 27, 2024
Closed
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: added kubectl exec alert policy yp969803/KubeArmor
3 participants
@daemon1024 @Ayush9026 @yp969803