808bits

AN/GRC-262

FIPS 140-2 certificate #4296 · Ultra Electronics TCS Inc. · data as of 2026-10-09

AN/GRC-262, from Ultra Electronics TCS Inc., holds FIPS 140-2 certificate #4296 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: When installed, initialized and configured as specified in Sections [7.1] and [12.1.1] of the Security Policy. The tamper evident seals installed as indicated in the Security Policy

Certificate

Certificate number4296
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-Chip Stand Alone
VendorUltra Electronics TCS Inc. · website
Hardware versionsAN/GRC-262(V)1 with FIPS kit 612-990309-088
Firmware versions1.13.10.1356

Module description

Quoted from the NIST CMVP entry for this certificate.

The AN/GRC-262 radio is a multiband, point-to-point (PTP), point-to-multipoint (PMP) and Mesh radio system capable of providing at-the-halt communications across multiple echelons and on-the-move access capability. The system offers up to 1Gbps throughput and operational flexibility in a compact form factor.

Security level exceptions

  • Mitigation of Other Attacks: N/A

Approved algorithms (8)

AlgorithmCAVP certificates
AESA1493, A1494
CVLA1493
DRBGA1493
ENT
HMACA1493, A1494
KAS-SSCA1493
RSAA1493
SHSA1493, A1494, A1495

Tested configurations

  • N/A

Validation history

DateTypeLab
2022-09-11InitialLightship Security, Inc.
2023-03-31UpdateLightship Security, 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-09-11, 2023-03-31

Source documents