808bits

ProxySG 600-10 [1], 600-20 [2] and 600-35 [3]

FIPS 140-2 certificate #1736 · Blue Coat® Systems, Inc. · data as of 2026-08-28
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 with the tamper evident seals and opacity baffles installed as indicated in the Security Policy

Certificate

Certificate number1736
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-chip standalone
VendorBlue Coat® Systems, Inc. · website
Hardware versions090-02911 [1], 090-02912 [1], 090-02913 [2], 090-02914 [2], 090-02915 [3] and 090-02916 [3] with FIPS kit 085-02762
Firmware versions6.1 or 6.1.5.5

Module description

The foundation of Blue Coat's application delivery infrastructure, Blue Coat ProxySG appliances establish points of control that accelerate and secure business applications for users across the distributed organization. Blue Coat appliances serve as an Internet proxy and wide area network (WAN) optimizer. The purpose of the appliances is to provide a layer of security between an Internal and External Network (typically an office network and the Internet) and to provide acceleration and compression of transmitted data. ProxySG 600 is one of several appliance lines offered by Blue Coat

Approved algorithms

AlgorithmCAVP certificate
AES105, 1875
DRBG153
HMAC1120
RSA956
SHS1648
Triple-DES217, 1218

Other algorithms

RSA (key wrapping; key establishment methodology provides 112 bits of encryption strength; non-compliant less than 112 bits of encryption strength)

Validation history

DateTypeLab
2012-06-21InitialCGI Information Systems & Management Consultants Inc
2012-07-24Update
2012-08-07Update
2013-01-04UpdateCGI Information Systems & Management Consultants Inc

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: 2012-06-21, 2012-07-24, 2012-08-07, 2013-01-04

Source documents