Ruckus Networks Virtual SmartZone (vSZ)
Ruckus Networks Virtual SmartZone (vSZ), from CommScope Technologies LLC, holds FIPS 140-2 certificate #4568 at overall level 1. The validation is historical: agencies may keep the module in existing systems but not buy it new. Below are its algorithm certificates, its validation history, and the list moves this tracker has observed, which NIST does not date.
Caveat: When operated in FIPS mode. When initialized and configured as specified in Section 8 of the Security Policy.
Certificate
| Certificate number | 4568 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Software |
| Embodiment | Multi-Chip Stand Alone |
| Vendor | CommScope Technologies LLC · website |
| Software versions | 5.2.1.3 |
Module description
Quoted from the NIST CMVP entry for this certificate.
The Ruckus Virtual SmartZone (vSZ) is a Network Function Virtualization (NFV) based and cloud-ready controller for service providers and enterprises ready to elevate their wired and wireless infrastructure deployment to the next level of flexibility, resiliency, and scale.
Security level exceptions
- Roles, Services, and Authentication: Level 2
- Physical Security: N/A
- Design Assurance: Level 2
- Mitigation of Other Attacks: N/A
Approved algorithms (10)
| Algorithm | CAVP certificates |
|---|---|
| AES | C2078, C2083 |
| CVL | C2083 |
| DRBG | C2083 |
| ECDSA | C2083 |
| HMAC | C2078, C2083 |
| KAS | |
| KAS-SSC | A2457 |
| KTS | |
| RSA | C2083 |
| SHS | C2078, C2083 |
Allowed algorithms
NDRNG
Tested configurations
- CentOS 7.5 on VMware ESXi 6.5.0 running on Dell PowerEdge R620 with Intel Xeon E5-2650 v2 without AES-NI (single-user mode)
- CentOS 7.5 on VMware ESXi 6.5.0 running on Dell PowerEdge R620 with Intel XeonE5-2650 v2 with AES-NI
Validation history
| Date | Type | Lab |
|---|---|---|
| 2023-08-30 | Initial | Gossamer Security Solutions |
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 at the time of the earliest snapshot
- 2026-09-22: observed moving from active to historical
- Validation dates on record: 2023-08-30