808bits

Samsung SCrypto Cryptographic Module

FIPS 140-2 certificate #4576 · Samsung Electronics Co., Ltd. · data as of 2026-10-21

Samsung SCrypto Cryptographic Module, from Samsung Electronics Co., Ltd., holds FIPS 140-2 certificate #4576 at overall level 1. The validation is historical: agencies may keep the module in existing systems but not buy it new. Below are its validation history, algorithm certificates and security policy, drawn from the NIST CMVP entry.

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

Certificate

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

Module description

Quoted from the NIST CMVP entry for this certificate.

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 (11)

AlgorithmCAVP certificates
AES5180
CKGvendor affirmed
CVL1682
DRBG1955
DSA1344
ECDSA1343
HMAC3436
KBKDF175
KTS
RSA2781
SHS4184

Allowed algorithms

NDRNG; RSA (CVL Cert. #1682, key wrapping; key establishment methodology provides 112 or 128 bits of encryption strength)

Tested configurations

  • Kinibi 400A (32-bit) with processor Electronics Exynos9810 running on Samsung Galaxy S9+
  • QSEE 5.0 (32-bit) with processor Qualcomm SDM845 running on Samsung Galaxy S9+
  • QSEE 5.0 (64-bit) with processor Qualcomm SDM845 running on Samsung Galaxy S9+ (single-user mode)

Validation history

DateTypeLab
2023-08-31InitialGossamer 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: 2023-08-31

Source documents