808bits

Cisco Adaptive Security Appliance (ASA) Virtual

FIPS 140-2 certificate #2653 · 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 number2653
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorCisco Systems, Inc. · website
Software versions9.4.3

Module description

The market-leading Cisco ASA Security Appliance Series deliver robust user and application policy enforcement, multi-vector attack protection, and secure connectivity services in cost-effective, easy-to-deploy solutions. The ASA Virtual Adaptive Security Appliances provide comprehensive security, performance, and reliability for network environments of all sizes.

Security level exceptions

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

Approved algorithms

AlgorithmCAVP certificate
AES3911
CVL772
DRBG1126
ECDSA854
HMAC2540
RSA1995
SHS3223
Triple-DES2147

Other algorithms

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

Tested configurations

  • ASA Virtual 9.4 on VMware ESXi 5.5 running on Cisco C220 M3
  • ASA Virtual 9.4 on VMware ESXi 5.5 running on Cisco E180D M2 (single-user mode)

Validation history

DateTypeLab
2016-06-06InitialGossamer Security Solutions
2016-08-15UpdateGossamer 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: 2016-06-06, 2016-08-15

Source documents