Kanguru Defender 3000
Kanguru Defender 3000, from Kanguru Solutions, holds FIPS 140-2 certificate #2401 at overall level 3. 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.
Caveat: None
Certificate
| Certificate number | 2401 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 3 |
| Module type | Hardware |
| Embodiment | Multi-chip standalone |
| Vendor | Kanguru Solutions · website |
| Hardware versions | P/Ns KDF3000-8G [1, 2, 3], KDF3000-16G [1, 2, 3], KDF3000-32G [1, 2, 3], KDF3000-64G [1, 2, 3], KDF3000-128G [1, 2, 3], KDF3000-256G [2, 3], KDF3000-512G [3], KDF3000-1T [3], Version 1.0 |
| Firmware versions | 2.10.10 [1], 2.11.10 [2], and 2.12.10[3] |
Module description
Quoted from the NIST CMVP entry for this certificate.
The Kanguru Defender 3000 is a 256-bit AES hardware encrypted USB flash drive used primarily to secure data at rest. The device can also be used as a secure platform for remote access and virtualized applications run directly from the drive. The Kanguru Defender line of secure USB solutions is remotely manageable through the Kanguru Remote Management Console (KRMC).
Security level exceptions
- Mitigation of Other Attacks: N/A
Approved algorithms (7)
| Algorithm | CAVP certificates |
|---|---|
| AES | 2962 |
| CKG | vendor affirmed |
| DRBG | 560 |
| HMAC | 1878 |
| PBKDF | vendor affirmed |
| RSA | 1557 |
| SHS | 2491 |
Other algorithms
NDRNG; RSA (key wrapping; key establishment methodology provides 112 bits of encryption strength)
Validation history
| Date | Type | Lab |
|---|---|---|
| 2015-06-30 | Initial | AEGISOLVE, Inc. |
| 2016-06-21 | Update | AEGISOLVE, Inc. |
| 2020-04-06 | Update | AEGISOLVE, Inc. |
| 2020-10-16 | Update | AEGISOLVE, Inc. |
| 2024-01-03 | Update | AEGISOLVE, Inc. |
| 2025-01-08 | Update | AEGISOLVE, 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: 2015-06-30, 2016-06-21, 2020-04-06, 2020-10-16, 2024-01-03, 2025-01-08