808bits

RAD X-1040 AES-256

FIPS 140-2 certificate #4196 · Vcinity, Inc. · data as of 2026-10-09

RAD X-1040 AES-256, from Vcinity, Inc., holds FIPS 140-2 certificate #4196 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

Certificate

Certificate number4196
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeHardware
EmbodimentMulti-Chip Stand Alone
VendorVcinity, Inc. · website
Hardware versionsRAD X-1040 (90-0206-101) Rev L
Firmware versionsRAD X Release 4.0.1

Module description

Quoted from the NIST CMVP entry for this certificate.

RAD X-1040 belongs to Vcinity’s Radical X product family and transforms the WAN into a Global LAN by encapsulating and extending RDMA over WAN across any distance. AES-256 encryption augments RAD X’s DataPrizm feature, which obfuscates and aggregates data in-flight across multiple network paths. The combined solution enables RAD X-1040 to secure the in-flight data to reduce the ever-growing risk of compromised or lost information. AES-256 encryption can be used independent of the DataPrizm function.

Security level exceptions

  • Roles, Services, and Authentication: Level 2
  • Design Assurance: Level 2
  • Mitigation of Other Attacks: N/A

Approved algorithms (3)

AlgorithmCAVP certificates
AESA934
HMACA911
SHSA911

Tested configurations

  • N/A

Validation history

DateTypeLab
2022-04-14InitialAEGISOLVE, Inc.

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-04-14

Source documents