808bits

RSA BSAFE® Crypto-C Micro Edition

FIPS 140-2 certificate #3743 · RSA Security, LLC · data as of 2026-08-28
Historical. SP 800-56Arev3 transition - replaced by certificate #4470. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode. When entropy is externally loaded, no assurance of the minimum strength of generated keys

Certificate

Certificate number3743
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorRSA Security, LLC · website
Software versions4.1.4

Module description

The Crypto-C Micro Edition (ME) Module is RSA's cryptographic library designed for securing mobile devices like wireless phones and personal digital assistants. It contains assembly-level optimizations on key wireless processors. Its functionality includes a wide range of data encryption and signing algorithms, including Triple-DES, the Advanced Encryption Standard (AES) algorithm, the RSA Public Key Cryptosystem, the DSA government signature algorithm, MD5 and SHA1 message digest routines, and more.

Security level exceptions

  • Cryptographic Module Specification: Level 3
  • Physical Security: N/A
  • Design Assurance: Level 3

Approved algorithms

AlgorithmCAVP certificate
AESC584
CKGvendor affirmed
CVLC584
DRBGC584
DSAC584
ECDSAC584
HMACC584
KASC584
KASvendor affirmed
KBKDFC584
KDAvendor affirmed
KTS
KTSvendor affirmed
PBKDFvendor affirmed
RSAC584
SHA-3C584
SHSC584
Triple-DESC584

Allowed algorithms

Diffie-Hellman (key agreement; key establishment methodology provides between 112 and 200 bits of encryption strength); EC Diffie-Hellman (key agreement; key establishment methodology provides between 112 and 256 bits of encryption strength); MD5; NDRNG; RSA (key wrapping; key establishment methodology provides between 112 and 256 bits of encryption strength)

Tested configurations

  • AIX 6.1 on PowerVM Virtual I/O Server 2.2.6.21 running on an IBM Power 8284 - 22A (32-bit)
  • AIX 6.1 on PowerVM Virtual I/O Server 2.2.6.21 running on an IBM Power 8284 - 22A (64-bit)
  • AIX 7.2 on PowerVM Virtual I/O Server 2.2.6.21 running on an IBM Power 8231 - E2B (32-bit)
  • AIX 7.2 on PowerVM Virtual I/O Server 2.2.6.21 running on an IBM Power 8231 - E2B (64-bit)
  • Android 6.0 running on Google Nexus 5X with Qualcomm Snapdragon 808
  • Android 8.0 running on Google Pixel with Qualcomm Snapdragon 821
  • FreeBSD 11.2 on VMWare ESXi 6.0.0 running on a Cisco C220 M3 with Intel Xeon E5-2650 with PAA
  • FreeBSD 11.2 on VMWare ESXi 6.0.0 running on a Cisco C220 M3 with Intel Xeon E5-2650 without PAA
  • HP-UX 11.31 running on an HP 9000 rp3410 with HP PA-8800 (32-bit)
  • HP-UX 11.31 running on an HP 9000 rp3410 with HP PA-8800 (64-bit)
  • HP-UX 11.31 running on an HP Integrity RX2620 with Intel Itanium 2 (32-bit)
  • HP-UX 11.31 running on an HP Integrity RX2620 with Intel Itanium 2 (64-bit)
  • iOS 10 running on an iPhone 5C with Apple A6
  • iOS 11 running on an iPad Pro 9.7 with Apple A9X
  • macOS 10.12 on VMWare ESXi 6.0.0 running on a Mac Pro with Intel Xeon E5-1650 v2 with PAA
  • macOS 10.12 on VMWare ESXi 6.0.0 running on a Mac Pro with Intel Xeon E5-1650 v2 without PAA
  • macOS 10.13 on VMWare ESXi 6.0.0 running on a Mac Pro with Intel Xeon E5-1650 v2 with PAA
  • macOS 10.13 on VMWare ESXi 6.0.0 running on a Mac Pro with Intel Xeon E5-1650 v2 without PAA
  • Red Hat Enterprise Linux 5.8 on z/VM 6.0 running on an IBM zEnterprise 196 with IBM s390x (31-bit)
  • Red Hat Enterprise Linux 5.8 on z/VM 6.0 running on an IBM zEnterprise 196 with IBM s390x (64-bit)
  • Solaris 10 Update 11 on VMWare ESXi 6.0.0 running on a Cisco C220 M3 with Intel Xeon E5-2650 without PAA
  • Solaris 11.4 running on a Solaris 11 LDOM on Oracle SPARC T4-2 (Sun C 5.13 32-bit v8+)
  • Solaris 11.4 running on a Solaris 11 LDOM on Oracle SPARC T4-2 (Sun C 5.13 64-bit v9)
  • Solaris 11.4 running on a Solaris 11 LDOM on Oracle SPARC T4-2 (Sun C 5.8 32-bit v8)
  • Solaris 11.4 running on a VMWare ESXi 6.0.0 running on a Cisco C220 M3 with Intel Xeon E5-2650 without PAA
  • SUSE Linux Enterprise Server 11 SP4 on HP Integrity RX2600 with Intel Itanium 2 (64-bit)
  • SUSE Linux Enterprise Server 11 SP4 on PowerVM Virtual I/O Server 2.2.6.21 running on an IBM Power 8231 - E2B (32-bit)
  • SUSE Linux Enterprise Server 11 SP4 on PowerVM Virtual I/O Server 2.2.6.21 running on an IBM Power 8231 - E2B (64-bit)
  • SUSE Linux Enterprise Server 12 SP3 on PowerVM Virtual I/O Server 2.2.6.21 running on an IBM Power 8284 - 22A (64-bit)
  • SUSE Linux Enterprise Server 12 SP3 on VMWare ESXi 6.0.0 running on a Dell R630 with Intel Xeon E5-2620 with PAA (32-bit)
  • SUSE Linux Enterprise Server 12 SP3 on VMWare ESXi 6.0.0 running on a Dell R630 with Intel Xeon E5-2620 with PAA (64-bit)
  • SUSE Linux Enterprise Server 12 SP3 on VMWare ESXi 6.0.0 running on a Dell R630 with Intel Xeon E5-2620 without PAA (32-bit)
  • SUSE Linux Enterprise Server 12 SP3 on VMWare ESXi 6.0.0 running on a Dell R630 with Intel Xeon E5-2620 without PAA (64-bit)
  • SUSE Linux Enterprise Server 12 SP3 running on SoftIron Overdrive 1000 with ARM CORTEX A57 (AMD OPTERON A1100)
  • SUSE Linux Enterprise Server 15 on VMWare ESXi 6.0.0 running on a Dell R630 with Intel Xeon E5-2620 with PAA
  • SUSE Linux Enterprise Server 15 on VMWare ESXi 6.0.0 running on a Dell R630 with Intel Xeon E5-2620 without PAA
  • Ubuntu 16.04 LTS running on a Beagle Bone Black with ARM Cortex A8
  • Windows 10 Enterprise on VMWare ESXi 6.0.0 running on a Dell R630 with Intel Xeon E5-2620 with PAA (Visual Studio 2013 /MD)
  • Windows 10 Enterprise on VMWare ESXi 6.0.0 running on a Dell R630 with Intel Xeon E5-2620 with PAA (Visual Studio 2013 /MT)
  • Windows 10 Enterprise on VMWare ESXi 6.0.0 running on a Dell R630 with Intel Xeon E5-2620 with PAA (Visual Studio 2017 /MD)
  • Windows 10 Enterprise on VMWare ESXi 6.0.0 running on a Dell R630 with Intel Xeon E5-2620 with PAA (Visual Studio 2017 /MT)
  • Windows 10 Enterprise on VMWare ESXi 6.0.0 running on a Dell R630 with Intel Xeon E5-2620 without PAA (Visual Studio 2013 /MD)
  • Windows 10 Enterprise on VMWare ESXi 6.0.0 running on a Dell R630 with Intel Xeon E5-2620 without PAA (Visual Studio 2013 /MT)
  • Windows 10 Enterprise on VMWare ESXi 6.0.0 running on a Dell R630 with Intel Xeon E5-2620 without PAA (Visual Studio 2017 /MD)
  • Windows 10 Enterprise on VMWare ESXi 6.0.0 running on a Dell R630 with Intel Xeon E5-2620 without PAA (Visual Studio 2017 /MT)
  • Windows 7 Enterprise SP1 (x64) on VMWare ESXi 6.0.0 running on a Cisco C220 M3 with Intel Xeon E5-2650 with PAA (Visual Studio 2005 /MT)
  • Windows 7 Enterprise SP1 (x64) on VMWare ESXi 6.0.0 running on a Cisco C220 M3 with Intel Xeon E5-2650 without PAA (Visual Studio 2005 /MT)
  • Windows 7 Enterprise SP1 on VMWare ESXi 6.0.0 running on a Cisco C220 M3 with Intel Xeon E5-2650 with PAA (Visual Studio 2005 /MD)
  • Windows 7 Enterprise SP1 on VMWare ESXi 6.0.0 running on a Cisco C220 M3 with Intel Xeon E5-2650 with PAA (Visual Studio 2005 /MT)
  • Windows 7 Enterprise SP1 on VMWare ESXi 6.0.0 running on a Cisco C220 M3 with Intel Xeon E5-2650 with PAA (Visual Studio 2010 /MD)
  • Windows 7 Enterprise SP1 on VMWare ESXi 6.0.0 running on a Cisco C220 M3 with Intel Xeon E5-2650 with PAA (Visual Studio 2010 /MT)
  • Windows 7 Enterprise SP1 on VMWare ESXi 6.0.0 running on a Cisco C220 M3 with Intel Xeon E5-2650 without PAA (Visual Studio 2005 /MD)
  • Windows 7 Enterprise SP1 on VMWare ESXi 6.0.0 running on a Cisco C220 M3 with Intel Xeon E5-2650 without PAA (Visual Studio 2005 /MT)
  • Windows 7 Enterprise SP1 on VMWare ESXi 6.0.0 running on a Cisco C220 M3 with Intel Xeon E5-2650 without PAA (Visual Studio 2010 /MD)
  • Windows 7 Enterprise SP1 on VMWare ESXi 6.0.0 running on a Cisco C220 M3 with Intel Xeon E5-2650 without PAA (Visual Studio 2010 /MT)
  • Windows 8.1 Enterprise on VMWare ESXi 6.0.0 running on a Cisco C220 M3 with Intel Xeon E5-2650 with PAA
  • Windows 8.1 Enterprise on VMWare ESXi 6.0.0 running on a Cisco C220 M3 with Intel Xeon E5-2650 without PAA
  • Windows Server 2008 Enterprise R2 SP1 on VMWare ESXi 6.0.0 running on a Cisco C220 M3 with Intel Xeon E5-2650 with PAA (Visual Studio 2005 /MD)
  • Windows Server 2008 Enterprise R2 SP1 on VMWare ESXi 6.0.0 running on a Cisco C220 M3 with Intel Xeon E5-2650 with PAA (Visual Studio 2010 /MT)
  • Windows Server 2008 Enterprise R2 SP1 on VMWare ESXi 6.0.0 running on a Cisco C220 M3 with Intel Xeon E5-2650 without PAA (Visual Studio 2005 /MD)
  • Windows Server 2008 Enterprise R2 SP1 on VMWare ESXi 6.0.0 running on a Cisco C220 M3 with Intel Xeon E5-2650 without PAA (Visual Studio 2010 /MT)
  • Windows Server 2008 Enterprise SP2 on HP Integrity RX2620 with Intel Itanium 2 (64-bit)
  • Windows Server 2012 R2 Standard on VMWare ESXi 6.0.0 running on a Cisco C220 M3 with Intel Xeon E5-2650 with PAA (Visual Studio 2010 /MD)
  • Windows Server 2012 R2 Standard on VMWare ESXi 6.0.0 running on a Cisco C220 M3 with Intel Xeon E5-2650 with PAA (Visual Studio 2013 /MD)
  • Windows Server 2012 R2 Standard on VMWare ESXi 6.0.0 running on a Cisco C220 M3 with Intel Xeon E5-2650 with PAA (Visual Studio 2017 /MT)
  • Windows Server 2012 R2 Standard on VMWare ESXi 6.0.0 running on a Cisco C220 M3 with Intel Xeon E5-2650 without PAA (Visual Studio 2010 /MD)
  • Windows Server 2012 R2 Standard on VMWare ESXi 6.0.0 running on a Cisco C220 M3 with Intel Xeon E5-2650 without PAA (Visual Studio 2013 /MD)
  • Windows Server 2012 R2 Standard on VMWare ESXi 6.0.0 running on a Cisco C220 M3 with Intel Xeon E5-2650 without PAA (Visual Studio 2017 /MT)
  • Windows Server 2016 on VMWare ESXi 6.0.0 running on a Cisco C220 M3 with Intel Xeon E5-2650 with PAA
  • Windows Server 2016 on VMWare ESXi 6.0.0 running on a Cisco C220 M3 with Intel Xeon E5-2650 without PAA (single-user mode)

Validation history

DateTypeLab
2020-11-16InitialLeidos Accredited Testing & Evaluation (AT&E) Lab
2021-04-12UpdateLeidos Accredited Testing & Evaluation (AT&E) Lab

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: 2020-11-16, 2021-04-12

Source documents