Kubernetes Service Account Created in Kube Namespace
이 페이지는 아직 영어로 제공되지 않습니다. 번역 작업 중입니다.
현재 번역 프로젝트에 대한 질문이나 피드백이 있으신 경우
언제든지 연락주시기 바랍니다.Goal
Detect when a user is creating a service account in one of the Kubernetes default namespaces.
Strategy
This rule monitors when a create (@http.method:create) action occurs for a service account (@objectRef.resource:serviceaccounts) within either of the kube-system or kube-public namespaces.
The only users creating service accounts in the kube-system namespace should be cluster administrators. Furthermore, it is best practice to not run any cluster critical infrastructure in the kube-system namespace.
The kube-public namespace is intended for kubernetes objects which should be readable by unauthenticated users. Thus, a service account should likely not be created in the kube-public namespace.
Triage and response
Determine if the user should be creating this new service account in one of the default namespaces.
Changelog
- 21 September 2022 - Tuned rule to remove system and EKS service account creations, increased severity, added decrease on environment flag.
- 17 October 2022 - Updated tags.
- 7 May 2024 - Updated detection query to include logs from Azure Kubernetes Service.
- 17 July 2024 - Updated detection query to include logs from Google Kubernetes Engine.
- 19 November 2024 - Updated detection query to exclude token creation.
