808bits

Honeywell Mobility Edge™ BoringCrypto

FIPS 140-2 certificate #3448 · Honeywell International, Inc · data as of 2026-10-21

Honeywell Mobility Edge™ BoringCrypto, from Honeywell International, Inc, holds FIPS 140-2 certificate #3448 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 operated in FIPS mode. The module generates cryptographic keys whose strengths are modified by available entropy. This validation entry is a non-security relevant modification to Cert. #2964.

Certificate

Certificate number3448
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorHoneywell International, Inc · website
Software versions1.0

Module description

Quoted from the NIST CMVP entry for this certificate.

Honeywell Mobility Edge™ BoringCrypto 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 computer on which this module is installed.

Security level exceptions

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

Approved algorithms (9)

AlgorithmCAVP certificates
AESC430
CVLC430
DRBGC430
ECDSAC430
HMACC430
KTS
RSAC430
SHSC430
Triple-DESC430

Allowed algorithms

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

Tested configurations

  • Android 8.1.0 running on CN80 with Qualcomm Snapdragon 660 (ARMv8) (single-user mode)

Validation history

DateTypeLab
2019-04-30InitialAcumen 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: 2019-04-30

Source documents