808bits

HP Poly Cryptographic Module

FIPS 140-3 certificate #5011 · Hewlett Packard, 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 number5011
StandardFIPS 140-3
Statusactive
Sunset date2029-07-22
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorHewlett Packard, Inc. · website
Software versions2022061300

Module description

The HP Poly Cryptographic Module is a general-purpose cryptographic library incorporated into the CCX line of products to provide FIPS 140-3 validated cryptography for the protection of sensitive information.

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-CBCA6962
AES-CCMA2811
AES-CCMA6962
AES-CTRA2811
AES-CTRA6962
AES-ECBA2811
AES-ECBA6962
AES-GCMA2811
AES-GCMA6962
AES-KWA2811
AES-KWA6962
AES-KWPA2811
AES-KWPA6962
Counter DRBGA2811
Counter DRBGA6962
ECDSA KeyGen (FIPS186-4)A2811
ECDSA KeyGen (FIPS186-4)A6962
ECDSA KeyVer (FIPS186-4)A2811
ECDSA KeyVer (FIPS186-4)A6962
ECDSA SigGen (FIPS186-4)A2811
ECDSA SigGen (FIPS186-4)A6962
ECDSA SigVer (FIPS186-4)A2811
ECDSA SigVer (FIPS186-4)A6962
HMAC-SHA-1A2811
HMAC-SHA-1A6962
HMAC-SHA2-224A2811
HMAC-SHA2-224A6962
HMAC-SHA2-256A2811
HMAC-SHA2-256A6962
HMAC-SHA2-384A2811
HMAC-SHA2-384A6962
HMAC-SHA2-512A2811
HMAC-SHA2-512A6962
KAS-ECC-SSC Sp800-56Ar3A2811
KAS-ECC-SSC Sp800-56Ar3A6962
KDF TLSA2811
KDF TLSA6962
RSA KeyGen (FIPS186-4)A2811
RSA KeyGen (FIPS186-4)A6962
RSA SigGen (FIPS186-4)A2811
RSA SigGen (FIPS186-4)A6962
RSA SigVer (FIPS186-4)A2811
RSA SigVer (FIPS186-4)A6962
SHA-1A2811
SHA-1A6962
SHA2-224A2811
SHA2-224A6962
SHA2-256A2811
SHA2-256A6962
SHA2-384A2811
SHA2-384A6962
SHA2-512A2811
SHA2-512A6962
SHA2-512/256A2811
SHA2-512/256A6962

Tested configurations

  • Android 12 running on CCX 400 with Rockchip PX30 ARMv8-A with PAA
  • Android 12 running on CCX 600 with NXP i.MX 8M ARMv8-A with PAA
  • 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

Validation history

DateTypeLab
2025-04-29InitialAcumen Security
2025-12-15UpdateAcumen Security
2026-02-12UpdateAcumen Security
2026-05-14UpdateAcumen 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 active
  • Validation dates on record: 2025-04-29

Source documents