808bits

MultiApp V31 Platform

FIPS 140-2 certificate #2679 · Gemalto SA · data as of 2026-09-12

MultiApp V31 Platform, from Gemalto SA, holds FIPS 140-2 certificate #2679 at overall level 3. 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 in accordance with SP800-131A Revision 1 Transition (AES/TDES key wrapping). Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: The module generates cryptographic keys whose strengths are modified by available entropy. No assurance of the minimum strength of generated keys.

Certificate

Certificate number2679
StandardFIPS 140-2
Statushistorical
Overall level3
Module typeHardware
EmbodimentSingle Chip
VendorGemalto SA · website
Hardware versionsNXP P60D080P VC (MPH132), NXP P60D144P VA (MPH149)
Firmware versionsMultiApp V31 patch 1.4, Demonstration Applet version V1.3

Module description

Quoted from the NIST CMVP entry for this certificate.

The MultiApp ID smart cards are fully compliant with two major industry standards: Sun's Javacard 2.2.1 and Global Platform (GP) Card Specification version 2.1.1. They are therefore Java-GP cards, capable of managing applets in a controlled and secure manner in this multi-applet environment. This platform is delivered with a set of applet already loaded loaded in ROM and that can be installed if proper ordering options have been set.

Approved algorithms (9)

AlgorithmCAVP certificates
AES3543
CVL597
DRBG900
ECDSA721
KBKDF85
RSA1822, 1823
SHS2921
Triple-DES1984
Triple-DES MACvendor affirmed

Other algorithms

EC Diffie-Hellman (key agreement; key establishment methodology provides between 112 and 256 bits of encryption strength); Triple-DES (Cert. #1984, key wrapping; key establishment methodology provides 112 bits of encryption strength); AES (Cert. #3543, key agreement; key establishment methodology provides between 128 and 256 bits of encryption strength)

Tested configurations

  • N/A

Validation history

DateTypeLab
2016-07-15InitialUL 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-07-15

Source documents