808bits

Samsung Kernel Cryptographic Module

FIPS 140-2 certificate #2337 · Samsung Electronics Co., Ltd. · data as of 2026-10-21

Samsung Kernel Cryptographic Module, from Samsung Electronics Co., Ltd., holds FIPS 140-2 certificate #2337 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. RNG SP800-131A Revision 1 Transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode

Certificate

Certificate number2337
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-chip standalone
VendorSamsung Electronics Co., Ltd. · website
Software versionsSKC1.5

Module description

Quoted from the NIST CMVP entry for this certificate.

Provides general purpose cryptographic services to services in the Linux kernel and user-space applications, intended to protect data in transit and at rest.

Security level exceptions

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

Approved algorithms (5)

AlgorithmCAVP certificates
AES3007, 3010
HMAC1900, 1902
RNG1304, 1305
SHS2514, 2518
Triple-DES1766

Other algorithms

DES; Twofish; MD4; MD5; ansi_cprng; krng; ARC4; Pcompress; AES-XCBC (non-compliant); CRC32c; Deflate; LZO; AES-GCM (non-compliant); RFC4106-AES-GCM (non-compliant); RFC4543-AES-GCM (non-compliant); AES-CTR (non-compliant); Triple-DES-CTR (non-compliant); GHASH; GF128MUL

Tested configurations

  • Android KitKat 4.4.4 running on Samsung Galaxy Note 4 (single-user mode)

Validation history

DateTypeLab
2015-03-16Initialatsec 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: 2015-03-16

Source documents