808bits

AirTight Wireless Sensor

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

AirTight Wireless Sensor, from Mojo Networks, Inc., holds FIPS 140-2 certificate #2615 at overall level 2. 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. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode and with tamper evident seals installed as indicated in the Security Policy

Certificate

Certificate number2615
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-Chip Stand Alone
VendorMojo Networks, Inc. · website
Hardware versionsC-75 and C-75-E with Tamper Evident Seal Kit: C-TPL-A
Firmware versions7.2.FIPS.04

Module description

Quoted from the NIST CMVP entry for this certificate.

The module performs wireless intrusion detection and prevention. It monitors radio channels to ensure conformance of wireless activity to security policy. It mitigates various types of wireless security violations such as rogue wireless networks, unauthorized wireless connections, network mis-configurations and denial of service attacks.

Security level exceptions

  • Mitigation of Other Attacks: N/A

Approved algorithms (8)

AlgorithmCAVP certificates
AES3766
CVL710
DRBG1036
HMAC2465
KBKDF77
KTS
RSA1937
SHS3135

Other algorithms

Diffie-Hellman (key agreement; key establishment methodology provides 112 bits of encryption strength); MD5; NDRNG

Tested configurations

  • N/A

Validation history

DateTypeLab
2016-04-12InitialCYGNACOM SOLUTIONS INC
2016-04-14UpdateCYGNACOM SOLUTIONS INC
2016-04-15UpdateCYGNACOM SOLUTIONS INC
2016-04-19UpdateCYGNACOM SOLUTIONS 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
  • Validation dates on record: 2016-04-12, 2016-04-14, 2016-04-15, 2016-04-19

Source documents