BoringCrypto SoC
BoringCrypto SoC, from Google, LLC., holds FIPS 140-2 certificate #4444 at overall level 1. The validation is historical: agencies may keep the module in existing systems but not buy it new. Below are its algorithm certificates, its validation history, and the list moves this tracker has observed, which NIST does not date.
Caveat: When operated in FIPS mode. No assurance of the minimum strength of generated keys.
Certificate
| Certificate number | 4444 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Software |
| Embodiment | Multi-Chip Stand Alone |
| Vendor | Google, LLC. · website |
| Software versions | 853ca1ea1168dff08011e5d42d94609cc0ca2e27 |
Module description
Quoted from the NIST CMVP entry for this certificate.
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 (10)
| Algorithm | CAVP certificates |
|---|---|
| AES | A1657, A1727 |
| CVL | A1657, A1727 |
| DRBG | A1657, A1727 |
| ECDSA | A1657, A1727 |
| HMAC | A1657, A1727 |
| KAS-SSC | A1657, A1727 |
| KTS | |
| RSA | A1657, A1727 |
| SHS | A1657, A1727 |
| Triple-DES | A1657, 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
| Date | Type | Lab |
|---|---|---|
| 2023-02-27 | Initial | Acumen 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 historical at the time of the earliest snapshot
- 2026-09-22: observed moving from active to historical
- Validation dates on record: 2023-02-27