808bits

Trellix Core Cryptographic Module (kernel)

FIPS 140-2 certificate #4220 · Trellix · data as of 2026-10-09

Trellix Core Cryptographic Module (kernel), from Trellix, holds FIPS 140-2 certificate #4220 at overall level 1. 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: None

Certificate

Certificate number4220
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorTrellix · website
Software versions2.2.0.17.0

Module description

Quoted from the NIST CMVP entry for this certificate.

The Trellix Core Cryptographic Module provides cryptographic functionality for Trellix's Endpoint Encryption product range.

Security level exceptions

  • Physical Security: N/A
  • Design Assurance: Level 3
  • Mitigation of Other Attacks: N/A

Approved algorithms (3)

AlgorithmCAVP certificates
AESA1555
HMACA1555
SHSA1555

Tested configurations

  • Windows 10 64-bit running on Microsoft Surface 3 with an Intel i5-520M with PAA
  • Windows 10 64-bit running on Microsoft Surface 3 with an Intel i5-520M without PAA
  • Windows 7 32-bit running on Dell Latitude E7270 with Intel i5-6300U with PAA
  • Windows 7 32-bit running on Dell Latitude E7270 with Intel i5-6300U without PAA (single-user mode)

Validation history

DateTypeLab
2022-05-09InitialAcumen Security
2024-03-13UpdateAcumen Security

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-05-09, 2024-03-13

Source documents