Forcepoint Next Generation Firewall
Certificate
| Certificate number | 3317 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 2 |
| Module type | Hardware |
| Embodiment | Multi-Chip Stand Alone |
| Vendor | Forcepoint · website |
| Hardware versions | 1101, 2101, 2105, 3305, and 6205 |
| Firmware versions | 6.4.1.20056.fips.8 |
Module description
Forcepoint NGFW is a next generation firewall that blocks malicious attacks and prevents the theft of data and intellectual property while transforming infrastructure and increasing the efficiency of your operations. With Forcepoint NGFW, painlessly handle the rapid shift to encrypted transmissions for both incoming and outgoing traffic.
Security level exceptions
- Mitigation of Other Attacks: N/A
Approved algorithms
| Algorithm | CAVP certificate |
|---|---|
| AES | 5168, 5511, 5512, 5513, 5514, 5515, 5516 |
| CKG | vendor affirmed |
| CVL | 1676, 1957, 1958, 1959, 1960, 1961, 1962 |
| DRBG | 1946, 2179, 2180, 2181 |
| ECDSA | 1339, 1480, 1481, 1482 |
| HMAC | 3429, 3667, 3668, 3669, 3670, 3671, 3672 |
| KBKDF | 230, 231, 232 |
| KTS | |
| KTS | |
| KTS | |
| KTS | |
| PBKDF | vendor affirmed |
| RSA | 2777, 2957, 2958, 2959 |
| SHS | 4175, 4422, 4423, 4424, 4425, 4426, 4427 |
| Triple-DES | 2632, 2774, 2775, 2776, 2777, 2778, 2779 |
Allowed algorithms
Diffie-Hellman (key agreement; key establishment methodology provides 112 bits of encryption strength); EC Diffie-Hellman (CVL Certs. #1676, #1957, #1959 and #1961 with CVL Certs. #1958, #1960 and #1962, key agreement; key establishment methodology provides between 112 and 256 bits of encryption strength); NDRNG; RSA (key wrapping; key establishment methodology provides 112 or 128 bits of encryption strength)
Tested configurations
- N/A
Validation history
| Date | Type | Lab |
|---|---|---|
| 2018-11-01 | Initial | 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: 2018-11-01