808bits

Ascom Smartphone BoringCrypto

FIPS 140-2 certificate #4276 · Ascom Sweden AB · data as of 2026-10-09

Ascom Smartphone BoringCrypto, from Ascom Sweden AB, holds FIPS 140-2 certificate #4276 at overall level 1. The validation is historical: agencies may keep the module in existing systems but not buy it new. Below are its validation history, algorithm certificates and security policy, drawn from the NIST CMVP entry.

Historical. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When installed, initialized and configured as specified in Section 12.1 of the Security Policy and operated in FIPS mode. The module generates cryptographic keys whose strengths are modified by available entropy

Certificate

Certificate number4276
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorAscom Sweden AB · website
Software versions7f02881e96e51f1873afcf384d02f782b48967ca

Module description

Quoted from the NIST CMVP entry for this certificate.

Ascom Smartphone BoringCrypto 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 (10)

AlgorithmCAVP certificates
AESC1314
CVLC1314
DRBGC1314
ECDSAC1314
HMACC1314
KAS-SSCvendor affirmed
KTS
RSAC1314
SHSC1314
Triple-DESC1314

Allowed algorithms

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

Tested configurations

  • Android 10 running on Pixel 3 XL with Snapdragon 845 32-bit with PAA
  • Android 10 running on Pixel 3 XL with Snapdragon 845 32-bit without PAA
  • Android 10 running on Pixel 3 XL with Snapdragon 845 64-bit with PAA
  • Android 10 running on Pixel 3 XL with Snapdragon 845 64-bit without PAA
  • Android 10 running on Pixel 3a with Snapdragon 670 32-bit with PAA
  • Android 10 running on Pixel 3a with Snapdragon 670 32-bit without PAA
  • Android 10 running on Pixel 3a with Snapdragon 670 64-bit with PAA
  • Android 10 running on Pixel 3a with Snapdragon 670 64-bit without PAA
  • Android 10 running on Pixel 4 XL with Snapdragon 855 32-bit with PAA
  • Android 10 running on Pixel 4 XL with Snapdragon 855 32-bit without PAA
  • Android 10 running on Pixel 4 XL with Snapdragon 855 64-bit with PAA
  • Android 10 running on Pixel 4 XL with Snapdragon 855 64-bit without PAA (single user mode)

Validation history

DateTypeLab
2022-08-08InitialAcumen 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
  • Validation dates on record: 2022-08-08

Source documents