808bits

Ascom Smartphone BoringCrypto v2

FIPS 140-2 certificate #4463 · Ascom Sweden AB · 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 number4463
StandardFIPS 140-2
Statusactive
Sunset date2026-09-21
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorAscom Sweden AB
Software versionsdcdc7bbc6e59ac0123407a9dc4d1f43dd0d117cd

Module description

Ascom Smartphone BoringCrypto v2 is a general-purpose cryptographic library incorporated into the Ascom Myco smartphones for the protection of sensitive information.

Security level exceptions

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

Approved algorithms

AlgorithmCAVP certificate
AESA1109
CVLA1109
DRBGA1109
ECDSAA1109
HMACA1109
KAS
KAS-SSCA1109
KTS
RSAA1109
SHSA1109
Triple-DESA1109

Allowed algorithms

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

Tested configurations

  • Android 12 running on Google Pixel 3 XL with Qualcomm Snapdragon 845 (SDM845) 32-bit with PAA
  • Android 12 running on Google Pixel 3 XL with Qualcomm Snapdragon 845 (SDM845) 32-bit without PAA
  • Android 12 running on Google Pixel 3 XL with Qualcomm Snapdragon 845 (SDM845) 64-bit with PAA
  • Android 12 running on Google Pixel 3 XL with Qualcomm Snapdragon 845 (SDM845) 64-bit without PAA
  • Android 12 running on Google Pixel 3a XL with Qualcomm Snapdragon 670 (SDM670) 32-bit with PAA
  • Android 12 running on Google Pixel 3a XL with Qualcomm Snapdragon 670 (SDM670) 32-bit without PAA
  • Android 12 running on Google Pixel 3a XL with Qualcomm Snapdragon 670 (SDM670) 64-bit with PAA
  • Android 12 running on Google Pixel 3a XL with Qualcomm Snapdragon 670 (SDM670) 64-bit without PAA
  • Android 12 running on Google Pixel 4 XL with Qualcomm Snapdragon 855 (SDM855) 32-bit with PAA
  • Android 12 running on Google Pixel 4 XL with Qualcomm Snapdragon 855 (SDM855) 32-bit without PAA
  • Android 12 running on Google Pixel 4 XL with Qualcomm Snapdragon 855 (SDM855) 64-bit with PAA
  • Android 12 running on Google Pixel 4 XL with Qualcomm Snapdragon 855 (SDM855) 64-bit without PAA
  • Android 12 running on Google Pixel 4a with Qualcomm Snapdragon 730G (SDM730) 32-bit with PAA
  • Android 12 running on Google Pixel 4a with Qualcomm Snapdragon 730G (SDM730) 32-bit without PAA
  • Android 12 running on Google Pixel 4a with Qualcomm Snapdragon 730G (SDM730) 64-bit with PAA
  • Android 12 running on Google Pixel 4a with Qualcomm Snapdragon 730G (SDM730) 64-bit without PAA
  • Android 12 running on Google Pixel 4a-5G with Qualcomm Snapdragon 765G (SDM765) 32-bit with PAA
  • Android 12 running on Google Pixel 4a-5G with Qualcomm Snapdragon 765G (SDM765) 32-bit without PAA
  • Android 12 running on Google Pixel 4a-5G with Qualcomm Snapdragon 765G (SDM765) 64-bit with PAA
  • Android 12 running on Google Pixel 4a-5G with Qualcomm Snapdragon 765G (SDM765) 64-bit without PAA
  • Android 12 running on Google Pixel 5 with Qualcomm Snapdragon 765G (SDM765) 32-bit with PAA
  • Android 12 running on Google Pixel 5 with Qualcomm Snapdragon 765G (SDM765) 32-bit without PAA
  • Android 12 running on Google Pixel 5 with Qualcomm Snapdragon 765G (SDM765) 64-bit with PAA
  • Android 12 running on Google Pixel 5 with Qualcomm Snapdragon 765G (SDM765) 64-bit without PAA
  • Android 12 running on Google Pixel 6 with Google Tensor/Mali-G78 MP20 32-bit with PAA
  • Android 12 running on Google Pixel 6 with Google Tensor/Mali-G78 MP20 32-bit without PAA (single-user mode)
  • Android 12 running on Google Pixel 6 with Google Tensor/Mali-G78 MP20 64-bit with PAA
  • Android 12 running on Google Pixel 6 with Google Tensor/Mali-G78 MP20 64-bit without PAA

Validation history

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

Source documents