808bits

IOS Common Cryptographic Module (IC2M)

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

IOS Common Cryptographic Module (IC2M), from Cisco Systems, Inc., holds FIPS 140-2 certificate #4222 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. 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. No assurance of the minimum strength of generated keys

Certificate

Certificate number4222
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeFirmware
EmbodimentMulti-Chip Stand Alone
VendorCisco Systems, Inc. · website
Firmware versionsRel5a

Module description

Quoted from the NIST CMVP entry for this certificate.

The IC2M module provides the FIPS validated cryptographic algorithms for services requiring those algorithms. The module does not implement any protocols directly. Instead, it provides the cryptographic primitives and functions to allow IOS to implement those various protocols.

Security level exceptions

  • Mitigation of Other Attacks: N/A

Approved algorithms (12)

AlgorithmCAVP certificates
AESA1462
CKGvendor affirmed
CVLA1462
DRBGA1462
ECDSAA1462
HMACA1462
KAS-SSCA1462
KBKDFA1462
KTS
RSAA1462
SHSA1462
Triple-DESA1462

Allowed algorithms

RSA (key wrapping; key establishment methodology provides 112 or 128 bits of encryption strength)

Tested configurations

  • IOS-XE 17.3 running on a Cisco ASR1K RP2 with an Intel Xeon L52XX
  • IOS-XE 17.3 running on a Cisco ASR1K RP3 with an Intel Xeon D-15XX
  • IOS-XE 17.3 running on a Cisco ISR 4321 with an Intel Atom C25XX

Validation history

DateTypeLab
2022-05-09InitialAcumen Security

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: 2022-05-09

Source documents