808bits

Cryptographic Module for Intel® Platforms' Security Engine Chipset

FIPS 140-2 certificate #4355 · Intel Corporation · data as of 2026-10-21

Cryptographic Module for Intel® Platforms' Security Engine Chipset, from Intel Corporation, holds FIPS 140-2 certificate #4355 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. Does not meet SP 800-56Arev3 requirements. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode and installed, initialized and configured as specified in Sections 2.3 and 9.1 for of the Security Policy. When entropy is externally loaded, no assurance of the minimum strength of generated keys

Certificate

Certificate number4355
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeFirmware-Hybrid
EmbodimentMulti-Chip Stand Alone
VendorIntel Corporation · website
Hardware versions2.0
Firmware versions3.1

Module description

Quoted from the NIST CMVP entry for this certificate.

The Cryptographic Module for Intel® CSE is a hardware-firmware hybrid module present on Intel® PCH platforms. The module performs crypto functions for CSE applications, including but are not limited to: PTT (Platform Trust Technology), AMT (Active Management Technology), and DAL (Dynamic Application Loader).

Approved algorithms (11)

AlgorithmCAVP certificates
AESC1463
CKGvendor affirmed
CVLC1463
DRBGC1463
ECDSAC1463
HMACC1463
KASC1463
KBKDFC1463
KTSvendor affirmed
RSAC1463
SHSC1463

Allowed algorithms

NDRNG

Tested configurations

  • Embedded customized proprietary OS running firmware version 14.0.30.1115 on Intel Comet Point PCH with Lakemont processor 3.6

Validation history

DateTypeLab
2022-11-07InitialUL Verification Services, 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: 2022-11-07

Source documents