808bits

X-Wall MX+

FIPS 140-2 certificate #3675 · Enova Technology Corporation · data as of 2026-10-21

X-Wall MX+, from Enova Technology Corporation, holds FIPS 140-2 certificate #3675 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. 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. This validation entry is a non-security-relevant modification to Cert. #3013

Certificate

Certificate number3675
StandardFIPS 140-2
Statushistorical
Overall level3
Module typeHardware
EmbodimentSingle Chip
VendorEnova Technology Corporation · website
Hardware versionsxF
Firmware versionsmr.20.06.02.2203.CIF

Module description

Quoted from the NIST CMVP entry for this certificate.

The X-Wall MX+ chip is real-time SATA-to-SATA single chip crypto module. Both FIPS certified authentication method and in-line 6Gbps AES ECB/CBC/XTS 256-bit encryption capability are provided. The modules can be populated directly onto either the mainboard or SATA drive interface. The cryptographic operation is OS independent and doesn’t require host CPU and memory interventions. The Module supports a standard SATA interface and is compliant with the Trusted Computing Group (TCG) SSC specification Opal 2.0.

Security level exceptions

  • Mitigation of Other Attacks: N/A

Approved algorithms (7)

AlgorithmCAVP certificates
AES4013, 4025
CVL836, 884, 885
DRBG1201
HMAC2627
KBKDF100
RSA2090
SHS3311

Allowed algorithms

RSA (key wrapping; key establishment methodology provides 112 bits of encryption strength); NDRNG

Tested configurations

  • N/A

Validation history

DateTypeLab
2020-07-02InitialLightship 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
  • Validation dates on record: 2020-07-02

Source documents