808bits

MS1201 Security Sub-system

FIPS 140-2 certificate #4045 · eWBM · data as of 2026-10-09

MS1201 Security Sub-system, from eWBM, holds FIPS 140-2 certificate #4045 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. SP 800-56Arev3 transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode

Certificate

Certificate number4045
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentSingle Chip
VendoreWBM · website
Hardware versions2.2.0
Firmware versions2.5.3

Module description

Quoted from the NIST CMVP entry for this certificate.

MS1201 Security Sub-system is a Silicon IP Security Module with a secure asset store protecting all valuable assets on your device. It is a stand-alone Root of Trust that offers key management and crypto functions needed for platform and application security. MS1201 Security Sub-system offers all security services to manage your device securely through its lifecycle. These include Secure Debug, Secure Provisioning, HUK and Identity protection and secure authentication services.

Security level exceptions

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

Approved algorithms (11)

AlgorithmCAVP certificates
AESC1900
CKGvendor affirmed
CVLC1900
DRBGC1900
ECDSAC1900
HMACC1900
KBKDFC1900
KDAvendor affirmed
KTS
RSAC1900
SHSC1900

Allowed algorithms

EC Diffie-Hellman (CVL Cert. #C1900 with SP 800-56C, vendor affirmed, key agreement; key establishment methodology provides between 112 and 256 bits of encryption strength); NDRNG

Tested configurations

  • MS1201 Security Sub-system

Validation history

DateTypeLab
2021-10-18Initialatsec information security corporation

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: 2021-10-18

Source documents