808bits

LG Framework Cryptographic Module

FIPS 140-2 certificate #2662 · LG Electronics, 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 operated in FIPS mode. The protocol TLS shall not be used when operated in FIPS mode. No assurance of the minimum strength of generated keys. The module generates cryptographic keys whose strengths are modified by available entropy

Certificate

Certificate number2662
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorLG Electronics, Inc. · website
Software versions1.0.0

Module description

The LG Framework Cryptographic Module is a software library that provides cryptographic functionality.

Security level exceptions

  • Physical Security: N/A

Approved algorithms

AlgorithmCAVP certificate
AES3289
DRBG748
DSA943
HMAC2087
RSA1683
SHS2728
Triple-DES1874

Other algorithms

Diffie-Hellman (key agreement; key establishment methodology provides between 112 and 192 bits of encryption strength; non-compliant less than 112 bits of encryption strength); EC Diffie-Hellman (key agreement; key establishment methodology provides between 112 and 256 bits of encryption strength; non-compliant less than 112 bits of encryption strength); RSA (key wrapping; key establishment methodology provides 112 or 128 bits of encryption strength); PRNG; ECDSA (non-compliant); TLS KDF (non-compliant)

Tested configurations

  • Android 5.0.1 running on an LG G Flex 2 (Model LGLS996) (single-user mode)
  • Android 5.0.1 running on an LG G3 (Model VS985)

Validation history

DateTypeLab
2016-06-17InitialUL Verification Services, Inc.
2016-09-02UpdateUL Verification Services, Inc.

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: 2016-06-17, 2016-09-02

Source documents