808bits

Samsung SCrypto Cryptographic Module

FIPS 140-2 certificate #3027 · Samsung Electronics Co., Ltd. · data as of 2026-08-28
Historical. SP 800-56Arev3 transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode

Certificate

Certificate number3027
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorSamsung Electronics Co., Ltd.
Software versions2.0

Module description

SCrypto is secure library which is used to provide a standardized common cryptographic API to trusted applications for the secure world/TEE environment.

Security level exceptions

  • Physical Security: N/A
  • EMI/EMC: Level 3
  • Design Assurance: Level 3
  • Mitigation of Other Attacks: N/A

Approved algorithms

AlgorithmCAVP certificate
AES4389
CVL1092, 1093
DRBG1412
DSA1169
ECDSA1049
HMAC2916
KBKDF125
KTS
RSA2372
SHS3618

Allowed algorithms

Diffie-Hellman (CVL Cert. #1092, key agreement; key establishment methodology provides between 112 and 150 bits of encryption strength); EC Diffie-Hellman (CVL Cert. #1092, key agreement; key establishment methodology provides between 112 and 256 bits of encryption strength); NDRNG; RSA (CVL Cert. #1093, key wrapping; key establishment methodology provides 112 or 128 bits of encryption strength)

Tested configurations

  • Kinibi 310 (32-bit) with processor Samsung EXYNOS7870 running on Samsung Tab Active2 (single-user mode)
  • Kinibi 400A (32-bit) with processor Samsung EXYNOS8895 running on Samsung Galaxy S8
  • QSEE 4.0 (32-bit) with processor Qualcomm MSM8998 running on Samsung Galaxy S8+
  • QSEE 4.0 (64-bit) with processor Qualcomm MSM8998 running on Samsung Galaxy S8+

Validation history

DateTypeLab
2017-09-25InitialGossamer Security Solutions
2017-10-27UpdateGossamer Security Solutions
2018-07-20UpdateGossamer Security Solutions

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: 2017-09-25, 2017-10-27, 2018-07-20

Source documents