808bits

Samsung BoringSSL Cryptographic Module

FIPS 140-2 certificate #2991 · 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 number2991
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorSamsung Electronics Co., Ltd.
Software versions1.1

Module description

Provides general purpose cryptographic services to user-space applications on the mobile platform for the protection of data.

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
AES4432
CVL1142, 1143
DRBG1431
DSA1189
ECDSA1074
HMAC2944
KTS
RSA2413
SHS3650

Allowed algorithms

Diffie-Hellman (Key agreement; key establishment methodology provides between 112 and 150 bits of encryption strength); EC Diffie-Hellman (Key agreement; key establishment methodology provides between 112 and 256 bits of encryption strength); NDRNG; RSA (key wrapping; key establishment methodology provides between 112 and 128 bits of encryption strength)

Tested configurations

  • Android 7.0 with processor Qualcomm MSM8917 running on Samsung Galaxy J3
  • Android 7.0 with processor Qualcomm MSM8996 running on Samsung Galaxy S7 Edge
  • Android 7.0 with processor Qualcomm MSM8996 running on Samsung Galaxy Tab S3
  • Android 7.0 with processor Qualcomm MSM8998 running on Samsung Galaxy S8+
  • Android 7.0 with processor Samsung EXYNOS7420 running on Samsung Galaxy S6 Edge
  • Android 7.0 with processor Samsung EXYNOS7570 running on Samsung Galaxy J3
  • Android 7.0 with processor Samsung EXYNOS8890 running on Samsung Galaxy S7 Edge
  • Android 7.0 with processor Samsung EXYNOS8895 running on Samsung Galaxy S8
  • Android 7.1 with processor Samsung EXYNOS7870 running on Samsung Tab Active2 (single-user mode)

Validation history

DateTypeLab
2017-08-10InitialGossamer Security Solutions
2017-10-27UpdateGossamer 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-08-10, 2017-10-27

Source documents