808bits

Spectro Cloud Cryptographic Library

FIPS 140-3 certificate #5061 · Spectro Cloud, Inc. · data as of 2026-08-28
Active. Sunset date 2029-07-22, 1058 days away.
Caveat: No assurance of the minimum strength of generated SSPs (e.g., keys). When operated in approved mode.

Certificate

Certificate number5061
StandardFIPS 140-3
Statusactive
Sunset date2029-07-22
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorSpectro Cloud, Inc. · website
Software versionsv2

Module description

The Spectro Cloud Cryptographic Library v2 is a general-purpose cryptographic module incorporated into the applications to provide FIPS 140-3 validated cryptography for the protection of sensitive information. The module is pre-installed and configured in supported Spectro Cloud solutions, such as Palette VerteX.

Security level exceptions

  • Physical security: N/A
  • Non-invasive security: N/A
  • Mitigation of other attacks: N/A

Approved algorithms

AlgorithmCAVP certificate
AES-CBCA2811
AES-CCMA2811
AES-CTRA2811
AES-ECBA2811
AES-GCMA2811
AES-KWA2811
AES-KWPA2811
Counter DRBGA2811
ECDSA KeyGen (FIPS186-4)A2811
ECDSA KeyVer (FIPS186-4)A2811
ECDSA SigGen (FIPS186-4)A2811
ECDSA SigVer (FIPS186-4)A2811
HMAC-SHA-1A2811
HMAC-SHA2-224A2811
HMAC-SHA2-256A2811
HMAC-SHA2-384A2811
HMAC-SHA2-512A2811
KAS-ECC-SSC Sp800-56Ar3A2811
KDF TLSA2811
RSA KeyGen (FIPS186-4)A2811
RSA SigGen (FIPS186-4)A2811
RSA SigVer (FIPS186-4)A2811
SHA-1A2811
SHA2-224A2811
SHA2-256A2811
SHA2-384A2811
SHA2-512A2811
SHA2-512/256A2811

Tested configurations

  • Android 13 running on Google Pixel 4a with Qualcomm Snapdragon 730 32-bit with PAA
  • Android 13 running on Google Pixel 4a with Qualcomm Snapdragon 730 32-bit without PAA
  • Android 13 running on Google Pixel 4a with Qualcomm Snapdragon 730 64-bit with PAA
  • Android 13 running on Google Pixel 4a with Qualcomm Snapdragon 730 64-bit without PAA
  • Android 13 running on Google Pixel 4XL with Qualcomm Snapdragon 855 32-bit with PAA
  • Android 13 running on Google Pixel 4XL with Qualcomm Snapdragon 855 32-bit without PAA
  • Android 13 running on Google Pixel 4XL with Qualcomm Snapdragon 855 64-bit with PAA
  • Android 13 running on Google Pixel 4XL with Qualcomm Snapdragon 855 64-bit without PAA
  • Android 13 running on Google Pixel 5a with Qualcomm Snapdragon 765 32-bit with PAA
  • Android 13 running on Google Pixel 5a with Qualcomm Snapdragon 765 32-bit without PAA
  • Android 13 running on Google Pixel 5a with Qualcomm Snapdragon 765 64-bit with PAA
  • Android 13 running on Google Pixel 5a with Qualcomm Snapdragon 765 64-bit without PAA
  • Android 13 running on Google Pixel 6 Pro with Google Tensor 32-bit with PAA
  • Android 13 running on Google Pixel 6 Pro with Google Tensor 32-bit without PAA
  • Android 13 running on Google Pixel 6 Pro with Google Tensor 64-bit with PAA
  • Android 13 running on Google Pixel 6 Pro with Google Tensor 64-bit without PAA
  • Android 13 running on Google Pixel 7 Pro with Google Tensor G2 32-bit with PAA
  • Android 13 running on Google Pixel 7 Pro with Google Tensor G2 32-bit without PAA
  • Android 13 running on Google Pixel 7 Pro with Google Tensor G2 64-bit with PAA
  • Android 13 running on Google Pixel 7 Pro with Google Tensor G2 64-bit without PAA
  • Debian Linux 5.17.11 (Rodete) running on n2d with AMD EPYC 7B12 with PAA
  • Debian Linux 5.17.11 (Rodete) running on n2d with AMD EPYC 7B12 without PAA
  • Google Prodimage with Linux 4.15.0 running on n1 with Intel Xeon E5 2696 v4 with PAA
  • Google Prodimage with Linux 4.15.0 running on n1 with Intel Xeon E5 2696 v4 without PAA
  • Google Prodimage with Linux 4.15.0 running on Tau t2a with Ampere Altra with PAA
  • Google Prodimage with Linux 4.15.0 running on Tau t2a with Ampere Altra without PAA
  • Google Prodimage with Linux 5.10.120 running on IN762 with PAA
  • Google Prodimage with Linux 5.10.120 running on IN762 without PAA

Validation history

DateTypeLab
2025-09-17InitialTeron Labs
2026-01-06UpdateTeron Labs

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 active
  • Validation dates on record: 2025-09-17

Source documents