808bits

RSA BSAFE® Crypto Module

FIPS 140-2 certificate #3409 · RSA Security LLC · data as of 2026-10-09

RSA BSAFE® Crypto Module, from RSA Security LLC, holds FIPS 140-2 certificate #3409 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 in FIPS mode

Certificate

Certificate number3409
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorRSA Security LLC · website
Software versions1.0.1

Module description

Quoted from the NIST CMVP entry for this certificate.

RSA BSAFE® Crypto Module 1.0.1 is designed to help protect sensitive data as it is stored using strong encryption techniques to provide a persistent level of protection. The software supports a wide range of industry standard encryption algorithms offering developers the flexibility to choose the appropriate option to meet their requirements.

Security level exceptions

  • Physical Security: N/A
  • Design Assurance: Level 2

Approved algorithms (10)

AlgorithmCAVP certificates
AES5941
CKGvendor affirmed
CVL2172, 2173
DRBG2494
HMAC3916
KTSvendor affirmed
PBKDFvendor affirmed
RSA3119
SHS4694
Triple-DES2895

Allowed algorithms

NDRNG

Tested configurations

  • Windows 10 Enterprise x64 running on a Dell Latitude 5590 with an Intel Core i7-8650U with PAA (VS2017)
  • Windows 10 Enterprise x64 running on a Dell Latitude 5590 with an Intel Core i7-8650U without PAA (VS2017)
  • Windows 10 Enterprise x64 running on a Dell Optiplex 5060 with an Intel Core i7-8700 with PAA (VS2015)
  • Windows 10 Enterprise x64 running on a Dell Optiplex 5060 with an Intel Core i7-8700 without PAA (VS2015)
  • Windows 10 Enterprise x86 running on a Dell Optiplex 7040 with an Intel Core i5-6500T with PAA (VS2015)
  • Windows 10 Enterprise x86 running on a Dell Optiplex 7040 with an Intel Core i5-6500T with PAA (VS2017)
  • Windows 10 Enterprise x86 running on a Dell Optiplex 7040 with an Intel Core i5-6500T without PAA (VS2015)
  • Windows 10 Enterprise x86 running on a Dell Optiplex 7040 with an Intel Core i5-6500T without PAA (VS2017)
  • Windows 7 Enterprise SP1 x64 running on a Dell Optiplex 7040 with an Intel Core i5-6500T with PAA (VS2015)
  • Windows 7 Enterprise SP1 x64 running on a Dell Optiplex 7040 with an Intel Core i5-6500T with PAA (VS2017)
  • Windows 7 Enterprise SP1 x64 running on a Dell Optiplex 7040 with an Intel Core i5-6500T without PAA (VS2015)
  • Windows 7 Enterprise SP1 x64 running on a Dell Optiplex 7040 with an Intel Core i5-6500T without PAA (VS2017)
  • Windows 7 Enterprise SP1 x86 running on a Dell Optiplex 7040 with an Intel Core i5-6500T with PAA (VS2015)
  • Windows 7 Enterprise SP1 x86 running on a Dell Optiplex 7040 with an Intel Core i5-6500T with PAA (VS2017)
  • Windows 7 Enterprise SP1 x86 running on a Dell Optiplex 7040 with an Intel Core i5-6500T without PAA (VS2015)
  • Windows 7 Enterprise SP1 x86 running on a Dell Optiplex 7040 with an Intel Core i5-6500T without PAA (VS2017)
  • Windows Server 2016 running on a Dell Latitude 5590 with an Intel Core i7-8650U with PAA (VS2015)
  • Windows Server 2016 running on a Dell Latitude 5590 with an Intel Core i7-8650U without PAA (VS2015)
  • Windows Server 2016 running on a Dell Optiplex 5060 with an Intel Core i7-8700 with PAA (VS2017) (single-user mode)
  • Windows Server 2016 running on a Dell Optiplex 5060 with an Intel Core i7-8700 without PAA (VS2017)

Validation history

DateTypeLab
2019-03-20InitialLeidos Accredited Testing & Evaluation (AT&E) Lab
2020-02-14UpdateLeidos 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: 2019-03-20, 2020-02-14

Source documents