808bits

Delta Cryptographic Module

FIPS 140-2 certificate #3384 · Google, Inc. · data as of 2026-10-21

Delta Cryptographic Module, from Google, Inc., holds FIPS 140-2 certificate #3384 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 dependency on certificate #3382. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode with Titan Chip validated to FIPS 140-2 under Cert. #3382 operating in FIPS mode

Certificate

Certificate number3384
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeHardware
EmbodimentMulti-Chip Embedded
VendorGoogle, Inc. · website
Hardware versionsDelta [Configuration 0]; [Configuration 1]; [Configuration 2] with components ARM Cortex-M7 CPU, RR16FFGL_111UHD32768X39M16B8W0R1E1L1P0D0L16, RR16FFGL_111HS16384X8M16B8W1R1E1L0P0D0A0U20 and RR16FFGL_111HS32768X8M16B8W1R1E1L0P0D0A0U20
Firmware versionsDelta-gqfips-1.2

Module description

Quoted from the NIST CMVP entry for this certificate.

The Delta Cryptographic Module is a Network Interface Card (NIC) housed on a host device, which is designed to support Ethernet and IP networking. The Delta module contains cryptographic hardware and firmware support, which allows data packets to be encrypted and decrypted using AES-GCM-128 at "line rate", while supporting a very large number of simultaneous Security Associations.

Security level exceptions

  • Mitigation of Other Attacks: N/A

Approved algorithms (8)

AlgorithmCAVP certificates
AES5656, 5659
CKGvendor affirmed
DRBG2285
ECDSA1529
KTS
RSA3045
SHA-358
SHS4536, 4537

Allowed algorithms

NDRNG

Tested configurations

  • N/A

Validation history

DateTypeLab
2019-03-27InitialAcumen 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-03-27

Source documents