- 필수 기능
- 시작하기
- 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:
2.1
Set up the docker integration.
By default, all network traffic is allowed between containers on the same host on the default network bridge. You can restrict all inter-container communication and link specific containers together that require communication. Or, you can create a custom network and only join containers that need to communicate to that custom network.
By default, unrestricted network traffic is enabled between all containers on the same host on the default network bridge. Each container has the potential of reading all packets across the container network on the same host. This might lead to an unintended and unwanted disclosure of information to other containers. Hence, restrict inter-container communication on the default network bridge.
Verify that the default network bridge has been configured to restrict inter-container communication by running:
docker network ls --quiet | xargs docker network inspect --format '{{ .Name }}: {{ .Options }}'
Check that it returns com.docker.network.bridge.enable_icc:false
for the default network bridge.
Edit the Docker daemon configuration file to ensure that inter-container communication is disabled:
"icc": false
Alternatively, run the Docker daemon directly and pass --icc=false
as an argument:
dockerd --icc=false
Follow the Docker documentation and create a custom network, and only join containers that need to communicate to that custom network. The --icc
parameter only applies to the default docker bridge. If you use a custom network, adopt the segmenting networks approach instead.
Inter-container communication is disabled on the default network bridge. If any communication between containers on the same host is desired, it needs to be explicitly defined using container linking or custom networks.
By default, all inter-container communication is allowed on the default network bridge.
None