808bits

Blue Coat Reverse Proxy S400-20 [1], S400-30 [2], S400-40 [3], S500-10 [4], S500-20 [5] and S500-30 [6]

FIPS 140-2 certificate #3048 · Symantec, A Division of Broadcom · data as of 2026-08-28
Historical. SP 800-56Arev3 transition. 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 the opacity baffles installed as indicated in the Security Policy

Certificate

Certificate number3048
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-Chip Stand Alone
VendorSymantec, A Division of Broadcom · website
Hardware versions090-03623 [1], 090-03626 [1], 090-03624 [2], 090-03627 [2], 090-03625 [3], 090-03628 [3], 090-03615 [4], 090-03617 [4], 090-03616 [5], 090-03618 [5], 090-03656 [6] and 090-03657 [6] with FIPS Kit: HW-KIT-FIPS-400 [1,2,3] and HW-KIT-FIPS-500 [4,5,6]
Firmware versions6.7.2 and 6.7.5

Module description

The Blue Coat Reverse Proxy appliances provide a termination point where deep inspection for malware and mission-critical policy is applied to inbound traffic. The Reverse Proxy gives organizations the ability to govern traffic and payloads on a wide variety of parameters, including location, devices, clients, software, protocols, and more. It can be used with either public-facing or internally facing web servers.

Security level exceptions

  • Design Assurance: Level 3
  • Mitigation of Other Attacks: N/A

Approved algorithms

AlgorithmCAVP certificate
AES4552
CKGvendor affirmed
CVL1231, 1233, 1237
DRBG1502
HMAC3005, 3006
KTS
KTS
RSA2478, 2479
SHS3729, 3730
Triple-DES2423

Allowed algorithms

Diffie-Hellman (CVL Cert. #1231 with CVL Certs. #1233 and #1237, key agreement; key establishment methodology provides 112 bits of encryption strength); EC Diffie-Hellman (CVL Cert. #1231 with CVL Certs. #1233 and #1237, key agreement; key establishment methodology provides 192 bits of encryption strength); MD5; NDRNG; RSA (key wrapping; key establishment methodology provides between 112 and 150 bits of encryption strength)

Tested configurations

  • N/A

Validation history

DateTypeLab
2017-10-17InitialAcumen Security
2017-11-16UpdateAcumen Security
2022-01-05UpdateAcumen Security

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: 2017-10-17, 2017-11-16, 2022-01-05

Source documents