808bits

Allegro Cryptographic Engine

FIPS 140-2 certificate #4627 · Allegro Software Development Corporation · 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 3 of the Security Policy

Certificate

Certificate number4627
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorAllegro Software Development Corporation · website
Software versions6.3.3

Module description

Allegro’s suite of Embedded Device Security toolkits makes embedding standards-based security protocols into resource sensitive embedded systems and consumer electronics fast, easy and reliable. The Allegro Cryptographic Engine (ACE) is a cryptographic library module specifically engineered for embedded devices. The module provides embedded systems developers with an easily understood software interface to enable bulk encryption and decryption, message digests, digital signature creation and validation and key generation and exchange. For full details see www.allegrosoft.com/ace.

Security level exceptions

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

Approved algorithms

AlgorithmCAVP certificate
AESA2685
CKGvendor affirmed
CVLA2685
DRBGA2685
ECDSAA2685
HMACA2685
KAS-SSCA2685
KTS
KTS
PBKDFvendor affirmed
RSAA2685
SHSA2685

Allowed algorithms

NDRNG; RSA (key wrapping; key establishment methodology provides 112 or 128 bits of encryption strength)

Tested configurations

  • Linux Mint 18 Cinnamon running on an Intel NUC6i7KYK System with Intel i7-6770HQ with PAA
  • Linux Mint 18 Cinnamon running on an Intel NUC6i7KYK System with Intel i7-6770HQ without PAA (single-user mode)

Validation history

DateTypeLab
2023-10-04InitialAcumen 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: 2023-10-04

Source documents