808bits

Samsung CryptoCore Module

FIPS 140-2 certificate #2474 · Samsung Electronics Co., Ltd. · 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. The module generates cryptographic keys whose strengths are modified by available entropy

Certificate

Certificate number2474
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorSamsung Electronics Co., Ltd. · website
Software versions0.2.9

Module description

A multipurpose cryptographic library which provides symmetric/asymmetric cipher, message digest, key agreement, and PRNG services.

Security level exceptions

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

Approved algorithms

AlgorithmCAVP certificate
AES3459, 3460
CVL530, 537
DRBG847, 848
DSA976, 977
ECDSA700, 701
HMAC2205, 2206
RSA1774, 1775
SHS2855, 2856
Triple-DES1950, 1951

Other algorithms

DES; Diffie-Hellman (key agreement; key establishment methodology provides between 112 bits and 150 bits of encryption strength; non-compliant less than 112 bits of encryption strength); EC Diffie-Hellman (CVL Certs. #530 and #537, key agreement; key establishment methodology provides between 112 bits and 256 bits of encryption strength; non-compliant less than 112 bits of encryption strength); HMAC-MD5; IBS; MD5; RC4; RSA (key wrapping; key establishment methodology provides 112 bits or 128 bits of encryption strength; non-compliant less than 112 bits of encryption strength); SNOW2; NDRNG; RNG

Tested configurations

  • Tizen 2.3 running on Samsung UN55JU6700 with Samsung Hawk-MU (single-user mode)
  • Ubuntu 14.04 running on Lenovo T540p with Intel i7

Validation history

DateTypeLab
2015-11-16Initialatsec information security corporation
2016-03-22Updateatsec information security corporation
2016-03-24Updateatsec information security corporation

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: 2015-11-16, 2016-03-22, 2016-03-24

Source documents