Cisco 1841 Integrated Services Router with AIM-VPN/BPII-Plus and Cisco 2801 Integrated Services Router with AIM- VPN/EPII-Plus
Cisco 1841 Integrated Services Router with AIM-VPN/BPII-Plus and Cisco 2801 Integrated Services Router with AIM- VPN/EPII-Plus, from Cisco Systems, Inc., holds FIPS 140-2 certificate #620 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.
Certificate
| Certificate number | 620 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 2 |
| Module type | Hardware |
| Embodiment | Multi-chip standalone |
| Vendor | Cisco Systems, Inc. · website |
| Hardware versions | 1841 and 2801; AIM-VPN/BPII-Plus Version: 1.0, Board Version: C1; AIM-VPN/EPII-Plus Version: 1.0, Board Version: D0 |
| Firmware versions | 12.3(11)T03 |
Module description
Quoted from the NIST CMVP entry for this certificate.
The Cisco 1841 and 2801 routers feature the ability to deliver multiple high-quality simultaneous services at wire speeds up to multiple T1/E1/xDSL connections. These routers offer embedded encryption acceleration on the motherboard. For additional performance, the Cisco 1841 and 2801 routers feature the ability to optionally add encryption acceleration advanced integration modules (AIMs).
Approved algorithms (5)
| Algorithm | CAVP certificates |
|---|---|
| AES | 219, 181, 100 |
| HMAC | 29, 27, 38 |
| RNG | 31 |
| SHS | 300, 267, 401 |
| Triple-DES | 311, 283, 213 |
Other algorithms
DES (Certs. #292, #275 and #235); Diffie-Hellman (key agreement; key establishment methodology provides 80 or 96 bits of encryption strength; non-compliant); MD5; HMAC-MD5; RSA (non-compliant); RC4
Validation history
| Date | Type | Lab |
|---|---|---|
| 2006-01-06 | Initial | SAIC-VA |
| 2010-05-28 | Update | |
| 2012-02-23 | Update |
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: 2006-01-06, 2010-05-28, 2012-02-23