808bits

Cisco Firepower Threat Defense Virtual (FTDv) Cryptographic Module

FIPS 140-2 certificate #3343 · Cisco Systems, Inc. · 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. When installed, initialized and configured as specified in Section 3 of the Security Policy

Certificate

Certificate number3343
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorCisco Systems, Inc. · website
Software versions6.2

Module description

Cisco Firepower Threat Defense (FTD) solution offers the combination of the industry's most deployed stateful firewall with a comprehensive range of next-generation network security services, intrusion prevention system (IPS), content security and secure unified communications. All running in a virtual environment.

Security level exceptions

  • Roles, Services, and Authentication: Level 3
  • Physical Security: N/A
  • Design Assurance: Level 2
  • Mitigation of Other Attacks: N/A

Approved algorithms

AlgorithmCAVP certificate
AES5008
CKGvendor affirmed
CVL1561
DRBG1828
ECDSA1277
HMAC3329
RSA2703
SHS4074
Triple-DES2584

Allowed algorithms

Diffie-Hellman (CVL Cert. #1561, key agreement; key establishment methodology provides between 112 and 150 bits of encryption strength); EC Diffie-Hellman (CVL Cert. #1561, key agreement; key establishment methodology provides between 128 and 256 bits of encryption strength); NDRNG; RSA (key wrapping; key establishment methodology provides 112 bits of encryption strength)

Tested configurations

  • FXOS version 2 on VMware ESXi 5.5 running on Cisco C220 M4 with Intel Xeon E5
  • FXOS version 2 on VMware ESXi 6.0 running on Cisco C220 M4 with Intel Xeon E5 (single-user mode)

Validation history

DateTypeLab
2018-12-17InitialGossamer Security Solutions

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: 2018-12-17

Source documents