The container platform must limit privileges to the container platform registry.
Severity | Group ID | Group Title | Version | Rule ID | Date | STIG Version |
---|---|---|---|---|---|---|
medium | V-233066 | SRG-APP-000133 | SRG-APP-000133-CTR-000290 | SV-233066r960960_rule | 2024-12-05 | 2 |
Description |
---|
To control what is instantiated within the container platform, it is important to control access to the registry. Without this control, container images can be introduced and instantiated by accident or on container platform startup. Without control of the registry, security measures put in place for the runtime can be bypassed meaning the controls of approval and testing are also bypassed. Only those individuals and roles approved by the organization can have access to the container platform registry. |
ℹ️ Check |
---|
Review the container platform registry configuration to determine if the level of access to the registry is controlled through user privileges. Attempt to perform registry operations to determine if the privileges are enforced. If the container platform registry is not limited through user privileges or the user privileges are not enforced, this is a finding. |
✔️ Fix |
---|
Configure the container platform to use and enforce user privileges when accessing the container platform registry. |