808bits

Kanguru Defender Elite/Elite+

FIPS 140-2 certificate #1270 · Kanguru Solutions · data as of 2026-09-13

Kanguru Defender Elite/Elite+, from Kanguru Solutions, holds FIPS 140-2 certificate #1270 at overall level 2. 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: Files distributed with the module mounted within the CD Drive, Public Drive, and/or Private Drive are excluded from the validation.) (Note: Refer to the cryptographic module's Security Policy Appendix 1 for the details on the letter x and y designations

Certificate

Certificate number1270
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-chip standalone
VendorKanguru Solutions · website
Hardware versionsKDFE-1Ga-y, KDFE-xG, KDFE-xG-y, KDFE-xG-L, KDFE-xG-y-L, KDFEP-xG and KDFEP-xG-y
Firmware versions1.0, 2.01.10 or 2.01.15

Module description

Quoted from the NIST CMVP entry for this certificate.

The Kanguru Defender Elite/Elite+ is a FIPS 140-2 Level 2 multi-chip standalone cryptographic module that utilizes AES hardware encryption to secure data at rest. The module is a ruggedized, opaque, tamper-evident USB token/storage device.

Security level exceptions

  • Cryptographic Module Specification: Level 3
  • Roles, Services, and Authentication: Level 3
  • EMI/EMC: Level 3
  • Design Assurance: Level 3

Approved algorithms (4)

AlgorithmCAVP certificates
AES1066
RNG603
RSA506
SHS1009

Other algorithms

NDRNG; RSA-512 (non-compliant)

Validation history

DateTypeLab
2010-03-29InitialAEGISOLVE, Inc.
2010-08-09Update
2010-08-12Update
2010-08-20UpdateAEGISOLVE, Inc.
2010-12-21UpdateAEGISOLVE, 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: 2010-03-29, 2010-08-09, 2010-08-12, 2010-08-20, 2010-12-21

Source documents