808bits

RSA BSAFE® Crypto-C Micro Edition for Samsung MFP SW Platform (VxWorks)

FIPS 140-2 certificate #1861 · RSA, The Security Division of EMC · data as of 2026-10-21

RSA BSAFE® Crypto-C Micro Edition for Samsung MFP SW Platform (VxWorks), from RSA, The Security Division of EMC, holds FIPS 140-2 certificate #1861 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. RNG SP800-131A Revision 1 Transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode

Certificate

Certificate number1861
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-chip standalone
VendorRSA, The Security Division of EMC · website
Software versions3.0.0.1

Module description

Quoted from the NIST CMVP entry for this certificate.

A software cryptographic library within the Vxworks real-time operating system specifically for embedded systems based on the ARM9 CPU architecture.

Approved algorithms (9)

AlgorithmCAVP certificates
AES1826
DRBG143
DSA573
ECDSA252
HMAC1080
RNG962
RSA918
SHS1605
Triple-DES1179

Other algorithms

DES; MD2; MD5; HMAC-MD5; DES40; RC2; RC4; RC5; ECAES (non-compliant); ECIES; PBKDF1-SHA-1 (non-compliant); PBKDF2-HMAC (SHA-1, SHA-224, SHA-256, SHA-384 and SHA-512) (non-compliant); RSA (key wrapping; key establishment methodology provides between 112 and 150 bits of encryption strength; non-compliant less than 112 bits of encryption strength); RSA OAEP; Entropy RNG; OTP RNG; Diffie-Hellman; EC Diffie-Hellman

Tested configurations

  • VxWorks (single user mode)

Validation history

DateTypeLab
2012-12-10InitialBAE SYSTEMS APPLIED INTELLIGENCE
2016-02-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: 2012-12-10, 2016-02-12

Source documents