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

CAT II (Medium)

The container platform must use FIPS-validated SHA-2 or higher hash function for digital signature generation and verification (non-legacy use).

Rule ID

SV-233285r961896_rule

STIG

Container Platform Security Requirements Guide

Version

V2R4

CCIs

CCI-000803

Discussion

Without the use of digital signature, information can be altered by unauthorized accounts accessing or modifying the container platform registry, keystore, and container at runtime. Digital signatures provide non-repudiation for transactions between the components within the container platform. Without the use of approved FIPS-validated SHA-2 or higher hash function with digital signatures, the container platform cannot claim the validity of the individual or service identity and guarantee private key is kept secret. Keeping the private keys secure is vital for validating individuals or service identity prior to information exchange. The container platform must be configured to use SHA-2 or higher hash functions for digital signatures in accordance with SP 800-131Ar2.

Check Content

Review the container platform configuration to validate that a FIPS-validated SHA-2 or higher hash function is being used for digital signature generation and verification. 

If a FIPS-validated SHA-2 or higher hash function is not being used for digital signature generation and verification, this is a finding.

Fix Text

Configure the container platform to use a FIPS-validated SHA-2 or higher hash function for digital signature generation and verification.