Benchmark: CronJob
Description
This section contains recommendations for configuring CronJob resources.
Usage
Install the mod:
mkdir dashboardscd dashboardspowerpipe mod initpowerpipe mod install github.com/turbot/steampipe-mod-kubernetes-complianceStart the Powerpipe server:
steampipe service startpowerpipe serverOpen http://localhost:9033 in your browser and select CronJob.
Run this benchmark in your terminal:
powerpipe benchmark run kubernetes_compliance.benchmark.all_controls_cronjobSnapshot and share results via Turbot Pipes:
powerpipe benchmark run kubernetes_compliance.benchmark.all_controls_cronjob --shareControls
- CronJob containers should has admission capability restricted
- CronJob containers admission control plugin should be set to 'always pull images'
- CronJob containers admission control plugin should not be set to 'always admit'
- CronJob containers peer client cert auth should be enabled
- CronJob containers argument anonymous auth should be disabled
- CronJob containers should have audit log max-age set to 30 or greater
- CronJob containers should have audit log max backup set to 10 or greater
- CronJob containers should have audit log max size set to 100 or greater
- CronJob containers should have audit log path configured appropriately
- CronJob containers argument authorization mode should not be set to 'always allow'
- CronJob containers argument authorization mode should have node
- CronJob containers argument authorization mode should have RBAC
- CronJob containers argument etcd auto TLS should be disabled
- CronJob containers argument etcd cafile should be set
- CronJob containers should have etcd certfile and keyfile configured appropriately
- CronJob containers argument etcd client cert auth should be enabled
- CronJob containers should have etcd peer certfile and peer keyfile configured appropriately
- CronJob containers argument event qps should be less than 5
- CronJob containers argument insecure port should be set to 0
- CronJob containers argument apiserver etcd certfile and keyfile should be configured
- CronJob containers kube-apiserver profiling should be disabled
- CronJob containers should have kube-apiserver TLS cert file and TLS private key file configured appropriately
- CronJob containers argument kube-controller-manager bind address should be set to 127.0.0.1
- CronJob containers kube controller manager profiling should be disabled
- CronJob containers should have kube controller manager root CA file configured appropriately
- CronJob containers argument kube controller manager service account credentials should be enabled
- CronJob containers should have kube controller manager service account private key file configured appropriately
- CronJob containers argument kube-scheduler bind address should be set to 127.0.0.1
- CronJob containers kube scheduler profiling should be disabled
- CronJob containers argument kubelet authorization mode should not be set to 'always allow'
- CronJob containers should have kubelet client CA file configured appropriately
- CronJob containers argument kubelet client certificate and key should be configured
- CronJob containers argument kubelet HTTPS should be enabled
- CronJob containers argument kubelet read-only port should be set to 0
- CronJob containers should have kubelet terminated pod gc threshold configured appropriately
- CronJob containers should have kubelet TLS cert file and TLS private key file configured appropriately
- CronJob containers argument make iptables util chains should be enabled
- CronJob containers argument admission control plugin NamespaceLifecycle should be enabled
- CronJob containers argument admission control plugin NodeRestriction should be enabled
- CronJob containers argument admission control plugin PodSecurityPolicy should be enabled
- CronJob containers argument protect kernel defaults should be enabled
- CronJob containers argument request timeout should be set as appropriate
- CronJob containers argument rotate kubelet server certificate should be enabled
- CronJob containers argument secure port should not be set to 0
- CronJob containers argument admission control plugin where either PodSecurityPolicy or SecurityContextDeny should be enabled
- CronJob containers argument admission control plugin ServiceAccount should be enabled
- CronJob containers --service-account-key-file argument should be set as appropriate
- CronJob containers argument service account lookup should be enabled
- CronJob containers should minimize its admission with capabilities assigned
- CronJob containers should has encryption providers configured appropriately
- CronJob containers ports should not have host port specified
- CronJob containers should has image pull policy set to Always
- CronJob containers have image tag specified which should be fixed not latest or blank
- CronJob containers should have kubelet certificate authority configured appropriately
- CronJob containers Kubernetes dashboard should not be deployed
- CronJob containers should have liveness probe
- CronJob containers argument basic auth file should not be set
- CronJob containers argument hostname override should not be configured
- CronJob containers argument insecure bind address should not be set
- CronJob containers should not have privileged access
- CronJob containers should not allow privilege escalation
- CronJob containers should not be mapped with privilege ports
- CronJob containers should have readiness probe
- CronJob containers certificate rotation should be enabled
- CronJob containers should have secrets defined as files
- CronJob containers should has security context defined
- CronJob containers argument --streaming-connection-idle-timeout should not be set to 0
- CronJob containers kube-apiserver should only make use of strong cryptographic ciphers
- CronJob containers kubelet should only make use of strong cryptographic ciphers
- CronJob containers should not use CAP_SYS_ADMIN linux capability
- CronJob containers token auth file should not be configured
- CronJob containers should not have added capabilities
- CronJob containers should have a CPU limit
- CronJob containers should have a CPU request
- CronJob definition should not use default namespace
- Seccomp profile is set to docker/default in CronJob definition
- CronJob containers should not run with host network access
- CronJob containers should not share the host process namespace
- CronJob containers should run with a read only root file system
- CronJob containers should have a memory limit
- CronJob containers should have a memory request
- CronJob containers should not run with root privileges