808bits

Continuum Network Security Module

FIPS 140-2 certificate #1355 · Schneider Electric · data as of 2026-10-09

Continuum Network Security Module, from Schneider Electric, holds FIPS 140-2 certificate #1355 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. RNG SP800-131A Revision 1 Transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated only on the specific platforms specified

Certificate

Certificate number1355
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeFirmware
EmbodimentMulti-chip standalone
VendorSchneider Electric · website
Firmware versionsACX Series v1.100021 and NetController II v2.100021

Module description

Quoted from the NIST CMVP entry for this certificate.

The Continuum Network Security module is part of the NetController II or ACX Series of controllers to provide the most secure method of communications amongst peer controllers and Cyberstation Workstations on the Ethernet/IP network by providing FIPS 140-2 certified encryption algorithms that are used by the IPSec/IKE protocol built into these controllers to automate building operations for HVAC, Lighting, and Physical Access Control.

Security level exceptions

  • Tested: [ACX Series Rev 2a (with ACX Series v1.100021 firmware) and NetController II Rev B (with NetController II v 2.100021 firmware)] with Multi-Threaded Real Time OS (ThreadX version G3.0e.3.0b)

Approved algorithms (4)

AlgorithmCAVP certificates
HMAC528
RNG537
SHS924
Triple-DES752

Other algorithms

Diffie-Hellman (key agreement; key establishment methodology provides 80 bits of encryption strength; non-compliant); RNG (non-compliant)

Validation history

DateTypeLab
2010-07-12InitialICSA

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-07-12

Source documents