808bits

Avaya BoringCrypto Android

FIPS 140-2 certificate #4040 · Avaya, Inc. · data as of 2026-10-09

Avaya BoringCrypto Android, from Avaya, Inc., holds FIPS 140-2 certificate #4040 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

Certificate

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

Module description

Quoted from the NIST CMVP entry for this certificate.

Avaya BoringCrypto Android 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.

Security level exceptions

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

Approved algorithms (10)

AlgorithmCAVP certificates
AESC1910
CVLC1910
DRBGC1910
ECDSAC1910
HMACC1910
KAS-SSCvendor affirmed
KTS
RSAC1910
SHSC1910
Triple-DESC1910

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 Avaya Vantage™ K155 with RockChip 3399 (32-bit core) with PAA
  • Android 9 running on Avaya Vantage™ K155 with RockChip 3399 (32-bit core) without PAA
  • Android 9 running on Avaya Vantage™ K155 with RockChip 3399 (32-bit vendor) with PAA
  • Android 9 running on Avaya Vantage™ K155 with RockChip 3399 (32-bit vendor) without PAA
  • Android 9 running on Avaya Vantage™ K155 with RockChip 3399 (64-bit core) with PAA
  • Android 9 running on Avaya Vantage™ K155 with RockChip 3399 (64-bit core) without PAA
  • Android 9 running on Avaya Vantage™ K155 with RockChip 3399 (64-bit vendor) with PAA
  • Android 9 running on Avaya Vantage™ K155 with RockChip 3399 (64-bit vendor) without PAA
  • Android 9 running on Avaya Vantage™ K175 with RockChip 3399 (32-bit core) with PAA
  • Android 9 running on Avaya Vantage™ K175 with RockChip 3399 (32-bit core) without PAA
  • Android 9 running on Avaya Vantage™ K175 with RockChip 3399 (32-bit vendor) with PAA
  • Android 9 running on Avaya Vantage™ K175 with RockChip 3399 (32-bit vendor) without PAA
  • Android 9 running on Avaya Vantage™ K175 with RockChip 3399 (64-bit core) with PAA
  • Android 9 running on Avaya Vantage™ K175 with RockChip 3399 (64-bit core) without PAA
  • Android 9 running on Avaya Vantage™ K175 with RockChip 3399 (64-bit vendor) with PAA
  • Android 9 running on Avaya Vantage™ K175 with RockChip 3399 (64-bit vendor) without PAA (single-user mode)

Validation history

DateTypeLab
2021-10-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 historical
  • Validation dates on record: 2021-10-05

Source documents