Search filters this STIG's checks locally. Separate terms must all match (use quotes for an exact phrase). A search you ran on the Search page carries over here.
Assessment Title
Rule Text
The container platform must prohibit containers from accessing privileged resources.
Description
Discussion Text
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.
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.
New to STIG checklists? Read What is a STIG checklist? and CKL vs CKLB.