Module Name
Ruckus Wireless, Inc. R710, R610, R720, T610 and T710 Wireless Access Points
Validation Dates
10/27/2020
Caveat
When operated in FIPS mode and with the tamper evident seals installed as indicated in the Security Policy. This validation entry is a non-security-relevant modification to Cert. #3393
Security Level Exceptions
- Mitigation of Other Attacks: N/A
Embodiment
Multi-Chip Stand Alone
Description
The Ruckus Wireless, Inc. Wi-Fi, switching and software portfolio builds on more than a decade's worth of patented technologies to offer better connections that enable awesome customer experiences-at a fraction of the cost of alternatives. Our indoor and outdoor wireless access points fit just about any budget, performance requirement or deployment scenario.
FIPS Algorithms
| AES |
Certs. #5096, #5309, #5312 and #5381 |
| CKG |
vendor affirmed |
| CVL |
Certs. #1646 and #1777 |
| DRBG |
Cert. #1902 |
| ECDSA |
Cert. #1321 |
| HMAC |
Certs. #3398 and #3564 |
| KBKDF |
Cert. #199 |
| KTS |
AES Cert. #5096 and HMAC Cert. #3398; key establishment methodology provides between 128 and 256 bits of encryption strength |
| KTS |
AES Cert. #5381 and HMAC Cert. #3564; key establishment methodology provides between 128 and 256 bits of encryption strength |
| KTS |
Triple-DES Cert. #2627 and HMAC Cert. #3398; key establishment methodology provides 112 bits of encryption strength |
| RSA |
Certs. #2758 and #2878 |
| SHS |
Certs. #4144 and #4317 |
| Triple-DES |
Cert. #2627 |
Allowed Algorithms
Diffie-Hellman (CVL Cert. #1646, key agreement; key establishment methodology provides 112 bits of encryption strength); EC Diffie-Hellman (CVL Cert. #1646, key agreement; key establishment methodology provides between 112 and 256 bits of encryption strength); NDRNG; RSA (key wrapping; key establishment methodology provides 112 bits of encryption strength)
Hardware Versions
R710, R610, R720, T610 and T710
Firmware Versions
3.6.0.3
) or https:// don't prove our archive is authentic, only that you securely accessed it. Note that we are working to fix that :)
