808bits

BoringCrypto

FIPS 140-2 certificate #4407 · Google, LLC. · 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 number4407
StandardFIPS 140-2
Statusactive
Sunset date2026-09-21
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorGoogle, LLC. · website
Software versions853ca1ea1168dff08011e5d42d94609cc0ca2e27

Module description

A software library that contains cryptographic functionality to serve BoringSSL and other user-space applications.

Security level exceptions

  • Physical Security: N/A
  • Mitigation of Other Attacks: N/A

Approved algorithms

AlgorithmCAVP certificate
AESA1657
CVLA1657
DRBGA1657
ECDSAA1657
HMACA1657
KAS
KAS-SSCA1657
KTS
RSAA1657
SHSA1657
Triple-DESA1657

Allowed algorithms

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

Tested configurations

  • Debian Linux 5.10.40 (Rodete) running on HPE Z620 with Intel Xeon E5-2680 with PAA
  • Debian Linux 5.10.40 (Rodete) running on HPE Z620 with Intel Xeon E5-2680 without PAA
  • Google prodimage with Linux 4.15.0 running on Ampere Altra SoC with ARM Neoverse N1 with PAA
  • Google prodimage with Linux 4.15.0 running on Ampere Altra SoC with ARM Neoverse N1 without PAA (single-user mode)
  • Google prodimage with Linux 4.15.0 running on Google Arcadia-Rome with AMD Rome with PAA
  • Google prodimage with Linux 4.15.0 running on Google Arcadia-Rome with AMD Rome without PAA

Validation history

DateTypeLab
2023-01-04InitialAcumen 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: 2023-01-04

Source documents