808bits

McAfee Database Security Sensor Cryptographic Module

FIPS 140-2 certificate #2088 · McAfee, Inc. · data as of 2026-08-28
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 and when installed, initialized and configured as specified in the Security Policy Section 4

Certificate

Certificate number2088
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-chip standalone
VendorMcAfee, Inc. · website
Software versions1.0

Module description

The McAfee Database Security Sensor Cryptographic Module Version 1.0, is a software shared library that provides cryptographic services required by the McAfee Database Security Sensor.

Security level exceptions

  • Physical Security: N/A
  • Mitigation of Other Attacks: N/A

Approved algorithms

AlgorithmCAVP certificate
AES2571
DSA786
HMAC1587
RNG1223
RSA1318
SHS2166
Triple-DES1557

Other algorithms

Diffie-Hellman; RSA (key wrapping; key establishment methodology provides between 112 and 256 bits of encryption strength; non-compliant less than 112 bits of encryption strength)

Tested configurations

  • AIX 5.3 on a IBM 9115-305
  • CentOS 5.5 with VMWare ESXi 5.0 running on a Dell PowerEdge R510
  • HP-UX 11.23 running on a HP RX2600 Server
  • Red Hat Enterprise Linux 5.9 with VMWare ESXi 5.0 running on a Dell PowerEdge R510
  • Solaris 9 running on a Sun UltraSPARC C-III (single-user mode)
  • SUSE 11 patch 2 with VMWare ESXi 5.0 running on a Dell PowerEdge R510
  • Windows Server 2008 64-bit with VMWare ESXi 5.0 running on a HP Proliant DL380 GS
  • Windows Server 2008 R2 64-bit with VMWare ESXi 4.0 running on a HP Proliant DL185 GS

Validation history

DateTypeLab
2014-02-25InitialCGI Information Systems & Management Consultants 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: 2014-02-25

Source documents