808bits

Ixia Cryptographic Module for Network Visibility

FIPS 140-2 certificate #3311 · Ixia, a Keysight Business · data as of 2026-08-28
Historical. SP 800-56Arev3 transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode. The module generates cryptographic keys whose strengths are modified by available entropy. No assurance of the minimum strength of generated keys. This validation entry is a non-security relevant modification to Cert. #3152.

Certificate

Certificate number3311
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorIxia, a Keysight Business · website
Software versions1.0.1

Module description

The Ixia, a Keysight business, Cryptographic Module for Network Visibility is integrated into Ixia's Vision portfolio of network packet brokers (NPBs) to provide FIPS 140-2 validated cryptography for the protection of sensitive information.

Security level exceptions

  • Physical Security: N/A

Approved algorithms

AlgorithmCAVP certificate
AES5940
CKGvendor affirmed
CVL2168, 2169, 2170, 2171, C421
DRBG2493
DSA1506
ECDSA1590
HMAC3915
KAS210
KASvendor affirmed
KBKDF247
KTS
KTSvendor affirmed
KTS
PBKDFvendor affirmed
RSA3118
SHA-363
SHS4693
Triple-DES2894

Allowed algorithms

Diffie-Hellman (key agreement; key establishment methodology provides 112 bits of encryption strength); MD5; RSA (key wrapping; key establishment methodology provides 112 or 128 bits of encryption strength)

Tested configurations

  • Ixia, a Keysight Business, Network Visibility - Linux 4.12.0 and OpenJDK v8 (1.8.0) running on IXIA Vision ONE using an Intel Core i7-3555LE (single-user mode)

Validation history

DateTypeLab
2018-10-23InitialAcumen Security
2019-03-07UpdateAcumen Security
2020-05-29UpdateAcumen 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: 2018-10-23, 2019-03-07, 2020-05-29

Source documents