808bits

Secure Mobile

FIPS 140-2 certificate #2404 · Digital Defence Ltd · data as of 2026-09-08

Secure Mobile, from Digital Defence Ltd, holds FIPS 140-2 certificate #2404 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 with the Microsoft Windows CE, Windows Mobile, and Windows Embedded Handheld Enhanced Cryptographic Provider (RSAENH) validated to FIPS 140-2 under Cert. #560 operating in FIPS mode

Certificate

Certificate number2404
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-chip standalone
VendorDigital Defence Ltd · website
Software versions11.1.0.0

Module description

Quoted from the NIST CMVP entry for this certificate.

Secure Mobile Cryptographic Module provides core cryptographic functionality in a Windows Embedded Handheld environment. It supports XTS-AES-128 cipher mode for storage encryption, KDF acc. to NIST SP 800-108 to derive the storage encryption key, and HMAC-SHA-256 for integrity protection of its binaries and settings. For generation of XTS tweak values a validated RNG (Cert. #286) contained in "Windows CE and Windows Mobile Enhanced Cryptographic Provider (RSAENH)" , which is a FIPS 140-2 certified cryptographic software module contained in the platform.

Security level exceptions

  • Physical Security: N/A

Approved algorithms (4)

AlgorithmCAVP certificates
AES2851, 2852
HMAC1792, 1793
KBKDF26
SHS2394, 2395

Tested configurations

  • Windows Mobile 6.5 running on Motorola MC65 (Single-user mode)

Validation history

DateTypeLab
2015-07-06InitialTUVIT Evaluation Body for IT 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: 2015-07-06

Source documents