808bits

Samsung Kernel Cryptographic Module

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

Samsung Kernel Cryptographic Module, from Samsung Electronics Co., Ltd., holds FIPS 140-2 certificate #2674 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. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode. The module generates random strings whose strengths are modified by available entropy

Certificate

Certificate number2674
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorSamsung Electronics Co., Ltd. · website
Software versionsSKC1.7

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 (4)

AlgorithmCAVP certificates
AES3836, 3837
DRBG1082, 1083
HMAC2487, 2488, 2516
SHS3160, 3161, 3193

Other algorithms

DES; Twofish; MD5; krng; ARC4; Pcompress; CRC32c; Deflate; LZO; GHASH; GF128MUL; Triple-DES (non-compliant)

Tested configurations

  • Android Marshmallow 6.0.1 running on Samsung Galaxy S7 with PAA
  • Android Marshmallow 6.0.1 running on Samsung Galaxy S7 without PAA (single-user mode)

Validation history

DateTypeLab
2016-07-11Initialatsec information security corporation
2016-09-20Update

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: 2016-07-11, 2016-09-20

Source documents