Module Name
Samsung BoringSSL Cryptographic Module
Validation Dates
12/21/2020
Caveat
When operated in FIPS mode
Security Level Exceptions
- Physical Security: N/A
- EMI/EMC: Level 3
- Design Assurance: Level 3
- Mitigation of Other Attacks: N/A
Embodiment
Multi-Chip Stand Alone
Description
Provides general purpose cryptographic services to user-space applications on the mobile platform for the protection of data.
Tested Configuration(s)
- Android 10 with processor Qualcomm MSM8998 running on Samsung Galaxy Tab S4
- Android 10 with processor Qualcomm SDM450 running on Samsung Galaxy Tab A 10.5 (single-user mode)
- Android 10 with processor Qualcomm SDM845 running on Samsung Galaxy S9+
- Android 10 with processor Qualcomm SM7250 running on Samsung Galaxy A71
- Android 10 with processor Qualcomm SM8150 running on Samsung Galaxy S10+
- Android 10 with processor Qualcomm SM8250 running on Samsung Galaxy S20+
- Android 10 with processor Samsung Electronics Exynos 9611 running on Samsung Galaxy Xcover Pro
- Android 10 with processor Samsung Electronics Exynos 9810 running on Samsung Galaxy S9+
- Android 10 with processor Samsung Electronics Exynos 9820 running on Samsung Galaxy S10+
- Android 10 with processor Samsung Electronics Exynos 9825 running on Samsung Galaxy Note10+
- Android 10 with processor Samsung Electronics Exynos 990 running on Samsung Galaxy S20+
FIPS Algorithms
| AES |
Cert. #C1350 |
| CKG |
vendor affirmed |
| CVL |
Cert. #C1350 |
| DRBG |
Cert. #C1350 |
| ECDSA |
Cert. #C1350 |
| HMAC |
Cert. #C1350 |
| KBKDF |
Cert. #C1350 |
| KTS |
AES Cert. #C1350; key establishment methodology provides 128 or 256 bits of encryption strength |
| RSA |
Cert. #C1350 |
| SHS |
Cert. #C1350 |
Allowed Algorithms
Diffie-Hellman (key agreement; key establishment methodology provides between 112 and 150 bits of encryption strength); EC Diffie-Hellman (CVL Cert. #C1350, key agreement; key establishment methodology provides between 112 and 256 bits of encryption strength); NDRNG; RSA (CVL Cert. #C1350, key wrapping; key establishment methodology provides 112 or 128 bits of encryption strength)
) or https:// don't prove our archive is authentic, only that you securely accessed it. Note that we are working to fix that :)
