808bits

Samsung BoringSSL Android

FIPS 140-2 certificate #4216 · 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. No assurance of the minimum strength of generated keys.

Certificate

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

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
  • Mitigation of Other Attacks: N/A

Approved algorithms

AlgorithmCAVP certificate
AESA2351
CVLA2351
DRBGA2351
ECDSAA2351
HMACA2351
KAS
KAS-SSCA2351
KTS
RSAA2351
SHSA2351
Triple-DESA2351

Allowed algorithms

MD5; RSA (key wrapping; key establishment methodology provides between 112 and 256 bits of encryption strength)

Tested configurations

  • Android 12 running on Galaxy A71 5G with Qualcomm Snapdragon 765 with PAA
  • Android 12 running on Galaxy A71 5G with Qualcomm Snapdragon 765 without PAA
  • Android 12 running on Galaxy Tab Active3 with Exynos 9810 with PAA
  • Android 12 running on Galaxy Tab Active3 with Exynos 9810 without PAA
  • Android 12 running on Galaxy XCover6 Pro Qualcomm Snapdragon 778G with PAA
  • Android 12 running on Galaxy XCover6 Pro Qualcomm Snapdragon 778G without PAA (single-user mode)
  • Android 12 running on Galaxy XCoverPro with Exynos 9611 with PAA
  • Android 12 running on Galaxy XCoverPro with Exynos 9611 without PAA
  • Android 12 running on Galaxy Z Flip 4 5G with Snapdragon 8+ Gen 1 Mobile Platform with PAA
  • Android 12 running on Galaxy Z Flip 4 5G with Snapdragon 8+ Gen 1 Mobile Platform without PAA
  • Android 12 running on Samsung Galaxy A52 with Qualcomm Snapdragon 750 with PAA
  • Android 12 running on Samsung Galaxy A52 with Qualcomm Snapdragon 750 without PAA
  • Android 12 running on Samsung Galaxy A53 with Samsung Exynos 1280 with PAA
  • Android 12 running on Samsung Galaxy A53 with Samsung Exynos 1280 without PAA
  • Android 12 running on Samsung Galaxy Note10+ with Samsung Exynos 9825 with PAA
  • Android 12 running on Samsung Galaxy Note10+ with Samsung Exynos 9825 without PAA
  • Android 12 running on Samsung Galaxy S10+ with Qualcomm Snapdragon 855 with PAA
  • Android 12 running on Samsung Galaxy S10+ with Qualcomm Snapdragon 855 without PAA
  • Android 12 running on Samsung Galaxy S10+ with Samsung Exynos 9820 with PAA
  • Android 12 running on Samsung Galaxy S10+ with Samsung Exynos 9820 without PAA
  • Android 12 running on Samsung Galaxy S20+ 5G with Qualcomm Snapdragon 865 with PAA
  • Android 12 running on Samsung Galaxy S20+ 5G with Qualcomm Snapdragon 865 without PAA
  • Android 12 running on Samsung Galaxy S20+ 5G with Samsung Exynos 990 with PAA
  • Android 12 running on Samsung Galaxy S20+ 5G with Samsung Exynos 990 without PAA
  • Android 12 running on Samsung Galaxy S21+ with Qualcomm Snapdragon 888 with PAA
  • Android 12 running on Samsung Galaxy S21+ with Qualcomm Snapdragon 888 without PAA
  • Android 12 running on Samsung Galaxy S21+ with Samsung Exynos 2100 with PAA
  • Android 12 running on Samsung Galaxy S21+ with Samsung Exynos 2100 without PAA
  • Android 12 running on Samsung Galaxy S22 Ultra with Qualcomm Snapdragon 8 Gen 1 Mobile Platforms with PAA
  • Android 12 running on Samsung Galaxy S22 Ultra with Qualcomm Snapdragon 8 Gen 1 Mobile Platforms without PAA
  • Android 12 running on Samsung Galaxy S22 Ultra with Samsung Exynos 2200 with PAA
  • Android 12 running on Samsung Galaxy S22 Ultra with Samsung Exynos 2200 without PAA

Validation history

DateTypeLab
2022-05-09InitialAcumen Security
2022-11-18UpdateAcumen Security

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-05-09, 2022-11-18

Source documents