Cisco Adaptive Security Appliance (ASA) Virtual
Cisco Adaptive Security Appliance (ASA) Virtual, from Cisco Systems, Inc., holds FIPS 140-2 certificate #2653 at overall level 1. 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.
Certificate
| Certificate number | 2653 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Software |
| Embodiment | Multi-Chip Stand Alone |
| Vendor | Cisco Systems, Inc. · website |
| Software versions | 9.4.3 |
Module description
Quoted from the NIST CMVP entry for this certificate.
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 (8)
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
| Date | Type | Lab |
|---|---|---|
| 2016-06-06 | Initial | Gossamer Security Solutions |
| 2016-08-15 | Update | Gossamer 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