STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 4 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Mirantis Kubernetes Engine Security Technical Implementation Guide

V-260940

CAT II (Medium)

Use of privileged Linux containers must be limited to system containers.

Rule ID

SV-260940r966177_rule

STIG

Mirantis Kubernetes Engine Security Technical Implementation Guide

Version

V2R1

CCIs

CCI-002233

Discussion

Using the --privileged flag gives all Linux Kernel Capabilities to the container, thus overwriting the --cap-add and --cap-drop flags. The --privileged flag gives all capabilities to the container, and it also lifts all the limitations enforced by the device cgroup controller. Any container that requires this privilege must be documented and approved.

Check Content

When using Kubernetes orchestration, this check is Not Applicable. 

When using Swarm orchestration, execute the following command as a trusted user on the host operating system via CLI:

docker ps --quiet --all | grep -iv "MKE\|kube\|dtr" | awk '{print $1}' | xargs docker inspect --format '{{ .Id }}: Privileged={{ .HostConfig.Privileged }}'

Verify in the output that no containers are running with the --privileged flag. If there are, this is a finding.

Fix Text

When using Kubernetes orchestration, this check is Not Applicable. 

Review and remove nonsystem containers previously created by these users that allowed privileged execution using:

docker container rm [container]