RFS7000 RF Switch
RFS7000 RF Switch, from Motorola, Inc., holds FIPS 140-2 certificate #1089 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.
Certificate
| Certificate number | 1089 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 2 |
| Module type | Hardware |
| Embodiment | Multi-chip standalone |
| Vendor | Motorola, Inc. · website |
| Hardware versions | RFS7000 |
| Firmware versions | RFS7000-1.0.0.0-020GR and RFS7000-1.0.0.0-022GR |
Module description
Quoted from the NIST CMVP entry for this certificate.
Designed for large scale, high bandwidth deployments, the RFS7000 Wireless Switch from Motorola provides robust, highly scalable support for seamless enterprise mobility. Motorola's Wi-NG architecture, optimized for enterprise mobility and multimedia applications, simplifies network deployment and management, provides superior performance, security and scalability, and supports emerging RF technologies. Built on this platform, the RFS7000 enables campus wide roaming across subnets, and offers powerful failover capabilities, exceptional quality of service (QoS) and increased voice capacity.
Approved algorithms (7)
| Algorithm | CAVP certificates |
|---|---|
| AES | 724, 726, 727, 773 |
| DSA | 274 |
| HMAC | 390, 392, 393 |
| RNG | 423, 424 |
| RSA | 341 |
| SHS | 742, 744, 745 |
| Triple-DES | 646, 648, 649 |
Other algorithms
MD5; RSA (key wrapping; key establishment methodology provides 80 bits of encryption strength; non-compliant); Diffie-Hellman (key agreement; key establishment methodology provides 112 bits of encryption strength; non-compliant less than 112 bits of encryption strength)
Validation history
| Date | Type | Lab |
|---|---|---|
| 2009-02-09 | Initial | Aspect |
| 2009-06-01 | Update |
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: 2009-02-09, 2009-06-01