808bits

Samsung SCrypto Cryptographic Module

FIPS 140-2 certificate #4383 · Samsung Electronics Co., Ltd. · data as of 2026-08-28
Active. Sunset date 2026-09-21, 23 days away. This is the FIPS 140-2 sunset: after it, agencies may keep the module only in existing systems.
Caveat: When operated in FIPS mode

Certificate

Certificate number4383
StandardFIPS 140-2
Statusactive
Sunset date2026-09-21
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorSamsung Electronics Co., Ltd.
Software versions2.6

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
AESA915
CVLA915
DRBGA915
ECDSAA915
ENT
HMACA915
KBKDFA915
KTS
RSAA915
SHSA915

Allowed algorithms

RSA (Cert. #A915, key wrapping; key establishment methodology provides 112 bits of encryption strength)

Tested configurations

  • QSEE 5.18 (64-bit) running on Samsung Galaxy S22+ with Qualcomm Snapdragon 8 Gen 1
  • QSEE 5.18 (64-bit) running on Samsung Galaxy Z Flip 4 with Qualcomm Snapdragon 8+ Gen 1 (single-user mode)
  • TEEGRIS 4.2 (32-bit) running on Samsung Galaxy S21+ with Samsung Electronics Exynos 2100
  • TEEGRIS 4.2 (32-bit) running on Samsung Galaxy Watch 4 with Samsung Electronics Exynos W920
  • TEEGRIS 4.2 (64-bit) running on Samsung Galaxy S21+ with Samsung Electronics Exynos 2100
  • TEEGRIS 4.2.1 (64-bit) running on Samsung Galaxy A53 with Samsung Electronics Exynos 1280
  • TEEGRIS 4.2.1 (64-bit) running on Samsung Galaxy S22+ with Samsung Electronics Exynos 2200

Validation history

DateTypeLab
2022-12-03InitialGossamer Security Solutions
2024-05-24UpdateGossamer 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 active
  • Validation dates on record: 2022-12-03, 2024-05-24

Source documents