808bits

Versa Networks Branch

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

Versa Networks Branch, from Versa Networks, Inc., holds FIPS 140-2 certificate #4379 at overall level 1. 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: When operated in FIPS mode. No assurance of the minimum strength of generated keys

Certificate

Certificate number4379
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorVersa Networks, Inc. · website
Software versions1.0

Module description

Quoted from the NIST CMVP entry for this certificate.

The Versa Networks Branch is a software component that comprises of a comprehensive stack of network and security functions. The Versa Networks Branch software module can be deployed on a bare metal system or on a hypervisor-based Virtual Machine.

Security level exceptions

  • Physical Security: N/A
  • Mitigation of Other Attacks: N/A

Approved algorithms (10)

AlgorithmCAVP certificates
AESA1636, A1644, C1923, C1971
CVLC1923, C1971
DRBGC1923
ECDSAC1923
HMACC1923, C1971
KAS
KAS-SSCA1636, A1644
KTS
RSAC1923, C1971
SHSC1923, C1971

Tested configurations

  • Ubuntu 18.04 running on a Versa CSG750 with an Intel Denverton C3558
  • Ubuntu-18.04 on KVM on Ubuntu-18.04 running on Supermicro X10DDW-i with an Intel Xeon CPU E5-2660v4 @2.00GHz (single-user mode)

Validation history

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

Source documents