808bits

Cisco Telepresence C20 Codec

FIPS 140-2 certificate #1824 · Cisco 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

Certificate

Certificate number1824
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeHardware
EmbodimentMulti-chip standalone
VendorCisco Systems, Inc. · website
Hardware versionsC20 v1
Firmware versionsTC5.0.2

Module description

The Cisco TelePresence portfolio creates an immersive, face-to-face experience over the network, empowering you to collaborate with others like never before. Through a powerful combination of technologies and design that allows you and remote participants to feel as if you are all in the same room, the Cisco TelePresence portfolio has the potential to provide great productivity benefits and transform your business. Many organizations are already using it to control costs, make decisions faster, improve customer intimacy, scale scarce resources, and speed products to market.

Security level exceptions

  • Roles, Services, and Authentication: Level 3
  • Design Assurance: Level 2

Approved algorithms

AlgorithmCAVP certificate
AES1928
DRBG168
DSA612
ECDSA276
HMAC1162
RSA994
SHS1693
Triple-DES1255

Other algorithms

AES (Cert. #1928, key wrapping; key establishment methodology provides 128 bits of encryption strength); Blowfish; Camellia; DES; Diffie-Hellman (key agreement; key establishment methodology provides 80 bits of encryption strength; non-compliant); HMAC-MD5; MD5; RC2; RC4; RSA (key wrapping; key establishment methodology provides between 112 and 150 bits of encryption strength; non-compliant less than 112 bits of encryption strength)

Validation history

DateTypeLab
2012-11-14InitialSAIC-VA
2012-11-21UpdateSAIC-VA
2012-12-03Update

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-11-14, 2012-11-21, 2012-12-03

Source documents