808bits

Steelhead 250 and Steelhead 550 Appliances

FIPS 140-2 certificate #1373 · Riverbed Technology, Inc. · data as of 2026-09-15

Steelhead 250 and Steelhead 550 Appliances, from Riverbed Technology, Inc., holds FIPS 140-2 certificate #1373 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.

Historical. RNG SP800-131A Revision 1 Transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode with tamper evident seals and security panels installed as indicated in the Security Policy

Certificate

Certificate number1373
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-chip standalone
VendorRiverbed Technology, Inc. · website
Hardware versions250 and 550
Firmware versions4.1.10

Module description

Quoted from the NIST CMVP entry for this certificate.

The Steelhead family of appliances provides application acceleration and accelerated data transfer over a wide area network (WAN), overcoming bandwidth and geographical limitations to improve productivity and enable global collaboration.

Security level exceptions

  • Design Assurance: Level 3

Approved algorithms (6)

AlgorithmCAVP certificates
AES1044
HMAC586
RNG595
RSA498
SHS994
Triple-DES792

Other algorithms

DSA; MD5; DES; RC2; RC4; IDEA; CAST; Blowfish; Diffie-Hellman (key agreement; key establishment methodology provides 80 bits of encryption strength; non-compliant); RSA (key wrapping; key establishment methodology provides 112 bits of encryption strength; non-compliant less than 112 bits of encryption strength); HMAC-Tiger; EC Diffie-Hellman

Validation history

DateTypeLab
2010-07-21InitialDOMUS

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: 2010-07-21

Source documents