808bits

MFP Cryptographic Module(A)

FIPS 140-2 certificate #4455 · Kyocera Document Solutions Inc. · data as of 2026-10-09

MFP Cryptographic Module(A), from Kyocera Document Solutions Inc., holds FIPS 140-2 certificate #4455 at overall level 2. 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-08-24.
Caveat: When operated in FIPS mode and installed, initialized and configured as specified in Section 10.3 of the Security Policy

Certificate

Certificate number4455
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentSingle Chip
VendorKyocera Document Solutions Inc. · website
Hardware versionsVaultIP-2.1.10 and EIP38-3.2
Firmware versions2.2.18

Module description

Quoted from the NIST CMVP entry for this certificate.

MFP Cryptographic Module(A) is a cryptographic security chip for encrypting data written to a storage device and other security function of Kyocera multifunction printer. Secure key generation and fast AES encryption/decryption are offered through SATA interface. SecureBoot verifies the integrity of the firmware when the product starts up.

Security level exceptions

  • Mitigation of Other Attacks: N/A

Approved algorithms (10)

AlgorithmCAVP certificates
AESC1892, C1933
CKGvendor affirmed
DRBGC1892
ECDSAC1892
HMACC1892
KBKDFC1892
KDAvendor affirmed
KTS
RSAC1892
SHSC1892

Allowed algorithms

NDRNG

Tested configurations

  • Kyocera SCH114C

Validation history

DateTypeLab
2023-03-22Initialatsec 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 at the time of the earliest snapshot
  • 2026-08-24: observed moving from active to historical
  • Validation dates on record: 2023-03-22

Source documents