808bits

BoringCrypto SoC

FIPS 140-2 certificate #4444 · 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 number4444
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, A1727
CVLA1657, A1727
DRBGA1657, A1727
ECDSAA1657, A1727
HMACA1657, A1727
KAS-SSCA1657, A1727
KTS
RSAA1657, A1727
SHSA1657, A1727
Triple-DESA1657, A1727

Allowed algorithms

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

Tested configurations

  • Google prodimage with Linux 4.15.0 running on Ampere Altra SoC with ARM Neoverse N1 CPU with PAA
  • Google prodimage with Linux 4.15.0 running on Ampere Altra SoC with ARM Neoverse N1 CPU without PAA (single-user mode)
  • Google prodimage with Linux 5.4.99 running on Google IN762 SoC with Aarch64 ARMv8 CPU with PAA
  • Google prodimage with Linux 5.4.99 running on Google IN762 SoC with Aarch64 ARMv8 CPU without PAA

Validation history

DateTypeLab
2023-02-27InitialAcumen 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-02-27

Source documents