808bits

cVu 16100 Network Packet Broker

FIPS 140-2 certificate #4382 · cPacket Networks, Inc. · data as of 2026-10-09

cVu 16100 Network Packet Broker, from cPacket Networks, Inc., holds FIPS 140-2 certificate #4382 at overall level 2. The validation is historical: agencies may keep the module in existing systems but not buy it new. Below are its algorithm certificates, its validation history, and the list moves this tracker has observed, which NIST does not date.

Historical. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement. Observed moving to historical on 2026-09-22. It was one of the last FIPS 140-2 certificates, all moved at the 140-2 sunset on 2026-09-21.
Caveat: None

Certificate

Certificate number4382
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-Chip Stand Alone
VendorcPacket Networks, Inc. · website
Hardware versionscVu 16100 NG TAA
Firmware versions21.3.0

Module description

Quoted from the NIST CMVP entry for this certificate.

The cPacket cVu product family is the industry's leading network packet broker (NPB) with millisecond accuracy at 100G wire speed. The cVu 16100+ integrates real-time performance monitoring with network packet brokering to enable organizations to cost effectively and quickly find network infrastructure issues and reliably feed security and other network tools without dropping packets.

Security level exceptions

  • Roles, Services, and Authentication: Level 3
  • Mitigation of Other Attacks: N/A

Approved algorithms (14)

AlgorithmCAVP certificates
AESA2251
CKGvendor affirmed
CVLA2252, A2253, A2254
DRBGA2251
DSAA2251
ECDSAA2251
ENT
HMACA2251
KAS
KAS-SSCA2251
KTS
RSAA2251
SHA-3A2250
SHSA2251

Tested configurations

  • N/A

Validation history

DateTypeLab
2022-11-28InitialLeidos Accredited Testing & Evaluation (AT&E) Lab

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 at the time of the earliest snapshot
  • 2026-09-22: observed moving from active to historical
  • Validation dates on record: 2022-11-28

Source documents