Forcepoint C Cryptographic Module
Forcepoint C Cryptographic Module, from Forcepoint, holds FIPS 140-2 certificate #2875 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 built, installed, protected and initialized as assumed by the Crypto Officer role and as specified in the provided Security Policy and operated in FIPS in mode. Appendix A of the provided Security Policy specifies the actual distribution tar file containing the source code of this module. There shall be no additions, deletions or alterations to the tar file contents as used during module build. The distribution tar file shall be verified as specified in Appendix A of the provided Security Policy. Installation and protection shall be completed as specified in Appendix A of the provided Security Policy. Initialization shall be invoked as per Section 4 of the provided Security Policy. Any deviation from specified verification, protection, installation and initialization procedures will result in a non FIPS 140-2 compliant module. This validation entry is a non-security relevant modification to Cert. #1747
Certificate
| Certificate number | 2875 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Software |
| Embodiment | Multi-Chip Stand Alone |
| Vendor | Forcepoint · website |
| Software versions | 2.0.2, 2.0.5 or 2.0.10 |
Module description
Quoted from the NIST CMVP entry for this certificate.
Forcepoint produces a family of web, e-mail and data security solutions that can be deployed on pre-configured, security hardened hardware or as customer installable software. The Forcepoint C Crypto Module provides support for cryptographic and secure communications services for these solutions.
Security level exceptions
- Roles, Services, and Authentication: Level 2
- Physical Security: N/A
- Design Assurance: Level 3
- Mitigation of Other Attacks: N/A
Approved algorithms (9)
| Algorithm | CAVP certificates |
|---|---|
| AES | 2234, 3264, 4401 |
| CVL | 36, 472, 1110 |
| DRBG | 264, 723, 1419 |
| DSA | 693, 933, 1176 |
| ECDSA | 347, 620, 1058 |
| HMAC | 1363, 2063, 2925 |
| RSA | 1145, 1664, 2381 |
| SHS | 1923, 2702, 3628 |
| Triple-DES | 1398, 1853, 2373 |
Other algorithms
EC Diffie-Hellman; RSA (encrypt/decrypt); PRNG
Tested configurations
- Microsoft Windows 7 running on Intel Core i5- 2430M (64-bit) with PAA (Microsoft ® C/C++ Optimizing Compiler Version 16.00 for x64) CentOS 7.2 on a Forcepoint V10000 G4 Appliance (gcc 4.4.7) iOS 8.1 64-bit running on Apple A7 (ARMv8) without NEON and Crypto Extensions (clang Compilerv Version 600.0.56) iOS 8.1 64-bit running on Apple A7 (ARMv8) with NEON and Crypto Extensions (clang Compiler Version 600.0.56) (single-user mode)
Validation history
| Date | Type | Lab |
|---|---|---|
| 2017-04-05 | Initial | Acumen Security |
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: 2017-04-05