- 필수 기능
- 시작하기
- 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.4
Set up the kubernetes integration.
If kube-proxy is running, ensure that the file ownership of its kubeconfig file is set to root:root.
The kubeconfig file for kube-proxy controls various parameters for the kube-proxy service in the worker node. You should set its file ownership to maintain the integrity of the file. The file should be owned by root:root.
Find the kubeconfig file being used by kube-proxy
by running the following command: ps -ef | grep kube-proxy
. If kube-proxy
is running, get the kubeconfig file location from the --kubeconfig
parameter.
Run the following command (based on the file location on your system) on the each worker node. For example, stat -c %U:%G <proxy kubeconfig file>
. Verify that the ownership is set to root:root
.
Run the below command (based on the file location on your system) on the each worker node:
chown root:root <proxy kubeconfig file>
None
By default, proxy file ownership is set to 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.
Find the kubeconfig file being used by kube-proxy by running the following command: ps -ef | grep kube-proxy If kube-proxy is running, get the kubeconfig file location from the –kubeconfig parameter. Run the below command (based on the file location on your system) on the each worker node. For example, stat -c %U:%G