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-233122

CAT II (Medium)

The container platform runtime must fail to a secure state if system initialization fails, shutdown fails, or aborts fail.

Rule ID

SV-233122r961122_rule

STIG

Container Platform Security Requirements Guide

Version

V2R4

CCIs

CCI-001190

Discussion

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 Content

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 Text

Configure the container platform runtime to fail to a secure state if system initialization fails, shutdown fails, or aborts fail.