The kubernetes configuration does not set a logging property, which prevents log files from being created. These files are useful for identifying and tracking malicious actions or anomalous behavior. Alternatively, log files do not have sufficient level of detail.
Perform harmful actions without raising an alert.
Enable auditing on the Kubernetes API Server and set the desired audit log path.
Authenticated attacker from the Internet.
⌚ 60 minutes.
Default score using CVSS 3.1. It may change depending on the context of the src.
Default score using CVSS 4.0. It may change depending on the context of the src.
The Kubernetes configuration includes the desired log path
apiVersion: v1
kind: Pod
metadata:
creationTimestamp: null
labels:
component: kube-apiserver
tier: control-plane
name: kube-apiserver
namespace: kube-system
spec:
containers:
- command:
+
- kube-apiserver
+
- --audit-log-path=/path/to/log
image: gcr.io/google_containers/kube-apiserver-amd64:v1.6.0
...
The Kubernetes configuration does not set a log file configuration
apiVersion: v1
kind: Pod
metadata:
creationTimestamp: null
labels:
component: kube-apiserver
tier: control-plane
name: kube-apiserver
namespace: kube-system
spec:
containers:
- command:
+
- kube-apiserver