808bits

Enclave Microsegmentation Platform

FIPS 140-2 certificate #3381 · SideChannel Inc. · data as of 2026-10-09

Enclave Microsegmentation Platform, from SideChannel Inc., holds FIPS 140-2 certificate #3381 at overall level 1. 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. No assurance of the minimum strength of generated keys. This validation entry is a non-security relevant modification to Cert. #3273.

Certificate

Certificate number3381
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorSideChannel Inc. · website
Software versions1.0

Module description

Quoted from the NIST CMVP entry for this certificate.

SideChannel's Enclave Microsegmentation Platform builds overlay networks, firewalls, and Zero Trust network permission models to create spaces where access is only granted to specified machines and users. These spaces, or micro-segments, are called Enclaves. Enclave was designed to make creating these accesses in a simple way without sacrificing security.

Security level exceptions

  • Physical Security: N/A
  • Mitigation of Other Attacks: N/A

Approved algorithms (9)

AlgorithmCAVP certificates
AES4750
CKGvendor affirmed
DRBG1631
DSA1273
ECDSA1185
HMAC3164
RSA2594
SHS3893
Triple-DES2524

Tested configurations

  • CentOS 7.3 on a Dell Optiplex 755 with an Intel Celeron processor (single-user mode)

Validation history

DateTypeLab
2019-02-26InitialAEGISOLVE, Inc.
2020-06-04UpdateCYGNACOM SOLUTIONS INC
2021-03-16UpdateAEGISOLVE, Inc.
2023-05-11UpdateLeidos Accredited Testing & Evaluation (AT&E) Lab

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: 2019-02-26, 2020-06-04, 2021-03-16, 2023-05-11

Source documents