The container platform runtime must fail to a secure state if system initialization fails, shutdown fails, or aborts fail.
Severity | Group ID | Group Title | Version | Rule ID | Date | STIG Version |
|---|---|---|---|---|---|---|
| medium | V-233122 | SRG-APP-000225 | SRG-APP-000225-CTR-000570 | SV-233122r961122_rule | 2024-12-05 | 2 |
| Description |
|---|
| The container platform offers services for container image orchestration and services for users. If any of these services were to fail into an insecure state, security measures for user and data separation and image instantiation could become absent. In addition, audit log protections could be relaxed allowing for investigation of what occurred could be lost. To protect services and data, it is important for the container platform to fail to a secure state if the container platform registry initialization fails, shutdown fails, or aborts fail. |
| ℹ️ Check |
|---|
| Review documentation and configuration to determine if the container platform runtime fails to a secure state if system initialization fails, shutdown fails, or aborts fail. If the container platform runtime cannot be configured to fail securely, this is a finding. |
| ✔️ Fix |
|---|
| Configure the container platform runtime to fail to a secure state if system initialization fails, shutdown fails, or aborts fail. |