808bits

NetLib® Encryptionizer® Platform (NEP)

FIPS 140-2 certificate #3477 · NetLib Security, Inc. · data as of 2026-08-28
Historical. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: None

Certificate

Certificate number3477
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorNetLib Security, Inc. · website
Software versions2018.1.1.0

Module description

The NetLib® Encryptionizer® Platform Library (NEP) version 2018.1.1.0 provides encryption of data stored in server-based and desktop-based databases and files, including MS SQL Server databases and backups. It can be deployed without programming and without adding any administrative overhead. The purpose of whole database encryption is to make a database or file unusable if it is stolen, copied, downloaded, lost, or otherwise improperly accessed. It supports both 32-bit and 64-bit applications.

Security level exceptions

  • Physical Security: N/A
  • Design Assurance: Level 2
  • Mitigation of Other Attacks: N/A

Approved algorithms

AlgorithmCAVP certificate
AES5529
HMAC3682
SHS4437

Tested configurations

  • Windows 10 (32-bit) running on HP Pavilion Notebook PC with Intel Core i7-6500U with PAA
  • Windows 10 (32-bit) running on HP Pavilion Notebook PC with Intel Core i7-6500U without PAA
  • Windows 10 (64-bit) running on HP Pavilion Notebook PC with Intel Core i7-6500U with PAA
  • Windows 10 (64-bit) running on HP Pavilion Notebook PC with Intel Core i7-6500U without PAA
  • Windows Server 2016 (64-bit) running on Dell PowerEdge R210 II Server with Intel Xeon ES-2640 with PAA
  • Windows Server 2016 (64-bit) running on Dell PowerEdge R210 II Server with Intel Xeon ES-2640 without PAA (single-user mode)

Validation history

DateTypeLab
2019-06-25InitialCOACT INC CAFE 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-06-25

Source documents