808bits

Cloudian cryptographic module

FIPS 140-2 certificate #3663 · Cloudian, Inc. · data as of 2026-08-28
Historical. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode. No assurance of the minimum strength of generated keys. This validation entry is a non-security-relevant modification to Cert. #2398.

Certificate

Certificate number3663
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorCloudian, Inc. · website
Software versions1.0

Module description

Cloudian cryptographic module is an element of Cloudian HyperStore. Cloudian HyperStore is a software-defined object storage platform that provides a secure multi-tenant data store for unstructured data. HyperStore object storage can be deployed and scaled out as a global cluster of nodes to deliver capacity storage which scales seamlessly. It's the industry's most compatible S3 API based object storage solution.

Security level exceptions

  • Physical Security: N/A
  • Mitigation of Other Attacks: N/A

Approved algorithms

AlgorithmCAVP certificate
AESC1361
CVLC1361
DRBGC1361
DSAC1361
ECDSAC1361
HMACC1361
RSAC1361
SHSC1361
Triple-DESC1361

Allowed algorithms

EC Diffie-Hellman (CVL Cert. #C1361; key agreement; key establishment methodology provides between 112 and 256 bits of encryption strength); RSA (key wrapping; key establishment methodology provides between 112 and 256 bits of encryption strength)

Tested configurations

  • CentOS 7.4 on Vmware ESXi 6.5.0 running on a Dell PowerEdge T140 with an Intel® Xeon® E-2174G CPU @ 3.80GHz with PAA (single-user mode)
  • CentOS 7.4 running on a Supermicro MicroCloud SYS-5038MR-H8TRF with an Intel® Xeon® CPU E5-2640 v3 @ 2.60GHz with PAA

Validation history

DateTypeLab
2020-05-29InitialADVANCED DATA SECURITY

Status timeline

As observed by this tracker's snapshots. NIST publishes no dates for list moves; observation began 2026-08-21, so earlier changes carry no date.

  • 2026-08-21: first observed by this tracker, status historical
  • Validation dates on record: 2020-05-29

Source documents