- 필수 기능
- 시작하기
- 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-docker
Control:
3.7
Set up the docker integration.
You should verify that all the registry certificate files, usually found under the /etc/docker/certs.d/<registry-name>
directory, are individually owned and group owned by root.
The /etc/docker/certs.d/<registry-name>
directory contains Docker registry certificates. These certificate files must be individually owned and group owned by root to ensure that less privileged users are unable to modify the contents of the directory.
You should execute the command below to verify that the registry certificate files are individually owned and group owned by root:
stat -c %U:%G /etc/docker/certs.d/* | grep -v root:root
This command does not return any data.
Execute the following command: chown root:root /etc/docker/certs.d/<registry-name>/*
This sets the individual ownership and group ownership for the registry certificate files to root.
None
By default, the individual ownership and group ownership for registry certificate files is correctly set to 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.