808bits

Honeywell Mobility Edge™ BoringCrypto

FIPS 140-2 certificate #3828 · Honeywell International Inc. · data as of 2026-08-28
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 number3828
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorHoneywell International Inc. · website
Software versions2.0

Module description

Honeywell Mobility Edge™ Boring SSL 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
AESC1774
CVLC1774
DRBGC1774
ECDSAC1774
HMACC1774
KAS-SSCvendor affirmed
KTS
RSAC1774
SHSC1774
Triple-DESC1774

Allowed algorithms

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

Tested configurations

  • Android 9 running on Honeywell Mobility Edge CN80 with Qualcomm ® 660 32-bit with PAA
  • Android 9 running on Honeywell Mobility Edge CN80 with Qualcomm ® 660 32-bit without PAA (single-user mode)
  • Android 9 running on Honeywell Mobility Edge CN80 with Qualcomm ® 660 64-bit with PAA
  • Android 9 running on Honeywell Mobility Edge CN80 with Qualcomm ® 660 64-bit without PAA

Validation history

DateTypeLab
2021-02-25InitialAcumen 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: 2021-02-25

Source documents