cyberstrikeus CIS Docker Benchmark v1.7.0 - Control 7.9
Profile Applicability
- Level: 1
- Type: Manual
- Platform: Docker Swarm
Description
You should separate management plane traffic from data plane traffic.
Rationale
Separating management plane traffic from data plane traffic ensures that these types of traffic are segregated from each other. These traffic flows can then be individually monitored and tied to different traffic control policies and monitoring. This also ensures that the management plane is always reachable even if there is a great deal of traffic on the data plane.
Impact
This requires two network interfaces per node.
Audit Procedure
You should run the command below on each swarm node and ensure that the management plane address is the data plane address.
docker node inspect --format '{{ .Status.Addr }}' self
Remediation
You should initialize the swarm with dedicated interfaces for management and data planes respectively.
For example,
docker swarm init --advertise-addr=192.168.0.1 --data-path-addr=17.1.0.3
Default Value
By default, data plane traffic is not separated from management plane traffic.
References
CIS Controls
v8:
- 13.4 Perform Traffic Filtering Between Network Segments
- Perform traffic filtering between network segments, where appropriate.
v7:
- 14.1 Segment the Network Based on Sensitivity
- Segment the network based on the label or classification level of the information stored on the servers, locate all sensitive information on separated Virtual Local Area Networks (VLANs).