808bits

Cisco Secure ACS FIPS Module

FIPS 140-2 certificate #948 · Cisco Systems, Inc. · data as of 2026-10-21

Cisco Secure ACS FIPS Module, from Cisco Systems, Inc., holds FIPS 140-2 certificate #948 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.

Historical. RNG SP800-131A Revision 1 Transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode

Certificate

Certificate number948
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-chip standalone
VendorCisco Systems, Inc. · website
Software versions1.1

Module description

Quoted from the NIST CMVP entry for this certificate.

Cisco Secure ACS FIPS Module is a software library that supports WPA2 security and is contained within a defined cryptographic boundary. It provides FIPS 140-2 validated support for EAP-TLS, EAP-FAST, PEAP and AES key wrap for 802.11i PMK transfer.

Approved algorithms (5)

AlgorithmCAVP certificates
AES566
HMAC303
RNG331
RSA263
SHS632

Other algorithms

AES (AES Cert. #566, vendor affirmed; key wrapping; key establishment methodology provides 128 bits of encryption strength); DES; Diffie-Hellman (key agreement; key establishment methodology provides 112 bits of encryption strength); HMAC-MD5; MD2; MD4; MD5; RC2; RC4; RSA (key wrapping; key establishment methodology provides between 112 and 152 bits of encryption strength; non-compliant less than 112 bits of encryption strength)

Tested configurations

  • Windows 2000 Server Service Pack 4
  • Windows 2003 Service Pack 1 (single-user mode)

Validation history

DateTypeLab
2008-05-22InitialSAIC-VA
2011-08-22Update
2012-02-23Update

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: 2008-05-22, 2011-08-22, 2012-02-23

Source documents