808bits

SSL Visibility Appliance

FIPS 140-2 certificate #2361 · Blue Coat® Systems, Inc. · data as of 2026-10-21

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

Certificate

Certificate number2361
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-chip standalone
VendorBlue Coat® Systems, Inc. · website
Hardware versionsSV3800; 090-03064 and 080-03563 with FIPS Kit: FIPS-LABELS-SV
Firmware versions3.8.2F build 227 and 3.8.4FC

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 (9)

AlgorithmCAVP certificates
AES3195, 3496
CVL429, 562
DRBG669, 866
ECDSA584, 711
HMAC2013, 2230
PBKDFvendor affirmed
RSA1625, 1238, 1794
SHS2642, 2885
Triple-DES1821, 1968

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 than 112 bits of encryption strength); TRNG; NDRNG; MD5; RC4; HMAC-MD5; Camelia; DES; ChaCha20-Poly1305

Validation history

DateTypeLab
2015-04-23InitialCGI Information Systems & Management Consultants Inc
2015-09-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: 2015-04-23, 2015-09-04

Source documents