808bits

Blue Coat® Systems SSL Visibility Appliance

FIPS 140-2 certificate #2194 · Blue Coat® Systems, Inc. · data as of 2026-09-15

Blue Coat® Systems SSL Visibility Appliance, from Blue Coat® Systems, Inc., holds FIPS 140-2 certificate #2194 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 the tamper evident seals installed as indicated in the Security Policy

Certificate

Certificate number2194
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-chip standalone
VendorBlue Coat® Systems, Inc. · website
Hardware versionsModel: SV2800; 090-03063 and 080-03562 with FIPS Label Kit: FIPS-LABELS-SV
Firmware versions3.5.2 build 961

Module description

Quoted from the NIST CMVP entry for this certificate.

The SSL Visibility Appliance is designed to detect SSL traffic and then under policy control to "inspect" the traffic. Inspection involves decrypting and re-encrypting the traffic to gain access to the clear text then passing this data to one or more associated security appliance(s) that need to see decrypted traffic.

Security level exceptions

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

Approved algorithms (8)

AlgorithmCAVP certificates
AES2642
CVL123
HMAC1634
PBKDFvendor affirmed
RNG1246
RSA1238, 1352
SHS2215
Triple-DES1585

Other algorithms

RSA (key wrapping; key establishment methodology provides between 112 and 256 bits of encryption strength; non-compliant less than 112 bits of encryption strength); Diffie-Hellman (key agreement; key establishment methodology provides between 112 and 256 bits of encryption strength; non-compliant less than 112 bits of encryption strength); EC Diffie-Hellman (key agreement; key establishment methodology provides between 112 and 256 bits of encryption strength; non-compliant less then 112 bits of encryption strength); TRNG; NDRNG; MD5; RC4; HMAC-MD5; Camelia; DES

Validation history

DateTypeLab
2014-06-27InitialCGI 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: 2014-06-27

Source documents