808bits

Honeywell Mobility EdgeTM BoringCrypto

FIPS 140-2 certificate #4685 · Honeywell International, Inc. · 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 number4685
StandardFIPS 140-2
Statusactive
Sunset date2026-09-21
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorHoneywell International, Inc.
Software versionsdcdc7bbc6e59ac0123407a9dc4d1f43dd0d117cd

Module description

Honeywell Mobility Edge BoringSSL cryptographic module is a library that provides FIPS 140-2 approved cryptographic algorithms for the BoringSSL and other user-space Android applications which require cryptographic functionality. The physical cryptographic boundary is Honeywell Android mobile computer on which this module is installed.

Security level exceptions

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

Approved algorithms

AlgorithmCAVP certificate
AESA4657
CVLA4657
DRBGA4657
ECDSAA4657
HMACA4657
KAS
KAS-SSCA4657
KTS
RSAA4657
SHSA4657
Triple-DESA4657

Allowed algorithms

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

Tested configurations

  • Android 12 running on Honeywell Mobility Edge CT47 with Qualcomm Snapdragon 6490 (QCM6490) 32-bit with PAA
  • Android 12 running on Honeywell Mobility Edge CT47 with Qualcomm Snapdragon 6490 (QCM6490) 32-bit without PAA
  • Android 12 running on Honeywell Mobility Edge CT47 with Qualcomm Snapdragon 6490 (QCM6490) 64-bit with PAA
  • Android 12 running on Honeywell Mobility Edge CT47 with Qualcomm Snapdragon 6490 (QCM6490) 64-bit without PAA

Validation history

DateTypeLab
2024-04-02InitialAcumen 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: 2024-04-02

Source documents