STIGhubSTIGhub
STIGsSearchCompareAbout

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
  • Compare Versions

Resources

  • About
  • VPAT
  • DISA STIG Library
STIGs updated 2 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Container Platform Security Requirements Guide

V-233127

CAT II (Medium)

The container platform must prohibit containers from accessing privileged resources.

Rule ID

SV-233127r1137644_rule

STIG

Container Platform Security Requirements Guide

Version

V2R4

CCIs

CCI-001090

Discussion

Containers images instantiated within the container platform may request access to host system resources. Access to privileged resources can allow for unauthorized and unintended transfer of information, but in some cases, these resources may be needed for the service being offered by the container. By default, containers should be denied instantiation when privileged system resources are requested and granted only after approval has been given. When access to privileged resources is necessary for a container, a new policy for execution should be written for the container. The default behavior must not give containers privileged access to host system resources. Examples of system resources that should be protected are kernel namespaces and host system sensitive directories such as /etc and /usr. This requirement also applies to Zero Trust initiatives.

Check Content

Review documentation and configuration to determine if the container platform disallows instantiation of containers trying to access host system privileged resources. 

If the container platform does not block containers requesting host system privileged resources, this is a finding.

Fix Text

Configure the container platform to block instantiation of containers requesting access to host system-privileged resources.