SonicWALL TZ 170
SonicWALL TZ 170, from SonicWall, Inc., holds FIPS 140-2 certificate #458 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.
Caveat: When operated in FIPS mode
Certificate
| Certificate number | 458 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 2 |
| Module type | Hardware |
| Embodiment | Multi-chip standalone |
| Vendor | SonicWall, Inc. · website |
| Hardware versions | P/N 101-5000072-00 rev A |
| Firmware versions | SonicOS Enhanced Versions 2.0, v2.5 and v3.1 |
Module description
Quoted from the NIST CMVP entry for this certificate.
The SonicWALL TZ 170 is an internet security appliance with a WAN interface, a flexible Optional interface, and a LAN interface incorporating a 5-port Fast-Ethernet switch. The SonicWALL TZ 170 provides stateful packet inspection firewall services, accelerated IPSec VPN, bandwidth management, and can be upgraded to offer ISP failover and traffic loadbalancing. The SonicWALL TZ 170 also serves as a platform for extensible security services such as Content Filtering Services (CFS), Network Anti - Virus, and E-mail filtering.
Security level exceptions
- EMI/EMC: Level 3
Approved algorithms (6)
| Algorithm | CAVP certificates |
|---|---|
| AES | 121, 140 |
| DSA | 98 |
| HMAC-SHA-1 | vendor affirmed |
| RSA | vendor affirmed |
| SHA-1 | 208 |
| Triple-DES | 231, 248 |
Other algorithms
DES (Certs. #245 and #251); RC4; MD5; Diffie-Hellman (key agreement)
Validation history
| Date | Type | Lab |
|---|---|---|
| 2004-09-08 | Initial | UL Verification Services, Inc. |
| 2005-02-24 | Update | |
| 2006-05-17 | Update | |
| 2007-04-25 | Update | |
| 2015-04-21 | Update | UL Verification Services, Inc. |
| 2017-06-08 | Update | UL Verification Services, 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: 2004-09-08, 2005-02-24, 2006-05-17, 2007-04-25, 2015-04-21, 2017-06-08