SCS Linux Kernel Cryptographic Services module
SCS Linux Kernel Cryptographic Services module, from Northrop Grumman M5 Network Security, holds FIPS 140-2 certificate #2130 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 with module OpenSSL FIPS Object Module V2 validated to FIPS 140-2 under Cert. #1747 operating in FIPS mode. No assurance of the minimum strength of generated keys
Certificate
| Certificate number | 2130 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Software |
| Embodiment | Multi-chip standalone |
| Vendor | Northrop Grumman M5 Network Security · website |
| Software versions | kernel-PAE-2.6.32.14-127.scs.fips.fc12.i686 |
Module description
Quoted from the NIST CMVP entry for this certificate.
A FIPS module that provides a C-language application program interface (API) for use by other processes that require cryptographic functionality within the SCS 100 and 200 hardware platforms.
Security level exceptions
- Physical Security: N/A
- Mitigation of Other Attacks: N/A
Approved algorithms (5)
Other algorithms
DES; Triple-DES CTR (non-compliant); AES GCM (non-compliant)
Tested configurations
- Fedora 12 (Linux 2.6.32 kernel) running on M5 Network Security model SCS-100
- Fedora 12 (Linux 2.6.32 kernel) running on M5 Network Security model SCS-200 (single-user mode)
Validation history
| Date | Type | Lab |
|---|---|---|
| 2014-05-06 | Initial | BAE SYSTEMS APPLIED INTELLIGENCE |
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: 2014-05-06