808bits

VPN Client Software

FIPS 140-2 certificate #1032 · Nortel Networks · data as of 2026-10-21

VPN Client Software, from Nortel Networks, holds FIPS 140-2 certificate #1032 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 with Microsoft® Enhanced Cryptographic Provider validated to FIPS 140-1 under Cert. #238 operating in FIPS mode

Certificate

Certificate number1032
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-chip standalone
VendorNortel Networks · website
Software versions7_11.101

Module description

Quoted from the NIST CMVP entry for this certificate.

The Contivity VPN Client provides stable, secure network access via Nortel VPN routers and VPN gateways. The client can be preconfigured and customized by IT administrators for quick install and connect, or easily configured by end users via the connection wizard. The VPN client works over all IP infrastructures including all wireless, broadband, and satellite services. The VPN client also supports seamless roaming, enabling a user to roam wirelessly without losing the virtual connection.

Security level exceptions

  • EMI/EMC: Level 3

Approved algorithms (5)

AlgorithmCAVP certificates
AES721
HMAC389
RNG421
SHS740
Triple-DES644

Other algorithms

Diffie-Hellman (key agreement; key establishment methodology provides 80 or 96 bits of encryption strength; non-compliant); DES; 40-bit DES; MD5; ECDH (non-compliant); HMAC-MD5

Tested configurations

  • Windows XP Professional Service Pack 2 (single-user mode)

Validation history

DateTypeLab
2008-10-07InitialSAIC-VA

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-10-07

Source documents