DragonWave® Secure Cryptographic Module
Certificate
| Certificate number | 2170 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Firmware-Hybrid |
| Embodiment | Multi-chip standalone |
| Vendor | DragonWave Inc. · website |
| Hardware versions | Horizon® Quantum (PN: 74-000320) and Horizon® Compact+ (PN: 74-000320) with Tamper Evident Seal (PN: 65-000185-01-01) |
| Firmware versions | 1.2.5 (Compact+) and 1.3 (Quantum) |
Module description
The DragonWave® Secure Cryptographic Module is a hybrid cryptographic module consisting of firmware and hardware. The hardware portion of the module provides AES for bulk data encryption between two Horizon Compact+ or Horizon Quantum peer devices in a radio link, while the firmware provides cryptographic state management as well as secure peer-to-peer management communications over a protected TLS tunnel.
Security level exceptions
- Tested: Horizon Quantum (PN 60-000471-03) and Horizon Compact+ (PN CP-HP-18-B1-S-X-010-N-00-R1) with QNX Neutrino Real-Time Operating System Version 6.4.1
Approved algorithms
| Algorithm | CAVP certificate |
|---|---|
| AES | 2706, 2707, 2708, 2709 |
| CVL | 164, 165 |
| HMAC | 1687, 1688 |
| RNG | 1256, 1257 |
| RSA | 1404, 1405 |
| SHS | 2273, 2274 |
| Triple-DES | 1625, 1626 |
Other algorithms
Diffie-Hellman (key agreement; key establishment methodology provides 112 bits of encryption strength); RSA (key wrapping; key establishment methodology provides between 112 and 150 bits of encryption strength; non-compliant less then 112 bits of encryption strength); DSA (non compliant); MD5; SHA-[224, 384 and 512] (non-compliant); HMAC-SHA-[224, 256, 384 and 512] (non-compliant); RSA (non-compliant); AES (non-compliant); Triple-DES (non-compliant)
Validation history
| Date | Type | Lab |
|---|---|---|
| 2014-06-12 | Initial | CGI 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-06-12