808bits

CypherNET™ 3000 Series Multi-Protocol Encryptor

FIPS 140-2 certificate #1268 · Senetas Security Pty Ltd. · data as of 2026-09-03

CypherNET™ 3000 Series Multi-Protocol Encryptor, from Senetas Security Pty Ltd., holds FIPS 140-2 certificate #1268 at overall level 3. 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

Certificate

Certificate number1268
StandardFIPS 140-2
Statushistorical
Overall level3
Module typeHardware
EmbodimentMulti-chip standalone
VendorSenetas Security Pty Ltd. · website
Hardware versionsA5213B, A5214B, A5203B and A5204B
Firmware versions1.9

Module description

Quoted from the NIST CMVP entry for this certificate.

The CypherNET™ 3000 Series product is a high-speed, standards based, multi-protocol encryptor specifically designed to secure voice, data and video information transmitted over Synchronous Optical/Synchronous Digital Hierarchy (SONET/SDH) and Ethernet Networks at data rates up to 10 Gigabits per sec. Data privacy is provided by FIPS approved AES and Triple-DES algorithms.

Approved algorithms (7)

AlgorithmCAVP certificates
AES710, 717, 725, 964
DSA273
HMAC391
RNG422
RSA340
SHS743
Triple-DES647, 702

Other algorithms

RSA (key wrapping; key establishment methodology provides 112 bits of encryption strength; non-compliant less than 112 bits of encryption strength); Diffie-Hellman (key agreement; key establishment methodology provides 112 bits of encryption strength; non-compliant less than 112 bits of encryption strength)

Validation history

DateTypeLab
2010-03-29InitialDOMUS

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: 2010-03-29

Source documents