Samsung Kernel Cryptographic Module
Samsung Kernel Cryptographic Module, from Samsung Electronics Co., Ltd., holds FIPS 140-2 certificate #1915 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.
Caveat: When operated in FIPS mode
Certificate
| Certificate number | 1915 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Software |
| Embodiment | Multi-chip standalone |
| Vendor | Samsung Electronics Co., Ltd. · website |
| Software versions | SKC1.4.1, SKC 1.4.1.1 and SKC.1.4.1.2 |
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
- EMI/EMC: Level 3
- Design Assurance: Level 3
Approved algorithms (5)
| Algorithm | CAVP certificates |
|---|---|
| AES | 2056, 2097, 2141, 2144, 2256, 2392 |
| HMAC | 1251, 1272, 1308, 1311, 1383, 1483 |
| RNG | 1075, 1079, 1096, 1099, 1126, 1184 |
| SHS | 1799, 1821, 1863, 1866, 1943, 2054 |
| Triple-DES | 1325, 1334, 1361, 1362, 1411, 1491 |
Other algorithms
DES; AES-CTS (non-compliant); Triple-DES (CTR; non-compliant); Twofish; AEAD; MD5; ansi_cprng; ARC4; GHASH (GCM hash)
Tested configurations
- Android Ice Cream Sandwich 4.0 running on Galaxy S3
- Android Jelly Bean 4.1 running on Note II
- Android Jelly Bean 4.2 running on Galaxy S4 (single-user mode)
Validation history
| Date | Type | Lab |
|---|---|---|
| 2013-03-20 | Initial | atsec information security corporation |
| 2013-05-23 | Update | atsec information security corporation |
| 2013-06-21 | Update | atsec 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: 2013-03-20, 2013-05-23, 2013-06-21