- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- Administrator's Guide
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
",t};e.buildCustomizationMenuUi=t;function n(e){let t='
",t}function s(e){let n=e.filter.currentValue||e.filter.defaultValue,t='${e.filter.label}
`,e.filter.options.forEach(s=>{let o=s.id===n;t+=``}),t+="${e.filter.label}
`,t+=`Classification:
compliance
Framework:
cis-kubernetes
Control:
4.1.10
Set up the kubernetes integration.
Ensure that if the kubelet refers to a configuration file with the --config
argument, that file is owned by root:root.
The kubelet reads various parameters, including security settings, from a config file specified by the --config
argument. If this file is specified you should restrict its file permissions to maintain the integrity of the file. The file should be owned by root:root.
Locate the Kubelet config file as follows: ps -ef | grep kubelet | grep config
. If the --config
argument is present, this gives the location of the Kubelet config file, for example /var/lib/kubelet/config.yaml
. Run the following command (using the file location you just identified) to find that file’s permissions: stat -c %U:%G /var/lib/kubelet/config.yaml
. Verify that the ownership is set to root:root
.
Run the following command (using the config file location identified in the Audit step): chown root:root /etc/kubernetes/kubelet.conf
None
By default, /var/lib/kubelet/config.yaml
file as set up by kubeadm is owned by root:root
.
Version 6.5.1 Minimize And Sparingly Use Administrative Privileges - Minimize administrative privileges and only use administrative accounts when they are required. Implement focused auditing on the use of administrative privileged functions and monitor for anomalous behavior.
Version 7.5.2 Maintain Secure Images - Maintain secure images or templates for all systems in the enterprise based on the organization’s approved configuration standards. Any new system deployment or existing system that becomes compromised should be imaged using one of those images or templates.