808bits

BorderGuard 5000 and 6000 Series

FIPS 140-2 certificate #700 · Blue Ridge Networks · data as of 2026-09-03

BorderGuard 5000 and 6000 Series, from Blue Ridge Networks, holds FIPS 140-2 certificate #700 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. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode

Certificate

Certificate number700
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-chip standalone
VendorBlue Ridge Networks · website
Hardware versionsBorderGuard 5100, 5200, 5400, 5500, 5600, 6100, 6200, 6400, 6500 and 6600
Firmware versionsDPF1 V7.3

Module description

Quoted from the NIST CMVP entry for this certificate.

The BorderGuard hardware models 5100, 5200, 5400, 5500, 5600, 6100, 6200, 6400, 6500, and 6600 version DPF 7.3 firmware are standalone hardware security appliances (routers) used to secure Internet traffic. The module is a multi-chip-standalone device.

Approved algorithms (4)

AlgorithmCAVP certificates
AES116, 173
HMAC21, 22
SHS49, 258
Triple-DES57, 275

Other algorithms

DES (Certs. #119 and #271); DES MAC (Certs. #119 and #271, vendor affirmed); IDEA; HMAC-MD5; MD5; RSA (non-compliant); Diffie-Hellman (key agreement; key establishment methodology provides between 112 bits of encryption strength for Models 5100, 5200, 5400, 6100, 6200, and 6400; and between 112 and 150 bits of encryption strength for Models 5500, 5600, 6500, and 6600; non-compliant less than 112-bits of encryption strength)

Validation history

DateTypeLab
2006-08-22InitialCOACT INC CAFE LAB

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: 2006-08-22

Source documents