FortiGate-6300F/6301F/6500F/6501F
FortiGate-6300F/6301F/6500F/6501F, from Fortinet, Inc., holds FIPS 140-2 certificate #3942 at overall level 2. 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.
Certificate
| Certificate number | 3942 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 2 |
| Module type | Hardware |
| Embodiment | Multi-Chip Stand Alone |
| Vendor | Fortinet, Inc. · website |
| Hardware versions | FortiGate-6300F (C1AG83), FortiGate-6301F (C1AG85), FortiGate-6500F (C1AG84) and FortiGate-6501F (C1AG86) with Tamper Evident Seal Kit: FIPS-SEAL-RED |
| Firmware versions | FortiOS 6.2 build 5547 |
Module description
Quoted from the NIST CMVP entry for this certificate.
The FortiGate-6300F/6301F/6500F/6501F are multiple chip, standalone cryptographic modules consisting of production grade components contained in a physically protected enclosure in accordance with FIPS 140-2 Level 2 requirements.
Security level exceptions
- Roles, Services, and Authentication: Level 3
Approved algorithms (8)
| Algorithm | CAVP certificates |
|---|---|
| AES | C1549, C1575, C1576, C1578 |
| CVL | C1575, C1576, C1578 |
| DRBG | C1573 |
| ECDSA | C1575, C1576, C1578 |
| HMAC | C1575, C1576, C1578 |
| KTS | |
| RSA | A1187, A1252, C1576, C1578 |
| SHS | A1187, C1575, C1576, C1578 |
Allowed algorithms
Diffie-Hellman (CVL Certs. #C1575 and #C1576, key agreement; key establishment methodology provides between 112 and 196 bits of encryption strength); EC Diffie-Hellman (CVL Certs. #C1575 and #C1576, key agreement; key establishment methodology provides between 128 and 256 bits of encryption strength); NDRNG
Tested configurations
- N/A
Validation history
| Date | Type | Lab |
|---|---|---|
| 2021-06-02 | Initial | Lightship Security, Inc. |
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: 2021-06-02